Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.363059997558594e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.2896907329559326s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.7783474922180176s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.0003561973571777344s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 6.67572021484375e-06s
INFO | --- Analysis for 0080-3626 took 6.079373121261597s
Availability | SPARQL endpoint availability check for 土地利用图 took 3.981590270996094e-05s
Availability | VoID file availability check for 土地利用图 took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.24611663818359375s
Reputation | Calculation of the PageRank for 土地利用图 took 0.01996898651123047s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 土地利用图 took 0.00067138671875s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 2.6941299438476562e-05s
Believability | Calculation of trust value for 土地利用图 took 6.9141387939453125e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 3.723409414291382s
Availability | SPARQL endpoint availability check for 113322 took 4.100799560546875e-05s
Availability | VoID file availability check for 113322 took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for 113322 took 0.24356842041015625s
Reputation | Calculation of the PageRank for 113322 took 0.01970696449279785s
Interlinking | Calculation of Degree of Connection for 113322 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for 113322 took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for 113322 took 2.8133392333984375e-05s
Believability | Calculation of trust value for 113322 took 6.198883056640625e-06s
INFO | --- Analysis for 11 took 2.8397507667541504s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 4.0531158447265625e-05s
Availability | VoID file availability check for Korepetycje Buki took 0.0002384185791015625s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.26201844215393066s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.020077943801879883s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.000675201416015625s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 2.6464462280273438e-05s
Believability | Calculation of trust value for Korepetycje Buki took 5.7220458984375e-06s
INFO | --- Analysis for 12323 took 2.873246908187866s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 4.076957702636719e-05s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.2651951313018799s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.019910573959350586s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 8.559226989746094e-05s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 6.198883056640625e-06s
INFO | --- Analysis for 2000-us-census-rdf took 2.832674026489258s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 4.076957702636719e-05s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.26177048683166504s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.019793987274169922s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 3.552436828613281e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 6.4373016357421875e-06s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 2.854583740234375s
Availability | SPARQL endpoint availability check for Open Data Web took 4.029273986816406e-05s
Availability | VoID file availability check for Open Data Web took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.274294376373291s
Reputation | Calculation of the PageRank for Open Data Web took 0.02220940589904785s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.695487976074219e-05s
Believability | Calculation of trust value for Open Data Web took 6.67572021484375e-06s
INFO | --- Analysis for _data.odw.tw took 2.877396583557129s
Availability | SPARQL endpoint availability check for 土地利用 took 4.1961669921875e-05s
Availability | VoID file availability check for 土地利用 took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.2542285919189453s
Reputation | Calculation of the PageRank for 土地利用 took 0.02023458480834961s
Interlinking | Calculation of Degree of Connection for 土地利用 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0006756782531738281s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 2.6464462280273438e-05s
Believability | Calculation of trust value for 土地利用 took 7.152557373046875e-06s
INFO | --- Analysis for _data1.odw.tw took 2.7813470363616943s
Availability | SPARQL endpoint availability check for 土地利用模型 took 4.124641418457031e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.26107025146484375s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.019829750061035156s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0006730556488037109s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 2.6702880859375e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.1444091796875e-05s
INFO | --- Analysis for _data2.odw.tw took 2.909848213195801s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.1961669921875e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.24836993217468262s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020521879196166992s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 6.4373016357421875e-06s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 2.8883543014526367s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 4.100799560546875e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.29418253898620605s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.020069360733032227s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.6702880859375e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 6.9141387939453125e-06s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 2.825364112854004s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 4.029273986816406e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.25977015495300293s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 2.8371810913085938e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 5.9604644775390625e-06s
INFO | --- Analysis for A1 took 2.8003110885620117s
Availability | SPARQL endpoint availability check for SummerOlympics took 4.172325134277344e-05s
Availability | VoID file availability check for SummerOlympics took 0.0004134178161621094s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.2515292167663574s
Reputation | Calculation of the PageRank for SummerOlympics took 0.020406484603881836s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.4849853515625e-05s
Believability | Calculation of trust value for SummerOlympics took 7.62939453125e-06s
INFO | --- Analysis for abc took 2.8343544006347656s
Availability | SPARQL endpoint availability check for Test_m took 4.172325134277344e-05s
Availability | VoID file availability check for Test_m took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for Test_m took 0.24989771842956543s
Reputation | Calculation of the PageRank for Test_m took 0.02006983757019043s
Interlinking | Calculation of Degree of Connection for Test_m took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.765655517578125e-05s
Believability | Calculation of trust value for Test_m took 7.3909759521484375e-06s
INFO | --- Analysis for ABC took 2.8486907482147217s
Availability | SPARQL endpoint availability check for my intro took 6.985664367675781e-05s
Availability | VoID file availability check for my intro took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for my intro took 0.2544267177581787s
Reputation | Calculation of the PageRank for my intro took 0.020135879516601562s
Interlinking | Calculation of Degree of Connection for my intro took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for my intro took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for my intro took 2.7179718017578125e-05s
Believability | Calculation of trust value for my intro took 7.152557373046875e-06s
INFO | --- Analysis for abhay_intro took 2.861560821533203s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 3.981590270996094e-05s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.2529928684234619s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02055835723876953s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for abs-linked-data took 2.8402624130249023s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 4.7206878662109375e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.25591421127319336s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.7418136596679688e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 7.62939453125e-06s
INFO | --- Analysis for academic-offer-of-unl took 2.79646897315979s
Availability | SPARQL endpoint availability check for AcadOnto took 4.029273986816406e-05s
Availability | VoID file availability check for AcadOnto took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.2562732696533203s
Reputation | Calculation of the PageRank for AcadOnto took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for AcadOnto took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.7418136596679688e-05s
Believability | Calculation of trust value for AcadOnto took 7.3909759521484375e-06s
INFO | --- Analysis for acadonto took 2.8977341651916504s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 4.100799560546875e-05s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.25493502616882324s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.3855438232421875e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for acorn-sat took 2.836815595626831s
Availability | SPARQL endpoint availability check for Addgene took 4.1484832763671875e-05s
Availability | VoID file availability check for Addgene took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Addgene took 0.25357675552368164s
Reputation | Calculation of the PageRank for Addgene took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for Addgene took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.218650817871094e-05s
Believability | Calculation of trust value for Addgene took 1.0251998901367188e-05s
INFO | --- Analysis for addgene took 2.794020652770996s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.172325134277344e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.2539067268371582s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.02013707160949707s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 8.749961853027344e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 7.3909759521484375e-06s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 2.7771694660186768s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 4.076957702636719e-05s
Availability | VoID file availability check for AEMET metereological dataset took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.25427913665771484s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.019988059997558594s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 3.2901763916015625e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 6.9141387939453125e-06s
INFO | --- Analysis for aemet took 2.926105499267578s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.124641418457031e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.25469160079956055s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.019938230514526367s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 2.6702880859375e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for agenda-de-zaragoza took 2.8464601039886475s
Availability | SPARQL endpoint availability check for AgriNepalData took 4.076957702636719e-05s
Availability | VoID file availability check for AgriNepalData took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.24184942245483398s
Reputation | Calculation of the PageRank for AgriNepalData took 0.0199582576751709s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.580352783203125e-05s
Believability | Calculation of trust value for AgriNepalData took 6.198883056640625e-06s
INFO | --- Analysis for agrinepaldata took 2.85943341255188s
Availability | SPARQL endpoint availability check for AGRIS took 4.887580871582031e-05s
Availability | VoID file availability check for AGRIS took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for AGRIS took 0.26547956466674805s
Reputation | Calculation of the PageRank for AGRIS took 0.020481586456298828s
Interlinking | Calculation of Degree of Connection for AGRIS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AGRIS took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for AGRIS took 8.821487426757812e-05s
Believability | Calculation of trust value for AGRIS took 7.152557373046875e-06s
INFO | --- Analysis for agris took 2.8576438426971436s
Availability | SPARQL endpoint availability check for AGROVOC took 5.555152893066406e-05s
Availability | VoID file availability check for AGROVOC took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.26503705978393555s
Reputation | Calculation of the PageRank for AGROVOC took 0.020177841186523438s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.0001010894775390625s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc took 2.8440663814544678s
Availability | SPARQL endpoint availability check for AGROVOC took 4.172325134277344e-05s
Availability | VoID file availability check for AGROVOC took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.2552618980407715s
Reputation | Calculation of the PageRank for AGROVOC took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 8.368492126464844e-05s
Believability | Calculation of trust value for AGROVOC took 7.62939453125e-06s
INFO | --- Analysis for agrovoc-skos took 2.832648992538452s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 4.1961669921875e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.26166486740112305s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020124197006225586s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 2.7894973754882812e-05s
Believability | Calculation of trust value for Analytics India Magazine took 7.3909759521484375e-06s
INFO | --- Analysis for AIM took 2.8595950603485107s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 4.124641418457031e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00030922889709472656s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.2515735626220703s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.02044987678527832s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0009670257568359375s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 4.076957702636719e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 7.152557373046875e-06s
INFO | --- Analysis for AISHE took 2.8943088054656982s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.267692565917969e-05s
Availability | VoID file availability check for  equipment ontology took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.28237152099609375s
Reputation | Calculation of the PageRank for  equipment ontology took 0.02006840705871582s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 2.6226043701171875e-05s
Believability | Calculation of trust value for  equipment ontology took 7.152557373046875e-06s
INFO | --- Analysis for akash took 2.8727941513061523s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 4.100799560546875e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.24232959747314453s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 2.6941299438476562e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 5.9604644775390625e-06s
INFO | --- Analysis for aksworg took 2.857975482940674s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.100799560546875e-05s
Availability | VoID file availability check for AlchemyAPI took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.24196219444274902s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.02020883560180664s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0006818771362304688s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 2.6464462280273438e-05s
Believability | Calculation of trust value for AlchemyAPI took 6.9141387939453125e-06s
INFO | --- Analysis for alchemyapi took 2.789642572402954s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 4.506111145019531e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.24817466735839844s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020187854766845703s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 2.6702880859375e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 6.9141387939453125e-06s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 2.789724826812744s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1535160541534424s
Availability | VoID file availability check for aliada-scanbit-net took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.23912429809570312s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010514259338378906s
Believability | Calculation of trust value for aliada-scanbit-net took 1.1682510375976562e-05s
INFO | --- Analysis for aliada-scanbit-net took 4.000023603439331s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 4.1484832763671875e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.26511311531066895s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.02007460594177246s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 2.7894973754882812e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 7.3909759521484375e-06s
INFO | --- Analysis for allen-brain-atlas took 2.8779234886169434s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 4.100799560546875e-05s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.2536015510559082s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.020222187042236328s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007741451263427734s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 6.389617919921875e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.2159347534179688e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 2.8019211292266846s
Availability | SPARQL endpoint availability check for Alojamientos took 4.6253204345703125e-05s
Availability | VoID file availability check for Alojamientos took 0.0003521442413330078s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.24256324768066406s
Reputation | Calculation of the PageRank for Alojamientos took 0.02021646499633789s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.147125244140625e-05s
Believability | Calculation of trust value for Alojamientos took 7.3909759521484375e-06s
INFO | --- Analysis for alojamientos-zaragoza took 2.8192098140716553s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 4.0531158447265625e-05s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.24609994888305664s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.5762786865234375e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 6.67572021484375e-06s
INFO | --- Analysis for alpino-rdf took 2.862423896789551s
Availability | SPARQL endpoint availability check for AAT-atawil took 4.076957702636719e-05s
Availability | VoID file availability check for AAT-atawil took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.26427149772644043s
Reputation | Calculation of the PageRank for AAT-atawil took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.0279159545898438e-05s
Believability | Calculation of trust value for AAT-atawil took 6.4373016357421875e-06s
INFO | --- Analysis for Altawil took 2.865565538406372s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 4.220008850097656e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.26211047172546387s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020718812942504883s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.0040740966796875e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 5.9604644775390625e-06s
INFO | --- Analysis for am-collections-online took 2.878920316696167s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.029273986816406e-05s
Availability | VoID file availability check for Amer Nejma took 0.000244140625s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.24643182754516602s
Reputation | Calculation of the PageRank for Amer Nejma took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.147125244140625e-05s
Believability | Calculation of trust value for Amer Nejma took 6.198883056640625e-06s
INFO | --- Analysis for Amer_Nejma took 2.7844138145446777s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.278820276260376s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for amon took 2.833042621612549s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7472884654998779s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.26366114616394043s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.020556211471557617s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007884502410888672s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.107589721679688e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 5.7220458984375e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 3.5752298831939697s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 4.124641418457031e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00038814544677734375s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.24953913688659668s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.020284414291381836s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.0040740966796875e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 6.9141387939453125e-06s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.889864683151245s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 4.1484832763671875e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.25047969818115234s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 2.9087066650390625e-05s
Believability | Calculation of trust value for Animal Diversity Web took 6.4373016357421875e-06s
INFO | --- Analysis for animal-diversity-web took 2.886199712753296s
Availability | SPARQL endpoint availability check for Anime Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for Anime Dataset took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.25037693977355957s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for Anime Dataset took 1.1444091796875e-05s
INFO | --- Analysis for Anime took 2.792696237564087s
Availability | SPARQL endpoint availability check for ANNO took 4.1961669921875e-05s
Availability | VoID file availability check for ANNO took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for ANNO took 0.26961302757263184s
Reputation | Calculation of the PageRank for ANNO took 0.020517587661743164s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.266334533691406e-05s
Believability | Calculation of trust value for ANNO took 6.198883056640625e-06s
INFO | --- Analysis for anno took 2.864436149597168s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.3392181396484375e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.261216402053833s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020419836044311523s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.700920104980469e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 8.58306884765625e-06s
INFO | --- Analysis for AntiqueCarsCollection took 2.8206255435943604s
Availability | SPARQL endpoint availability check for apache took 4.00543212890625e-05s
Availability | VoID file availability check for apache took 0.00021839141845703125s
Completeness | Calculation of interlinking completeness for apache took 0.24148917198181152s
Reputation | Calculation of the PageRank for apache took 0.020567893981933594s
Interlinking | Calculation of Degree of Connection for apache took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for apache took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for apache took 5.1975250244140625e-05s
Believability | Calculation of trust value for apache took 6.9141387939453125e-06s
INFO | --- Analysis for apache took 2.782641649246216s
Availability | SPARQL endpoint availability check for Apertium RDF took 7.581710815429688e-05s
Availability | VoID file availability check for Apertium RDF took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.2501816749572754s
Reputation | Calculation of the PageRank for Apertium RDF took 0.02029585838317871s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf took 2.745328187942505s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 4.100799560546875e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.26499176025390625s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 2.867058753967285s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 5.054473876953125e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.25763463973999023s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02089524269104004s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 2.8354060649871826s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 4.029273986816406e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.2516038417816162s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-en-es took 2.776416778564453s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.291534423828125e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.27118372917175293s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.458427429199219e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-en-gl took 2.8540234565734863s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 9.655952453613281e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.2670924663543701s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.02046823501586914s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.291534423828125e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 7.3909759521484375e-06s
INFO | --- Analysis for apertium-rdf-eo-ca took 2.862701654434204s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.26785874366760254s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-EN took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.887580871582031e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-eo-en took 2.8407113552093506s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 4.410743713378906e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0003192424774169922s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.2490379810333252s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.02286529541015625s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.000972747802734375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.078315734863281e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 2.7350146770477295s
Availability | SPARQL endpoint availability check for Apertium RDF EO-FR took 4.00543212890625e-05s
Availability | VoID file availability check for Apertium RDF EO-FR took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.2310168743133545s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.020039081573486328s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-FR took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-FR took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 7.2479248046875e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-eo-fr took 2.7498691082000732s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 4.076957702636719e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.2894275188446045s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.02003765106201172s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.076957702636719e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 8.106231689453125e-06s
INFO | --- Analysis for apertium-rdf-es-an took 2.8531017303466797s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.2635633945465088s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.220008850097656e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 2.7994041442871094s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 8.20159912109375e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.26006603240966797s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 3.981590270996094e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.1682510375976562e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 2.9699790477752686s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.220008850097656e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.23889851570129395s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.0200808048248291s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0006725788116455078s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.076957702636719e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 7.62939453125e-06s
INFO | --- Analysis for apertium-rdf-es-gl took 2.796910524368286s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.2626218795776367s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.029273986816406e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 6.67572021484375e-06s
INFO | --- Analysis for apertium-rdf-es-pt took 2.947645664215088s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.2645857334136963s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.100799560546875e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-es-ro took 2.880215644836426s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 6.628036499023438e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.2627716064453125s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.020018577575683594s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.1484832763671875e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-eu-en took 2.867086172103882s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.26085400581359863s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.020036935806274414s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 5.14984130859375e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-eu-es took 2.8168957233428955s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 4.00543212890625e-05s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.27185606956481934s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.1961669921875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 7.152557373046875e-06s
INFO | --- Analysis for apertium-rdf-fr-ca took 2.8621463775634766s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 4.076957702636719e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.2891719341278076s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.020290136337280273s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.172325134277344e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-fr-es took 2.88346266746521s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.124641418457031e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.2675437927246094s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020318269729614258s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 1.4066696166992188e-05s
INFO | --- Analysis for apertium-rdf-oc-ca took 2.8483409881591797s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 5.1975250244140625e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.2629275321960449s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.267692565917969e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-oc-es took 2.8118526935577393s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 4.076957702636719e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.2444310188293457s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-CA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-CA took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.315376281738281e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-pt-ca took 2.8036348819732666s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 4.1484832763671875e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.2401587963104248s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 6.9141387939453125e-06s
INFO | --- Analysis for apertium-rdf-pt-gl took 2.842862367630005s
Availability | SPARQL endpoint availability check for AragoDBPedia took 4.220008850097656e-05s
Availability | VoID file availability check for AragoDBPedia took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.23389434814453125s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 3.814697265625e-05s
Believability | Calculation of trust value for AragoDBPedia took 7.62939453125e-06s
INFO | --- Analysis for aragodbpedia took 2.786635637283325s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for Archives Hub Linked Data took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.2391045093536377s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 4.649162292480469e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 7.62939453125e-06s
INFO | --- Analysis for archiveshub-linkeddata took 2.8864493370056152s
Availability | SPARQL endpoint availability check for Archivi ISMA took 4.172325134277344e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.25489234924316406s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.02090620994567871s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.24249267578125e-05s
Believability | Calculation of trust value for Archivi ISMA took 7.62939453125e-06s
INFO | --- Analysis for archivio-isma took 2.871861457824707s
Availability | SPARQL endpoint availability check for ARIADNE took 4.100799560546875e-05s
Availability | VoID file availability check for ARIADNE took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.2523179054260254s
Reputation | Calculation of the PageRank for ARIADNE took 0.02011585235595703s
Interlinking | Calculation of Degree of Connection for ARIADNE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ARIADNE took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 3.0040740966796875e-05s
Believability | Calculation of trust value for ARIADNE took 7.152557373046875e-06s
INFO | --- Analysis for ariadne took 2.811522960662842s
Availability | SPARQL endpoint availability check for Aristotle University took 4.4345855712890625e-05s
Availability | VoID file availability check for Aristotle University took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.2611253261566162s
Reputation | Calculation of the PageRank for Aristotle University took 0.02019977569580078s
Interlinking | Calculation of Degree of Connection for Aristotle University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.0994415283203125e-05s
Believability | Calculation of trust value for Aristotle University took 7.62939453125e-06s
INFO | --- Analysis for aristotle-university took 2.8249893188476562s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 4.100799560546875e-05s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.2562897205352783s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.020401954650878906s
Interlinking | Calculation of Degree of Connection for Transcription profiling of human, chimp and mouse brain took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of human, chimp and mouse brain took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 2.9802322387695312e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 6.4373016357421875e-06s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 2.7813916206359863s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.100799560546875e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.24730563163757324s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.020679950714111328s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.170967102050781e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 8.106231689453125e-06s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.848731756210327s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.220008850097656e-05s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.2599794864654541s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.719329833984375e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 7.3909759521484375e-06s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 2.7970101833343506s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.265735387802124s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.02024984359741211s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.870529174804688e-05s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 6.4373016357421875e-06s
INFO | --- Analysis for artenuevosmedios-gnoss took 2.8297924995422363s
Availability | SPARQL endpoint availability check for Arthroscopy community took 4.220008850097656e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.27571630477905273s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.020421743392944336s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.989738464355469e-05s
Believability | Calculation of trust value for Arthroscopy community took 1.3113021850585938e-05s
INFO | --- Analysis for arthroscopy took 2.9065191745758057s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 6.604194641113281e-05s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.25406599044799805s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.2874603271484375e-05s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 7.152557373046875e-06s
INFO | --- Analysis for artxscienceinternational-wikidata took 2.7945122718811035s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 4.557910919189453s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.23909759521484375s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02062821388244629s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006809234619140625s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.319450378417969e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 1.2159347534179688e-05s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 7.371001958847046s
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.12931227684021s
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.0002620220184326172s
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.26070356369018555s
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.022793054580688477s
Interlinking | Calculation of Degree of Connection for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 0.0010957717895507812s
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 8.749961853027344e-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 8.344650268554688e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 4.954701662063599s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.125648260116577s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.28010082244873047s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.019922494888305664s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006926059722900391s
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 1.0728836059570312e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 4.983378887176514s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.1178231239318848s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.2544524669647217s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.02009105682373047s
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.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 3.790855407714844e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-CRB took 4.937734842300415s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.127305030822754s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.2735438346862793s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.019927978515625s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.749961853027344e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 5.7220458984375e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 5.006622076034546s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.127131223678589s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.2555885314941406s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.02007889747619629s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC-DQOT took 4.933621406555176s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.1131491661071777s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.2368631362915039s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.020056724548339844s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.295608520507812e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 6.9141387939453125e-06s
INFO | --- Analysis for ASCDC-IHP-WCD took 4.979896783828735s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 2.834160327911377s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.2721829414367676s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.020329952239990234s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.43865966796875e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.1444091796875e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 5.711350679397583s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.1239330768585205s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006098747253417969s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.23640799522399902s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.01997852325439453s
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.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 4.8160552978515625e-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 5.009343862533569s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.107481002807617s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.2631967067718506s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.020199298858642578s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 4.76837158203125e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 4.96545147895813s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.4820828437805176s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.27541613578796387s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 4.267692565917969e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 7.62939453125e-06s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 6.359953880310059s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.1115365028381348s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.2781963348388672s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 6.937980651855469e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 6.4373016357421875e-06s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 5.008721113204956s
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.1386654376983643s
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.00026726722717285156s
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.24703478813171387s
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.020127534866333008s
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.0013580322265625e-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.0006902217864990234s
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.343292236328125e-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 7.3909759521484375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 5.00620174407959s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.125924825668335s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.000324249267578125s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.2589278221130371s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0009071826934814453s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 5.078315734863281e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 6.67572021484375e-06s
INFO | --- Analysis for ASCDC_-_DNB took 4.922036409378052s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 6.175041198730469e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.24964046478271484s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.02231287956237793s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0009047985076904297s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 8.344650268554688e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 7.62939453125e-06s
INFO | --- Analysis for asit took 2.7949678897857666s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 4.076957702636719e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.25797462463378906s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.02028179168701172s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.743171691894531e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 7.867813110351562e-06s
INFO | --- Analysis for asjp took 2.846141815185547s
Availability | SPARQL endpoint availability check for ASN:US took 5.1975250244140625e-05s
Availability | VoID file availability check for ASN:US took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for ASN:US took 0.2662181854248047s
Reputation | Calculation of the PageRank for ASN:US took 0.02018880844116211s
Interlinking | Calculation of Degree of Connection for ASN:US took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ASN:US took 0.0008444786071777344s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.604194641113281e-05s
Believability | Calculation of trust value for ASN:US took 7.3909759521484375e-06s
INFO | --- Analysis for asn-us took 2.852180242538452s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 4.3392181396484375e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.2892892360687256s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.02019190788269043s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 2.7894973754882812e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 7.152557373046875e-06s
INFO | --- Analysis for aspire-mmu took 2.8820948600769043s
Availability | SPARQL endpoint availability check for associations took 4.1484832763671875e-05s
Availability | VoID file availability check for associations took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for associations took 0.24915409088134766s
Reputation | Calculation of the PageRank for associations took 0.020039081573486328s
Interlinking | Calculation of Degree of Connection for associations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for associations took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for associations took 6.389617919921875e-05s
Believability | Calculation of trust value for associations took 7.62939453125e-06s
INFO | --- Analysis for associations took 2.8692939281463623s
Availability | SPARQL endpoint availability check for ATC publikovaná SÚKL took 4.220008850097656e-05s
Availability | VoID file availability check for ATC publikovaná SÚKL took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.2536778450012207s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 2.8371810913085938e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 6.67572021484375e-06s
INFO | --- Analysis for atc-publikovan--s-kl took 2.8690688610076904s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.100799560546875e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.24326419830322266s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.02026510238647461s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.559226989746094e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.0967254638671875e-05s
INFO | --- Analysis for athelia-rfid took 2.8981142044067383s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 4.220008850097656e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.2639658451080322s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for aueb-linked-open-data took 2.80497145652771s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 6.699562072753906e-05s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.2706599235534668s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020253658294677734s
Interlinking | Calculation of Degree of Connection for Augustini Confessiones in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Augustini Confessiones in LiLa took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.839897155761719e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for AugustiniConfessiones took 2.878708600997925s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 4.076957702636719e-05s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005609989166259766s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.26446080207824707s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02002429962158203s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.368492126464844e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.3113021850585938e-05s
INFO | --- Analysis for austrian_ski_racers took 2.8298068046569824s
Availability | SPARQL endpoint availability check for AVsOnto took 4.100799560546875e-05s
Availability | VoID file availability check for AVsOnto took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.2399005889892578s
Reputation | Calculation of the PageRank for AVsOnto took 0.020137548446655273s
Interlinking | Calculation of Degree of Connection for AVsOnto took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 2.7894973754882812e-05s
Believability | Calculation of trust value for AVsOnto took 3.24249267578125e-05s
INFO | --- Analysis for AVsOnto took 2.8246171474456787s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 30.38443875312805s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2599472999572754s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 5.507469177246094e-05s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.76837158203125e-06s
INFO | --- Analysis for b3kat took 63.41401505470276s
Availability | SPARQL endpoint availability check for BabelNet took 4.124641418457031e-05s
Availability | VoID file availability check for BabelNet took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for BabelNet took 0.25410914421081543s
Reputation | Calculation of the PageRank for BabelNet took 0.020140409469604492s
Interlinking | Calculation of Degree of Connection for BabelNet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001556873321533203s
Believability | Calculation of trust value for BabelNet took 5.4836273193359375e-06s
INFO | --- Analysis for babelnet took 2.842925548553467s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 3.9577484130859375e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.2419896125793457s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.7418136596679688e-05s
Believability | Calculation of trust value for Bacevicius.lt took 6.9141387939453125e-06s
INFO | --- Analysis for Bacevicius.lt took 2.866325616836548s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 7.82012939453125e-05s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.2679586410522461s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.020407438278198242s
Interlinking | Calculation of Degree of Connection for Basisregistratie Adressen en Gebouwen took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Basisregistratie Adressen en Gebouwen took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.124641418457031e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 6.4373016357421875e-06s
INFO | --- Analysis for bag took 2.868107557296753s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.172325134277344e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.2549278736114502s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.6941299438476562e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.9141387939453125e-06s
INFO | --- Analysis for baixue took 2.8421857357025146s
Availability | SPARQL endpoint availability check for baixue composer took 4.1484832763671875e-05s
Availability | VoID file availability check for baixue composer took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for baixue composer took 0.24430394172668457s
Reputation | Calculation of the PageRank for baixue composer took 0.020022153854370117s
Interlinking | Calculation of Degree of Connection for baixue composer took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.765655517578125e-05s
Believability | Calculation of trust value for baixue composer took 6.9141387939453125e-06s
INFO | --- Analysis for baixue_composer took 2.7582292556762695s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.984306335449219e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.27115845680236816s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 6.4373016357421875e-06s
INFO | --- Analysis for baixue_imagery took 2.8554718494415283s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 4.553794860839844e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.00037741661071777344s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.24979472160339355s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.9802322387695312e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 7.3909759521484375e-06s
INFO | --- Analysis for baixue_imagery1 took 2.7900643348693848s
Availability | SPARQL endpoint availability check for BAMS took 4.1484832763671875e-05s
Availability | VoID file availability check for BAMS took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for BAMS took 0.24482345581054688s
Reputation | Calculation of the PageRank for BAMS took 0.020472288131713867s
Interlinking | Calculation of Degree of Connection for BAMS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BAMS took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.123283386230469e-05s
Believability | Calculation of trust value for BAMS took 1.2159347534179688e-05s
INFO | --- Analysis for bams took 2.8517136573791504s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 4.172325134277344e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.2773473262786865s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.0206298828125s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 4.029273986816406e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 2.900752067565918s
Availability | SPARQL endpoint availability check for BBC Music took 0.4136056900024414s
Availability | VoID file availability check for BBC Music took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for BBC Music took 0.26168227195739746s
Reputation | Calculation of the PageRank for BBC Music took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for BBC Music took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.0006806850433349609s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00011992454528808594s
Believability | Calculation of trust value for BBC Music took 7.152557373046875e-06s
INFO | --- Analysis for bbc-music took 3.268300771713257s
Availability | SPARQL endpoint availability check for BBC Programmes took 4.1484832763671875e-05s
Availability | VoID file availability check for BBC Programmes took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.26485109329223633s
Reputation | Calculation of the PageRank for BBC Programmes took 0.020288705825805664s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 9.632110595703125e-05s
Believability | Calculation of trust value for BBC Programmes took 1.1444091796875e-05s
INFO | --- Analysis for bbc-programmes took 2.8378472328186035s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.3607640266418457s
Availability | VoID file availability check for BBC Wildlife Finder took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.26668286323547363s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.512901306152344e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 6.67572021484375e-06s
INFO | --- Analysis for bbc-wildlife-finder took 3.2753467559814453s
Availability | SPARQL endpoint availability check for BBOP took 0.0001423358917236328s
Availability | VoID file availability check for BBOP took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for BBOP took 0.2621035575866699s
Reputation | Calculation of the PageRank for BBOP took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for BBOP took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0009279251098632812s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.2901763916015625e-05s
Believability | Calculation of trust value for BBOP took 7.152557373046875e-06s
INFO | --- Analysis for bbop took 2.884350299835205s
Availability | SPARQL endpoint availability check for BBOP took 3.981590270996094e-05s
Availability | VoID file availability check for BBOP took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for BBOP took 0.2557804584503174s
Reputation | Calculation of the PageRank for BBOP took 0.02079463005065918s
Interlinking | Calculation of Degree of Connection for BBOP took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BBOP took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.7179718017578125e-05s
Believability | Calculation of trust value for BBOP took 6.4373016357421875e-06s
INFO | --- Analysis for bbop-selected took 2.8195433616638184s
Availability | SPARQL endpoint availability check for Bdgp took 4.458427429199219e-05s
Availability | VoID file availability check for Bdgp took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Bdgp took 0.26787829399108887s
Reputation | Calculation of the PageRank for Bdgp took 0.020289897918701172s
Interlinking | Calculation of Degree of Connection for Bdgp took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bdgp took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for Bdgp took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bdgp took 7.62939453125e-06s
INFO | --- Analysis for bdgp took 2.907407283782959s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.00543212890625e-05s
Availability | VoID file availability check for Bendev Junior took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.24610638618469238s
Reputation | Calculation of the PageRank for Bendev Junior took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bendev Junior took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 2.765655517578125e-05s
Believability | Calculation of trust value for Bendev Junior took 7.3909759521484375e-06s
INFO | --- Analysis for bendevoficial took 2.8064210414886475s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 4.00543212890625e-05s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.2652299404144287s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.02012181282043457s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.222724914550781e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.2159347534179688e-05s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 2.893815517425537s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 6.008148193359375e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.2591552734375s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.7179718017578125e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 6.67572021484375e-06s
INFO | --- Analysis for berlin-offener-haushalt took 2.7826735973358154s
Availability | SPARQL endpoint availability check for berlios took 3.8623809814453125e-05s
Availability | VoID file availability check for berlios took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for berlios took 0.27022647857666016s
Reputation | Calculation of the PageRank for berlios took 0.020209789276123047s
Interlinking | Calculation of Degree of Connection for berlios took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for berlios took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for berlios took 8.273124694824219e-05s
Believability | Calculation of trust value for berlios took 7.62939453125e-06s
INFO | --- Analysis for berlios took 2.892781972885132s
Availability | SPARQL endpoint availability check for Between Our Worlds took 5.078315734863281e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.2428576946258545s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.020366668701171875s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.270408630371094e-05s
Believability | Calculation of trust value for Between Our Worlds took 7.152557373046875e-06s
INFO | --- Analysis for betweenourworlds took 2.827779531478882s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.2438507080078125e-05s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.2638275623321533s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.416175842285156e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for bfs-linked-data took 2.875614643096924s
Availability | SPARQL endpoint availability check for BibBase took 3.981590270996094e-05s
Availability | VoID file availability check for BibBase took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for BibBase took 0.26059389114379883s
Reputation | Calculation of the PageRank for BibBase took 0.020097017288208008s
Interlinking | Calculation of Degree of Connection for BibBase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for BibBase took 0.0007989406585693359s
Interlinking | Calculation of Clustering coefficient for BibBase took 0.00012159347534179688s
Believability | Calculation of trust value for BibBase took 7.152557373046875e-06s
INFO | --- Analysis for bibbase took 2.80428409576416s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 4.029273986816406e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.2587876319885254s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 9.72747802734375e-05s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 7.152557373046875e-06s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 2.838078737258911s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 4.1484832763671875e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.25435900688171387s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.02009868621826172s
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.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.250640869140625e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 9.298324584960938e-06s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 2.8489105701446533s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.26955652236938477s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.02012038230895996s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 2.77219295501709s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 3.981590270996094e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.24994540214538574s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020720481872558594s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0008831024169921875s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.933906555175781e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1682510375976562e-05s
INFO | --- Analysis for BibSonomy took 2.7508647441864014s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 4.0531158447265625e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.25696778297424316s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.020122051239013672s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 7.152557373046875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 2.8247246742248535s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 4.076957702636719e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.2516603469848633s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02171802520751953s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0008392333984375s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 3.1948089599609375e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 7.152557373046875e-06s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.8303840160369873s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.25184178352355957s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020415782928466797s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 3.24249267578125e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-acfsid took 2.7592720985412598s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 5.340576171875e-05s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.00023937225341796875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.25283098220825195s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.020104169845581055s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.059906005859375e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 2.9695708751678467s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.23703455924987793s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020127296447753906s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00010967254638671875s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 6.67572021484375e-06s
INFO | --- Analysis for bio2rdf-biomodels took 2.7623543739318848s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 4.315376281738281e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.2405083179473877s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020590543746948242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 2.7972936630249023s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0005016326904296875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.28984665870666504s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.0003993511199951172s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-bioportal took 2.839219808578491s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.258159875869751s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.020044803619384766s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.0067901611328125e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-chembl took 2.845665693283081s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.25226736068725586s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.315376281738281e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 2.8516902923583984s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.26479101181030273s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.389617919921875e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-ctd took 2.857022523880005s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 5.14984130859375e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.2866175174713135s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.4345855712890625e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-dataset took 2.825925350189209s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.2510514259338379s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.029044628143310547s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.001222848892211914s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 8.96453857421875e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-dbsnp took 2.8057525157928467s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 4.506111145019531e-05s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.24440479278564453s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.02170729637145996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0011043548583984375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.0001125335693359375s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-drugbank took 2.8590245246887207s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::Genage took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.2739276885986328s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.054473876953125e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-genage took 2.8626530170440674s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 5.5789947509765625e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.26319098472595215s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.020569324493408203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.7697296142578125e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-genbank took 2.8217215538024902s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 4.935264587402344e-05s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.25277066230773926s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.0201416015625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 4.601478576660156e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-gendr took 2.8635177612304688s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 6.365776062011719e-05s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0003819465637207031s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.2557332515716553s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.02188420295715332s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0008485317230224609s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.723403930664062e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-goa took 2.81876277923584s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.26792359352111816s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010085105895996094s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-hgnc took 2.7727198600769043s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 5.269050598144531e-05s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.24886345863342285s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.020687341690063477s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 4.76837158203125e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-homologene took 2.805584669113159s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 4.267692565917969e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.27555012702941895s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-inoh took 2.857456922531128s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.25724053382873535s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 0.00010323524475097656s
Believability | Calculation of trust value for Bio2RDF::Interpro took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-interpro took 2.864280939102173s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.2771427631378174s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.02072310447692871s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.534027099609375e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-iproclass took 2.887326240539551s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 7.271766662597656e-05s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.27756714820861816s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.62939453125e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-irefindex took 2.9045684337615967s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.25299715995788574s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.020368337631225586s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0006799697875976562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.175041198730469e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-kegg took 2.8882081508636475s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.2631258964538574s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020622730255126953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.170967102050781e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-kegg-biopax took 2.828658103942871s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.2554442882537842s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.02054429054260254s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 2.8848648071289062e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 2.8844926357269287s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.2469491958618164s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.2438507080078125e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-lsr took 2.7967519760131836s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.26269054412841797s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.020755529403686523s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.677078247070312e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-mesh took 2.8306915760040283s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.0003333091735839844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.25793981552124023s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 8.416175842285156e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-mgi took 2.828331232070923s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 4.458427429199219e-05s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.00026917457580566406s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.2791481018066406s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.0205535888671875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.00011515617370605469s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-ncbigene took 2.874699592590332s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.24349284172058105s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.673004150390625e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ndc took 2.815690040588379s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.2767221927642822s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-netpath took 2.8423104286193848s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.2644064426422119s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020403385162353516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007638931274414062s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.266334533691406e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-nextprot took 2.988273859024048s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::Omim took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.2695784568786621s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.0001232624053955078s
Believability | Calculation of trust value for Bio2RDF::Omim took 7.152557373046875e-06s
INFO | --- Analysis for bio2rdf-omim took 2.8483095169067383s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 4.124641418457031e-05s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.2552940845489502s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 3.743171691894531e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 2.828986406326294s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.00037860870361328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.2549459934234619s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.02058267593383789s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 6.937980651855469e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-orphanet took 2.8561415672302246s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.27375197410583496s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.021568775177001953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.0517578125e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 2.896749496459961s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 4.1484832763671875e-05s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.2774999141693115s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0006814002990722656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 6.651878356933594e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-pharmgkb took 2.8613476753234863s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.0531158447265625e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2528257369995117s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020200729370117188s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 2.956390380859375e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 2.837486505508423s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.26221418380737305s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02074146270751953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-pid took 2.845609188079834s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.2578549385070801s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-pubchem-2 took 2.852773427963257s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 4.1961669921875e-05s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.00031566619873046875s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.24750304222106934s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02074265480041504s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0008680820465087891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.00014400482177734375s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 7.62939453125e-06s
INFO | --- Analysis for bio2rdf-pubmed took 2.782137155532837s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.2646148204803467s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020410537719726562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.699562072753906e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-reactome took 2.7834279537200928s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 4.172325134277344e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0005095005035400391s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.26467132568359375s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020784616470336914s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0009770393371582031s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 6.437301635742188e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-rhea took 2.815683364868164s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 4.2438507080078125e-05s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.29018688201904297s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.020238637924194336s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.390975952148438e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sabiork took 2.8646111488342285s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.2644202709197998s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 0.00010228157043457031s
Believability | Calculation of trust value for Bio2RDF::Sgd took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-sgd took 2.8606584072113037s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 4.220008850097656e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.2558269500732422s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.02042222023010254s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.695487976074219e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-sgd-resources took 2.8424112796783447s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.255002498626709s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.7670135498046875e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 8.58306884765625e-06s
INFO | --- Analysis for bio2rdf-sider took 2.8805410861968994s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.2629220485687256s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.9802322387695312e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-spike took 2.790580987930298s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 4.076957702636719e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.2576296329498291s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.2438507080078125e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.863633394241333s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.24558591842651367s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 0.00010013580322265625s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 8.344650268554688e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 2.8845908641815186s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.26482701301574707s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.02069854736328125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0009036064147949219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.814697265625e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 7.867813110351562e-06s
INFO | --- Analysis for bio2rdf-wikipathways took 2.8107244968414307s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.2639286518096924s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.02095627784729004s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007908344268798828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.843971252441406e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 8.106231689453125e-06s
INFO | --- Analysis for bio2rdf-wormbase took 2.8448917865753174s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 6.175041198730469e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.2636075019836426s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.3113021850585938e-05s
Believability | Calculation of trust value for Biografías y Vidas took 7.152557373046875e-06s
INFO | --- Analysis for biografiasyvidas took 2.8142552375793457s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 4.2438507080078125e-05s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.26576948165893555s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.020611047744750977s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 8.988380432128906e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 8.58306884765625e-06s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 2.8843958377838135s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 4.00543212890625e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.2536299228668213s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 2.9802322387695312e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for biolit took 2.8690237998962402s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 4.124641418457031e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.25904393196105957s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.020593643188476562s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.933906555175781e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 7.152557373046875e-06s
INFO | --- Analysis for biolod-pdb took 2.7646358013153076s
Availability | SPARQL endpoint availability check for BioModels RDF took 4.029273986816406e-05s
Availability | VoID file availability check for BioModels RDF took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.2436225414276123s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020485639572143555s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.790855407714844e-05s
Believability | Calculation of trust value for BioModels RDF took 7.3909759521484375e-06s
INFO | --- Analysis for biomodels-rdf took 2.8454580307006836s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.0531158447265625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.23910999298095703s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.956390380859375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.62939453125e-06s
INFO | --- Analysis for Biop took 2.8325769901275635s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.0531158447265625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.00035858154296875s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.24639201164245605s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020500659942626953s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.314018249511719e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.298324584960938e-06s
INFO | --- Analysis for Bioportal took 2.776118516921997s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 4.00543212890625e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.2589857578277588s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.020719289779663086s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.0008213520050048828s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006623268127441406s
Believability | Calculation of trust value for Amphibian gross anatomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-aao took 2.745687246322632s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 4.220008850097656e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.2407701015472412s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.01990365982055664s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.00028061866760253906s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-aba took 2.7455527782440186s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.253307580947876s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.02010321617126465s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014951229095458984s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-acgt took 2.6473402976989746s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 5.4836273193359375e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.2700049877166748s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.02005624771118164s
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.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.0003132820129394531s
Believability | Calculation of trust value for Animal natural history and life history took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-adw took 2.733934164047241s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 3.838539123535156e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.24503827095031738s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004572868347167969s
Believability | Calculation of trust value for Anatomical Entity Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-aeo took 2.722423791885376s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 4.172325134277344e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.2553102970123291s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0009837150573730469s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-aero took 2.8179047107696533s
Availability | SPARQL endpoint availability check for AI/RHEUM took 3.886222839355469e-05s
Availability | VoID file availability check for AI/RHEUM took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.24975299835205078s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.0201416015625s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.00040149688720703125s
Believability | Calculation of trust value for AI/RHEUM took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-air took 2.823014736175537s
Availability | SPARQL endpoint availability check for Amino Acid took 3.933906555175781e-05s
Availability | VoID file availability check for Amino Acid took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.25284624099731445s
Reputation | Calculation of the PageRank for Amino Acid took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Amino Acid took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Amino Acid took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002448558807373047s
Believability | Calculation of trust value for Amino Acid took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-amino-acid took 2.8373827934265137s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.0006778240203857422s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.2668426036834717s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020190000534057617s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002894401550292969s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-apo took 2.815471887588501s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 4.267692565917969e-05s
Availability | VoID file availability check for African Traditional Medicine took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.25675368309020996s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.0002295970916748047s
Believability | Calculation of trust value for African Traditional Medicine took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-atmo took 2.813718557357788s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 4.0531158447265625e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.2805910110473633s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.726119995117188e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-ato took 2.9225172996520996s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for BioAssay Ontology took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.24935317039489746s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020220041275024414s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0012640953063964844s
Believability | Calculation of trust value for BioAssay Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-bao took 2.851682662963867s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 3.910064697265625e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.000244140625s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.2356700897216797s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.0003750324249267578s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 2.808445930480957s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.2539184093475342s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.01988363265991211s
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.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003075599670410156s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-bcgo took 2.93243145942688s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.2749035358428955s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0013668537139892578s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-bdo took 2.7796528339385986s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.26393818855285645s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020277023315429688s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004799365997314453s
Believability | Calculation of trust value for Basic Formal Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-bfo took 2.880988836288452s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 4.100799560546875e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.23428082466125488s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020344972610473633s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.00070953369140625s
Believability | Calculation of trust value for Bleeding History Phenotype took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-bho took 2.786705493927002s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.601478576660156e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.2720937728881836s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00042700767517089844s
Believability | Calculation of trust value for Bilateria anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bila took 2.808328151702881s
Availability | SPARQL endpoint availability check for BIRNLex took 4.0531158447265625e-05s
Availability | VoID file availability check for BIRNLex took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.24119138717651367s
Reputation | Calculation of the PageRank for BIRNLex took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for BIRNLex took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for BIRNLex took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.0014569759368896484s
Believability | Calculation of trust value for BIRNLex took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-birnlex took 2.7711246013641357s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.23500537872314453s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007588863372802734s
Believability | Calculation of trust value for Gene Regulation Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-bootstrep took 2.8726210594177246s
Availability | SPARQL endpoint availability check for BioPAX took 4.029273986816406e-05s
Availability | VoID file availability check for BioPAX took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for BioPAX took 0.2769787311553955s
Reputation | Calculation of the PageRank for BioPAX took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for BioPAX took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for BioPAX took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for BioPAX took 0.00011324882507324219s
Believability | Calculation of trust value for BioPAX took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-bp took 2.869915723800659s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 5.173683166503906e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.24634242057800293s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.0003237724304199219s
Believability | Calculation of trust value for Biomedical Resource Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-bro_x1 took 2.7936179637908936s
Availability | SPARQL endpoint availability check for Spatial Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.2957134246826172s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002028942108154297s
Believability | Calculation of trust value for Spatial Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bspo took 2.829404592514038s
Availability | SPARQL endpoint availability check for BioTop took 4.0531158447265625e-05s
Availability | VoID file availability check for BioTop took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for BioTop took 0.2793107032775879s
Reputation | Calculation of the PageRank for BioTop took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for BioTop took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006296634674072266s
Believability | Calculation of trust value for BioTop took 7.62939453125e-06s
INFO | --- Analysis for bioportal-bt took 2.7549684047698975s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 4.076957702636719e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.2883603572845459s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008392333984375s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-bto took 2.933906316757202s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.25559115409851074s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.02010512351989746s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0017917156219482422s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-canco took 2.8615715503692627s
Availability | SPARQL endpoint availability check for CAO took 4.100799560546875e-05s
Availability | VoID file availability check for CAO took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for CAO took 0.2735254764556885s
Reputation | Calculation of the PageRank for CAO took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for CAO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CAO took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006213188171386719s
Believability | Calculation of trust value for CAO took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-cao took 2.933737277984619s
Availability | SPARQL endpoint availability check for CareLex took 4.124641418457031e-05s
Availability | VoID file availability check for CareLex took 0.0004124641418457031s
Completeness | Calculation of interlinking completeness for CareLex took 0.26393747329711914s
Reputation | Calculation of the PageRank for CareLex took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for CareLex took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CareLex took 0.0006778240203857422s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.673004150390625e-05s
Believability | Calculation of trust value for CareLex took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-carelex took 2.8857951164245605s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Cell Cycle Ontology took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.2489326000213623s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020015954971313477s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007786750793457031s
Believability | Calculation of trust value for Cell Cycle Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-cco took 2.8296003341674805s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.27722954750061035s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002636909484863281s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cdao took 2.8530123233795166s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 4.100799560546875e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0002872943878173828s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.28457093238830566s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007550716400146484s
Believability | Calculation of trust value for Chemical entities of biological interest took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-chebi took 3.230504274368286s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 3.9577484130859375e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.23462867736816406s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.020348310470581055s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002467632293701172s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 7.62939453125e-06s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.829317808151245s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.28593993186950684s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.02329230308532715s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0012145042419433594s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0010914802551269531s
Believability | Calculation of trust value for Chemical Information Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cheminf took 2.866842746734619s
Availability | SPARQL endpoint availability check for Cell type took 4.076957702636719e-05s
Availability | VoID file availability check for Cell type took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Cell type took 0.23717975616455078s
Reputation | Calculation of the PageRank for Cell type took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Cell type took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.0003712177276611328s
Believability | Calculation of trust value for Cell type took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-cl took 2.809260368347168s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.25313234329223633s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0007984638214111328s
Believability | Calculation of trust value for Cell Line Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-clo took 2.87372088432312s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.26348114013671875s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017380714416503906s
Believability | Calculation of trust value for Clinical Measurement Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-cmo took 2.8338418006896973s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.57763671875e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.2750270366668701s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020120620727539062s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.0002117156982421875s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cno took 2.8439652919769287s
Availability | SPARQL endpoint availability check for Wheat trait took 4.458427429199219e-05s
Availability | VoID file availability check for Wheat trait took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.24971795082092285s
Reputation | Calculation of the PageRank for Wheat trait took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Wheat trait took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Wheat trait took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 5.507469177246094e-05s
Believability | Calculation of trust value for Wheat trait took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-co_wheat took 2.8474881649017334s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 3.981590270996094e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.28841710090637207s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.020705223083496094s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.00034618377685546875s
Believability | Calculation of trust value for Cognitive Atlas took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-cogat took 2.8677496910095215s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.2693512439727783s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.02022695541381836s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0008077621459960938s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cogpo took 2.847954273223877s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 5.054473876953125e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.2729799747467041s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.00042247772216796875s
Believability | Calculation of trust value for Current Procedural Terminology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-cpt took 2.816408634185791s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 4.029273986816406e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.24591875076293945s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.001779794692993164s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 7.62939453125e-06s
INFO | --- Analysis for bioportal-csp took 2.8268227577209473s
Availability | SPARQL endpoint availability check for COSTART took 4.5299530029296875e-05s
Availability | VoID file availability check for COSTART took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for COSTART took 0.2635974884033203s
Reputation | Calculation of the PageRank for COSTART took 0.0201871395111084s
Interlinking | Calculation of Degree of Connection for COSTART took 4.267692565917969e-05s
Interlinking | Calculation of Centrality for COSTART took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009667873382568359s
Believability | Calculation of trust value for COSTART took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-cst took 2.8041892051696777s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 4.220008850097656e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.2790098190307617s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020394563674926758s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004951953887939453s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-ctcae took 2.8772923946380615s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 5.269050598144531e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.00031065940856933594s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.28229570388793945s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.021122455596923828s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.00080108642578125s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0005249977111816406s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ctx took 2.8216285705566406s
Availability | SPARQL endpoint availability check for Dendritic cell took 3.933906555175781e-05s
Availability | VoID file availability check for Dendritic cell took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.23682761192321777s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020488500595092773s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00029921531677246094s
Believability | Calculation of trust value for Dendritic cell took 7.62939453125e-06s
INFO | --- Analysis for bioportal-dc_cl took 2.912557601928711s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 4.076957702636719e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.24150609970092773s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020460128784179688s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.845329284667969e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-ddanat took 2.816725730895996s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 4.100799560546875e-05s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.2530214786529541s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009136199951171875s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ddi took 2.837019443511963s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.24989628791809082s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.463859558105469e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-diagnosticont took 2.7544872760772705s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.24924898147583008s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.00015997886657714844s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.8275368213653564s
Availability | SPARQL endpoint availability check for Human disease ontology took 4.3392181396484375e-05s
Availability | VoID file availability check for Human disease ontology took 0.00032138824462890625s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.2616710662841797s
Reputation | Calculation of the PageRank for Human disease ontology took 0.020367145538330078s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006394386291503906s
Believability | Calculation of trust value for Human disease ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-doid took 2.8484110832214355s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.38690185546875e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0005145072937011719s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.255403995513916s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.022577524185180664s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0010657310485839844s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008988380432128906s
Believability | Calculation of trust value for Electrocardiography Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-ecg took 2.8446335792541504s
Availability | SPARQL endpoint availability check for Evidence codes took 4.00543212890625e-05s
Availability | VoID file availability check for Evidence codes took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.26757311820983887s
Reputation | Calculation of the PageRank for Evidence codes took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for Evidence codes took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Evidence codes took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 2.7418136596679688e-05s
Believability | Calculation of trust value for Evidence codes took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-eco took 2.8093504905700684s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.25605177879333496s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017778873443603516s
Believability | Calculation of trust value for Experimental Factor Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-efo took 2.7356455326080322s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 3.9577484130859375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.25888824462890625s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.020214319229125977s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0011184215545654297s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-ehda took 2.8929502964019775s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 4.029273986816406e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.25848817825317383s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0008168220520019531s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007519721984863281s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-ehdaa took 2.8556344509124756s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.100799560546875e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.2738687992095947s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.020574569702148438s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005397796630859375s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ehdaa2 took 2.793079376220703s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.792213439941406e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.27968478202819824s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.020310640335083008s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 2.6941299438476562e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-emap took 2.8649652004241943s
Availability | SPARQL endpoint availability check for Environment Ontology took 5.435943603515625e-05s
Availability | VoID file availability check for Environment Ontology took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.24663400650024414s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02046036720275879s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0008842945098876953s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.00046515464782714844s
Believability | Calculation of trust value for Environment Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-envo took 2.8394014835357666s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 3.981590270996094e-05s
Availability | VoID file availability check for Plant environmental conditions took 0.000244140625s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.25113463401794434s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.0002963542938232422s
Believability | Calculation of trust value for Plant environmental conditions took 7.62939453125e-06s
INFO | --- Analysis for bioportal-eo took 2.81697678565979s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.25897765159606934s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.001149892807006836s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ep took 2.9020824432373047s
Availability | SPARQL endpoint availability check for Epilepsy took 4.100799560546875e-05s
Availability | VoID file availability check for Epilepsy took 0.0009992122650146484s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.23786115646362305s
Reputation | Calculation of the PageRank for Epilepsy took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Epilepsy took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Epilepsy took 0.0008907318115234375s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001571178436279297s
Believability | Calculation of trust value for Epilepsy took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.827342987060547s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.410743713378906e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.2633960247039795s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0012736320495605469s
Believability | Calculation of trust value for eagle-i research resource ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ero took 2.930656909942627s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 4.1484832763671875e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.258103609085083s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.00115203857421875s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ev took 2.776280641555786s
Availability | SPARQL endpoint availability check for ExO took 4.076957702636719e-05s
Availability | VoID file availability check for ExO took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for ExO took 0.26226162910461426s
Reputation | Calculation of the PageRank for ExO took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for ExO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ExO took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00023293495178222656s
Believability | Calculation of trust value for ExO took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-exo took 2.852297782897949s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 6.985664367675781e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.24781274795532227s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020131826400756836s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00010609626770019531s
Believability | Calculation of trust value for Fungal gross anatomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fao took 2.821066379547119s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.076957702636719e-05s
Availability | VoID file availability check for Biological imaging methods took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.26544618606567383s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019979476928710938s
Believability | Calculation of trust value for Biological imaging methods took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-fbbi took 2.8588850498199463s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 3.981590270996094e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.25580382347106934s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006239414215087891s
Believability | Calculation of trust value for Drosophila gross anatomy took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fbbt took 2.8349790573120117s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 3.910064697265625e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.2536196708679199s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.02104806900024414s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0009355545043945312s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0005252361297607422s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-fbcv took 2.7739014625549316s
Availability | SPARQL endpoint availability check for Drosophila development took 4.0531158447265625e-05s
Availability | VoID file availability check for Drosophila development took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.23614001274108887s
Reputation | Calculation of the PageRank for Drosophila development took 0.02013230323791504s
Interlinking | Calculation of Degree of Connection for Drosophila development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.267692565917969e-05s
Believability | Calculation of trust value for Drosophila development took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fbdv took 2.7994256019592285s
Availability | SPARQL endpoint availability check for Fly taxonomy took 3.9577484130859375e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.27147412300109863s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.00036263465881347656s
Believability | Calculation of trust value for Fly taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fbsp took 2.849712371826172s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 4.076957702636719e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.0003514289855957031s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.26328372955322266s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.020163297653198242s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00021123886108398438s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fda-meddevice took 2.840505599975586s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.25824761390686035s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0006806850433349609s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0003821849822998047s
Believability | Calculation of trust value for Family Health History Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-fhho took 3.0363597869873047s
Availability | SPARQL endpoint availability check for Influenza Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.24555563926696777s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0009920597076416016s
Believability | Calculation of trust value for Influenza Ontology took 4.649162292480469e-05s
INFO | --- Analysis for bioportal-flu took 2.7510666847229004s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.26490354537963867s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.020589590072631836s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.103515625e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-fma took 2.842677593231201s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.2534067630767822s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.0001304149627685547s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fypo took 2.781099557876587s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.23880529403686523s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.02005910873413086s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.893013000488281e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-geospecies took 2.8459017276763916s
Availability | SPARQL endpoint availability check for General Formal Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0002219676971435547s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.2790830135345459s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.0201566219329834s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.00015974044799804688s
Believability | Calculation of trust value for General Formal Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-gfo took 2.8483312129974365s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 4.100799560546875e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.25556111335754395s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0006778240203857422s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.0005719661712646484s
Believability | Calculation of trust value for General Formal Ontology: Biology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-gfo-bio took 2.8426289558410645s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 7.915496826171875e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.25524330139160156s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.02040386199951172s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.000827789306640625s
Believability | Calculation of trust value for Gene Ontology Extension took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-go_x1 took 2.855088233947754s
Availability | SPARQL endpoint availability check for Gene Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Gene Ontology took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.2635617256164551s
Reputation | Calculation of the PageRank for Gene Ontology took 0.020463228225708008s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008089542388916016s
Believability | Calculation of trust value for Gene Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-go_x2 took 2.842400550842285s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 4.3392181396484375e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.2732365131378174s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 2.8371810913085938e-05s
Believability | Calculation of trust value for Cereal Plant Development took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-gro took 2.906264543533325s
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.00030493736267089844s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.2492048740386963s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.020138025283813477s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.0004215240478515625s
Believability | Calculation of trust value for Cereal plant gross anatomy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-gro_x1 took 2.800511360168457s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 5.030632019042969e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.25399351119995117s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.022740840911865234s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0011258125305175781s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0009219646453857422s
Believability | Calculation of trust value for Gene Regulation Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-gro_x2 took 2.8757529258728027s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.24917387962341309s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005462169647216797s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-hao took 2.8456871509552s
Availability | SPARQL endpoint availability check for HCPCS took 3.933906555175781e-05s
Availability | VoID file availability check for HCPCS took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for HCPCS took 0.2651646137237549s
Reputation | Calculation of the PageRank for HCPCS took 0.020013809204101562s
Interlinking | Calculation of Degree of Connection for HCPCS took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.0002162456512451172s
Believability | Calculation of trust value for HCPCS took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-hcpcs took 2.851670742034912s
Availability | SPARQL endpoint availability check for Health Level Seven took 3.933906555175781e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.27570414543151855s
Reputation | Calculation of the PageRank for Health Level Seven took 0.02108144760131836s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0009942054748535156s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0014264583587646484s
Believability | Calculation of trust value for Health Level Seven took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-hl7 took 2.8905231952667236s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 4.982948303222656e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005850791931152344s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.2748885154724121s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020900487899780273s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003604888916015625s
Believability | Calculation of trust value for HEALTH_INDICATORS took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-hlth_indics took 2.857667922973633s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 3.886222839355469e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.26041460037231445s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.020235538482666016s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 2.7179718017578125e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-hom took 2.8268892765045166s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 4.00543212890625e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.2614481449127197s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.020109891891479492s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 2.7179718017578125e-05s
Believability | Calculation of trust value for HOM-HARVARD took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hom_harvard took 2.8121542930603027s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.26418089866638184s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006124973297119141s
Believability | Calculation of trust value for Human Phenotype Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-hp_x1 took 2.8373942375183105s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.2607417106628418s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.02025747299194336s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010142326354980469s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-hpio took 2.7824487686157227s
Availability | SPARQL endpoint availability check for HUGO took 4.0531158447265625e-05s
Availability | VoID file availability check for HUGO took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for HUGO took 0.28018975257873535s
Reputation | Calculation of the PageRank for HUGO took 0.02007293701171875s
Interlinking | Calculation of Degree of Connection for HUGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.176399230957031e-05s
Believability | Calculation of trust value for HUGO took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-hugo took 2.921426296234131s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.22959256172180176s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006234645843505859s
Believability | Calculation of trust value for Information Artifact Ontology took 5.9604644775390625e-06s
INFO | --- Analysis for bioportal-iao took 2.707871913909912s
Availability | SPARQL endpoint availability check for ICD10 took 3.9577484130859375e-05s
Availability | VoID file availability check for ICD10 took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for ICD10 took 0.25636744499206543s
Reputation | Calculation of the PageRank for ICD10 took 0.020489931106567383s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007956027984619141s
Believability | Calculation of trust value for ICD10 took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-icd10 took 2.799774169921875s
Availability | SPARQL endpoint availability check for ICD10CM took 4.029273986816406e-05s
Availability | VoID file availability check for ICD10CM took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.24079394340515137s
Reputation | Calculation of the PageRank for ICD10CM took 0.020102977752685547s
Interlinking | Calculation of Degree of Connection for ICD10CM took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006074905395507812s
Believability | Calculation of trust value for ICD10CM took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-icd10cm took 2.7103428840637207s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 3.981590270996094e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.24544382095336914s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.020170211791992188s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00017833709716796875s
Believability | Calculation of trust value for ICD-10-PCS took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icd10pcs took 2.725151300430298s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 4.00543212890625e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.2381572723388672s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006377696990966797s
Believability | Calculation of trust value for International Classification of Diseases took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-icd9cm took 2.7534286975860596s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 4.076957702636719e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.2492830753326416s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.020392656326293945s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.00042629241943359375s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-icf_x1 took 2.810624599456787s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 8.296966552734375e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.2650279998779297s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.02020263671875s
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.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012023448944091797s
Believability | Calculation of trust value for International Classification for Nursing Practice took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-icnp took 2.821737051010132s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 4.076957702636719e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.2744920253753662s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020313501358032227s
Interlinking | Calculation of Degree of Connection for International Classification of Primary Care took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for International Classification of Primary Care took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.0004322528839111328s
Believability | Calculation of trust value for International Classification of Primary Care took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-icpc took 2.7925515174865723s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.172325134277344e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.25441932678222656s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0008754730224609375s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0009784698486328125s
Believability | Calculation of trust value for ICPC-2 PLUS took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icpc2p took 2.805243730545044s
Availability | SPARQL endpoint availability check for ICPS Network took 5.841255187988281e-05s
Availability | VoID file availability check for ICPS Network took 0.0004086494445800781s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.25098729133605957s
Reputation | Calculation of the PageRank for ICPS Network took 0.020656585693359375s
Interlinking | Calculation of Degree of Connection for ICPS Network took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ICPS Network took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.00022029876708984375s
Believability | Calculation of trust value for ICPS Network took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-icps took 2.8388326168060303s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.2611818313598633s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0008413791656494141s
Believability | Calculation of trust value for Infectious Disease Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-ido took 2.822309732437134s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.2722208499908447s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0010895729064941406s
Believability | Calculation of trust value for Brucellosis Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-idobru took 2.8406801223754883s
Availability | SPARQL endpoint availability check for Malaria Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Malaria Ontology took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.25454068183898926s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012733936309814453s
Believability | Calculation of trust value for Malaria Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-idomal took 2.8045692443847656s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 4.1484832763671875e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.27869176864624023s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0003094673156738281s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-iev took 2.8165805339813232s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 4.5299530029296875e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.26314806938171387s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020174741744995117s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.000152587890625s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 7.62939453125e-06s
INFO | --- Analysis for bioportal-imgt took 2.8749585151672363s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 4.029273986816406e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.23926496505737305s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.020857572555541992s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0010364055633544922s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0006279945373535156s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 7.62939453125e-06s
INFO | --- Analysis for bioportal-imr took 2.8305559158325195s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.26426124572753906s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.020509004592895508s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0009007453918457031s
Believability | Calculation of trust value for Interaction Network Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-ino took 2.8321194648742676s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.0531158447265625e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.26177096366882324s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 3.0517578125e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-invertebrata took 2.8507134914398193s
Availability | SPARQL endpoint availability check for IxnO took 4.076957702636719e-05s
Availability | VoID file availability check for IxnO took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for IxnO took 0.2669639587402344s
Reputation | Calculation of the PageRank for IxnO took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for IxnO took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.000179290771484375s
Believability | Calculation of trust value for IxnO took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-ixno took 2.8341197967529297s
Availability | SPARQL endpoint availability check for SysMO-JERM took 4.100799560546875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.2394254207611084s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0004725456237792969s
Believability | Calculation of trust value for SysMO-JERM took 7.62939453125e-06s
INFO | --- Analysis for bioportal-jerm took 2.9171876907348633s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.25122928619384766s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 3.886222839355469e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-kisao took 2.7953121662139893s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 4.124641418457031e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.25515294075012207s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00019693374633789062s
Believability | Calculation of trust value for Loggerhead nesting took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-lhn took 2.7935197353363037s
Availability | SPARQL endpoint availability check for Lipid Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.26030492782592773s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.02053976058959961s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00019550323486328125s
Believability | Calculation of trust value for Lipid Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-lipro took 2.892794609069824s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.7206878662109375e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.2783341407775879s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020552396774291992s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.001787424087524414s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-lnc took 2.9249775409698486s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0010068416595458984s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.2532954216003418s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020847797393798828s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006535053253173828s
Believability | Calculation of trust value for Mouse adult gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-ma took 2.8250277042388916s
Availability | SPARQL endpoint availability check for Multiple alignment took 7.128715515136719e-05s
Availability | VoID file availability check for Multiple alignment took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.24872350692749023s
Reputation | Calculation of the PageRank for Multiple alignment took 0.020099639892578125s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019311904907226562s
Believability | Calculation of trust value for Multiple alignment took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mao took 2.7593328952789307s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 4.100799560546875e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0003769397735595703s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.23751139640808105s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006995201110839844s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.3828277587890625e-05s
INFO | --- Analysis for bioportal-mat took 2.8048295974731445s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 3.933906555175781e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.26908016204833984s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0003993511199951172s
Believability | Calculation of trust value for Breast tissue cell lines took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mcbcc took 2.835832357406616s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cell line ontology took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.26119494438171387s
Reputation | Calculation of the PageRank for Cell line ontology took 0.0202639102935791s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0007481575012207031s
Believability | Calculation of trust value for Cell line ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mccl took 2.8090059757232666s
Availability | SPARQL endpoint availability check for Cell line ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Cell line ontology took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.25944972038269043s
Reputation | Calculation of the PageRank for Cell line ontology took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.00139617919921875s
Believability | Calculation of trust value for Cell line ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mccl_x1 took 2.8979909420013428s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 4.124641418457031e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.2643907070159912s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02030038833618164s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.0002396106719970703s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mcv took 2.8033201694488525s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 3.981590270996094e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0003249645233154297s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.26682448387145996s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0006806850433349609s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.00017786026000976562s
Believability | Calculation of trust value for Master Drug Data Base took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mddb took 2.8164799213409424s
Availability | SPARQL endpoint availability check for MedDRA took 3.981590270996094e-05s
Availability | VoID file availability check for MedDRA took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for MedDRA took 0.2456378936767578s
Reputation | Calculation of the PageRank for MedDRA took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for MedDRA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011277198791503906s
Believability | Calculation of trust value for MedDRA took 7.62939453125e-06s
INFO | --- Analysis for bioportal-mdr took 2.7360289096832275s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.1484832763671875e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.000308990478515625s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.23656845092773438s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.00087738037109375s
Believability | Calculation of trust value for MedlinePlus Health Topics took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-medlineplus took 2.8321127891540527s
Availability | SPARQL endpoint availability check for MeGO took 5.340576171875e-05s
Availability | VoID file availability check for MeGO took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for MeGO took 0.26191258430480957s
Reputation | Calculation of the PageRank for MeGO took 0.02029132843017578s
Interlinking | Calculation of Degree of Connection for MeGO took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MeGO took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.0001404285430908203s
Believability | Calculation of trust value for MeGO took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mego took 2.7977116107940674s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 4.124641418457031e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.25610947608947754s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.020220041275024414s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0006766319274902344s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0017673969268798828s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-mesh-owl took 2.805293560028076s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.2509613037109375s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0005931854248046875s
Believability | Calculation of trust value for Mental Functioning Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mf took 2.88985538482666s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 4.0531158447265625e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.23789381980895996s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.020481109619140625s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0009796619415283203s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0006239414215087891s
Believability | Calculation of trust value for Medaka fish anatomy and development took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mfo took 2.841270923614502s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2616302967071533s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007462501525878906s
Believability | Calculation of trust value for Emotion Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-mfoem took 2.822023868560791s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.265700101852417s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.02038431167602539s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006773471832275391s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 9.775161743164062e-05s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-mhc took 2.824709415435791s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 3.933906555175781e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.00035190582275390625s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.2578918933868408s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0007724761962890625s
Believability | Calculation of trust value for Protein-protein interaction took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-mi took 2.838491678237915s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 4.267692565917969e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.2524409294128418s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0006909370422363281s
Believability | Calculation of trust value for Mosquito insecticide resistance took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-miro took 2.864400625228882s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.25042295455932617s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.019925355911254883s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013494491577148438s
Believability | Calculation of trust value for Measurement Method Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-mmo took 2.8360981941223145s
Availability | SPARQL endpoint availability check for MGED Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for MGED Ontology took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.25418949127197266s
Reputation | Calculation of the PageRank for MGED Ontology took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.000370025634765625s
Believability | Calculation of trust value for MGED Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mo took 2.7459070682525635s
Availability | SPARQL endpoint availability check for Protein modification took 6.0558319091796875e-05s
Availability | VoID file availability check for Protein modification took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Protein modification took 0.27272510528564453s
Reputation | Calculation of the PageRank for Protein modification took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Protein modification took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Protein modification took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00021767616271972656s
Believability | Calculation of trust value for Protein modification took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-mod took 2.883981227874756s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 4.076957702636719e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.26300501823425293s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006532669067382812s
Believability | Calculation of trust value for Mammalian phenotype took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-mp took 2.8529064655303955s
Availability | SPARQL endpoint availability check for Mouse pathology took 3.981590270996094e-05s
Availability | VoID file availability check for Mouse pathology took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.24724125862121582s
Reputation | Calculation of the PageRank for Mouse pathology took 0.02046513557434082s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00046706199645996094s
Believability | Calculation of trust value for Mouse pathology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mpath took 2.8098998069763184s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.506111145019531e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.2661123275756836s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.02388739585876465s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.001260519027709961s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.0004839897155761719s
Believability | Calculation of trust value for Mass spectrometry took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ms took 2.932034730911255s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 4.124641418457031e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.2707085609436035s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.0019307136535644531s
Believability | Calculation of trust value for Medical Subject Headings took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-msh took 2.8486104011535645s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.076957702636719e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.25356388092041016s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.020251989364624023s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017213821411132812s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mthch took 2.8130178451538086s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.27625060081481934s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.02059006690979004s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0008168220520019531s
Believability | Calculation of trust value for Natural Products Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-natpro took 2.851567506790161s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 4.124641418457031e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.2634146213531494s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008192062377929688s
Believability | Calculation of trust value for NCBI organismal classification took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 2.899229049682617s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 0.00016736984252929688s
Availability | VoID file availability check for NCI Thesaurus took 0.00037670135498046875s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.26414918899536133s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.0019173622131347656s
Believability | Calculation of trust value for NCI Thesaurus took 5.7220458984375e-06s
INFO | --- Analysis for bioportal-ncit took 2.8521246910095215s
Availability | SPARQL endpoint availability check for National Drug Data File took 3.9577484130859375e-05s
Availability | VoID file availability check for National Drug Data File took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.2635807991027832s
Reputation | Calculation of the PageRank for National Drug Data File took 0.02030038833618164s
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.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0005948543548583984s
Believability | Calculation of trust value for National Drug Data File took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-nddf took 2.840877056121826s
Availability | SPARQL endpoint availability check for National Drug File took 4.076957702636719e-05s
Availability | VoID file availability check for National Drug File took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for National Drug File took 0.27159595489501953s
Reputation | Calculation of the PageRank for National Drug File took 0.02300572395324707s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0010600090026855469s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.00136566162109375s
Believability | Calculation of trust value for National Drug File took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ndfrt took 3.045844078063965s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 4.029273986816406e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.23684072494506836s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.001094818115234375s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-nemo_x1 took 2.809779167175293s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 3.910064697265625e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.24877476692199707s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.020045757293701172s
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.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006208419799804688s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-neomark took 2.82593035697937s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0002143383026123047s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.2797257900238037s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.019982099533081055s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00011372566223144531s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.9097509384155273s
Availability | SPARQL endpoint availability check for NIFSTD took 4.0531158447265625e-05s
Availability | VoID file availability check for NIFSTD took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.25483202934265137s
Reputation | Calculation of the PageRank for NIFSTD took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for NIFSTD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0006785392761230469s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018231868743896484s
Believability | Calculation of trust value for NIFSTD took 3.123283386230469e-05s
INFO | --- Analysis for bioportal-nif took 2.8309249877929688s
Availability | SPARQL endpoint availability check for NIF Cell took 4.0531158447265625e-05s
Availability | VoID file availability check for NIF Cell took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.25234389305114746s
Reputation | Calculation of the PageRank for NIF Cell took 0.020079851150512695s
Interlinking | Calculation of Degree of Connection for NIF Cell took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.001298666000366211s
Believability | Calculation of trust value for NIF Cell took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-nif_cell took 2.758479356765747s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 5.412101745605469e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.24456095695495605s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.021428585052490234s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0014729499816894531s
Believability | Calculation of trust value for NIF Dysfunction took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.8476953506469727s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.2657163143157959s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.020171165466308594s
Interlinking | Calculation of Degree of Connection for Neural-Immune Gene Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neural-Immune Gene Ontology took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005428791046142578s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-nigo took 2.9017083644866943s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 4.0531158447265625e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.25515270233154297s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0005199909210205078s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-nmr took 2.8683013916015625s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.26432347297668457s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010251998901367188s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-nonrctontology took 2.912250280380249s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.25998735427856445s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.02045273780822754s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.001150369644165039s
Believability | Calculation of trust value for NanoParticle Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-npo took 2.8444550037384033s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.24999547004699707s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0007100105285644531s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-oae took 2.804321050643921s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 4.029273986816406e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.2895791530609131s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.020029783248901367s
Interlinking | Calculation of Degree of Connection for Ontology for Biomedical Investigations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ontology for Biomedical Investigations took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.00142669677734375s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-obi took 2.880965232849121s
Availability | SPARQL endpoint availability check for OBOE took 4.0531158447265625e-05s
Availability | VoID file availability check for OBOE took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for OBOE took 0.25989460945129395s
Reputation | Calculation of the PageRank for OBOE took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for OBOE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.00010514259338378906s
Believability | Calculation of trust value for OBOE took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-oboe took 2.747636556625366s
Availability | SPARQL endpoint availability check for OBOE SBC took 4.0531158447265625e-05s
Availability | VoID file availability check for OBOE SBC took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.2667248249053955s
Reputation | Calculation of the PageRank for OBOE SBC took 0.019975900650024414s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0007462501525878906s
Believability | Calculation of trust value for OBOE SBC took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-oboe-sbc took 2.8756771087646484s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.1961669921875e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.2637913227081299s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005631446838378906s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-ocre took 2.835538148880005s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 4.029273986816406e-05s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.23949599266052246s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008151531219482422s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-odgi took 2.8065242767333984s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 5.078315734863281e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.2595713138580322s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02020120620727539s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0008518695831298828s
Believability | Calculation of trust value for Ontology for Genetic Interval took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ogi took 2.876879930496216s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 4.076957702636719e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.2328641414642334s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020489215850830078s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00029540061950683594s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-ogmd took 2.747002601623535s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 3.886222839355469e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.2602860927581787s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006589889526367188s
Believability | Calculation of trust value for Ontology for General Medical Science took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-ogms took 2.8443169593811035s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 4.1484832763671875e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.26305103302001953s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020308494567871094s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.00113677978515625s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-omim took 2.8303380012512207s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.601478576660156e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.26545190811157227s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.0003952980041503906s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-omit took 2.871136426925659s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 0.0005593299865722656s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.2640645503997803s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005738735198974609s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-omrse took 2.8317224979400635s
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.0002601146697998047s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.24577021598815918s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007734298706054688s
Believability | Calculation of trust value for Ontology of Data Mining took 7.62939453125e-06s
INFO | --- Analysis for bioportal-ontodm took 2.8116061687469482s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.2641935348510742s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.020807743072509766s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.0002598762512207031s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-ontodt took 2.852691650390625s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 8.606910705566406e-05s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.0002989768981933594s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.2722964286804199s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020247697830200195s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0006151199340820312s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-ontoorpha took 2.855708122253418s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0006070137023925781s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.25295400619506836s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0009658336639404297s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.001035928726196289s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-opl took 2.9739301204681396s
Availability | SPARQL endpoint availability check for Phenotypic quality took 4.076957702636719e-05s
Availability | VoID file availability check for Phenotypic quality took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.2523798942565918s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008423328399658203s
Believability | Calculation of trust value for Phenotypic quality took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pato took 2.812781810760498s
Availability | SPARQL endpoint availability check for Physician Data Query took 4.076957702636719e-05s
Availability | VoID file availability check for Physician Data Query took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.24491620063781738s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Physician Data Query took 0.00081634521484375s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0009207725524902344s
Believability | Calculation of trust value for Physician Data Query took 9.059906005859375e-06s
INFO | --- Analysis for bioportal-pdq took 2.8106236457824707s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 4.1484832763671875e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.26337194442749023s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0008335113525390625s
Believability | Calculation of trust value for Pediatric Terminology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-pedterm took 2.912346601486206s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.00038051605224609375s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.26040053367614746s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.00019669532775878906s
Believability | Calculation of trust value for Parasite Experiment Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-peo took 2.8608152866363525s
Availability | SPARQL endpoint availability check for PHARE took 4.0531158447265625e-05s
Availability | VoID file availability check for PHARE took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for PHARE took 0.22919797897338867s
Reputation | Calculation of the PageRank for PHARE took 0.020612716674804688s
Interlinking | Calculation of Degree of Connection for PHARE took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for PHARE took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006229877471923828s
Believability | Calculation of trust value for PHARE took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-phare took 2.837069034576416s
Availability | SPARQL endpoint availability check for PKO_Re took 4.100799560546875e-05s
Availability | VoID file availability check for PKO_Re took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.2395944595336914s
Reputation | Calculation of the PageRank for PKO_Re took 0.02071857452392578s
Interlinking | Calculation of Degree of Connection for PKO_Re took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for PKO_Re took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.0001857280731201172s
Believability | Calculation of trust value for PKO_Re took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-pko took 2.8498172760009766s
Availability | SPARQL endpoint availability check for PMA 2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for PMA 2010 took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.25658226013183594s
Reputation | Calculation of the PageRank for PMA 2010 took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0009119510650634766s
Believability | Calculation of trust value for PMA 2010 took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-pma took 2.865196466445923s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 4.076957702636719e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.26512718200683594s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020487070083618164s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00019073486328125s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-pmr took 2.8313252925872803s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.034706115722656e-05s
Availability | VoID file availability check for Plant Anatomy took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.24966692924499512s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038361549377441406s
Believability | Calculation of trust value for Plant Anatomy took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-po took 2.8855409622192383s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 4.3392181396484375e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.2764167785644531s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.02027606964111328s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 6.842613220214844e-05s
Believability | Calculation of trust value for Plant Growth and Development Stage took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-po_x1 took 2.827016592025757s
Availability | SPARQL endpoint availability check for Plant Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Plant Ontology took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.2627387046813965s
Reputation | Calculation of the PageRank for Plant Ontology took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.00044536590576171875s
Believability | Calculation of trust value for Plant Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-po_x2 took 2.8499972820281982s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 4.076957702636719e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.25043511390686035s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006518363952636719s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-pr took 2.824573040008545s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.029273986816406e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.23761558532714844s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02031254768371582s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0002491474151611328s
Believability | Calculation of trust value for Proteomics data and process provenance took 1.811981201171875e-05s
INFO | --- Analysis for bioportal-propreo took 2.9198296070098877s
Availability | SPARQL endpoint availability check for Pathway ontology took 3.886222839355469e-05s
Availability | VoID file availability check for Pathway ontology took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.239241361618042s
Reputation | Calculation of the PageRank for Pathway ontology took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.0001270771026611328s
Believability | Calculation of trust value for Pathway ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-pw took 2.807823419570923s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.00038743019104003906s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.2645289897918701s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-qibo took 2.850135564804077s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.506111145019531e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.2393033504486084s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.02043628692626953s
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.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0019237995147705078s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 7.62939453125e-06s
INFO | --- Analysis for bioportal-rcd took 2.810697078704834s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 5.245208740234375e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.2544841766357422s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.02049541473388672s
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.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.00012683868408203125s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-rctontology took 2.7788338661193848s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.291534423828125e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.279343843460083s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 9.703636169433594e-05s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-repo took 2.8669464588165283s
Availability | SPARQL endpoint availability check for Physico-chemical process took 3.9577484130859375e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.2515099048614502s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020544767379760742s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.00019669532775878906s
Believability | Calculation of trust value for Physico-chemical process took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-rex took 2.854846477508545s
Availability | SPARQL endpoint availability check for RadLex took 4.124641418457031e-05s
Availability | VoID file availability check for RadLex took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for RadLex took 0.2709958553314209s
Reputation | Calculation of the PageRank for RadLex took 0.020372867584228516s
Interlinking | Calculation of Degree of Connection for RadLex took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RadLex took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.001523733139038086s
Believability | Calculation of trust value for RadLex took 8.821487426757812e-06s
INFO | --- Analysis for bioportal-rid took 2.8209619522094727s
Availability | SPARQL endpoint availability check for RNA ontology took 4.029273986816406e-05s
Availability | VoID file availability check for RNA ontology took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.2593529224395752s
Reputation | Calculation of the PageRank for RNA ontology took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for RNA ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.000537872314453125s
Believability | Calculation of trust value for RNA ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-rnao took 2.7545714378356934s
Availability | SPARQL endpoint availability check for Role Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Role Ontology took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.23551726341247559s
Reputation | Calculation of the PageRank for Role Ontology took 0.020616769790649414s
Interlinking | Calculation of Degree of Connection for Role Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Role Ontology took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00019407272338867188s
Believability | Calculation of trust value for Role Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-roleo took 2.745898723602295s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.24025821685791016s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020150423049926758s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.00017452239990234375s
Believability | Calculation of trust value for Rat Strain Ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-rs took 2.7418179512023926s
Availability | SPARQL endpoint availability check for RxNORM took 4.2438507080078125e-05s
Availability | VoID file availability check for RxNORM took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for RxNORM took 0.2365560531616211s
Reputation | Calculation of the PageRank for RxNORM took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for RxNORM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for RxNORM took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006186962127685547s
Believability | Calculation of trust value for RxNORM took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-rxnorm took 2.779960870742798s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 4.00543212890625e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.00028967857360839844s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.2911522388458252s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.02036452293395996s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010132789611816406s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-sao took 2.8281776905059814s
Availability | SPARQL endpoint availability check for Systems Biology took 4.100799560546875e-05s
Availability | VoID file availability check for Systems Biology took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.24927473068237305s
Reputation | Calculation of the PageRank for Systems Biology took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for Systems Biology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004570484161376953s
Believability | Calculation of trust value for Systems Biology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sbo took 2.7940168380737305s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.2625911235809326s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02003622055053711s
Interlinking | Calculation of Degree of Connection for Smoking Behavior Risk Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Smoking Behavior Risk Ontology took 0.0006806850433349609s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 9.870529174804688e-05s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-sbro took 2.8229386806488037s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.25370168685913086s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020204544067382812s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.0012843608856201172s
Believability | Calculation of trust value for Sleep Domain Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-sdo took 3.01324462890625s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 4.0531158447265625e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.2763075828552246s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02036142349243164s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.00032639503479003906s
Believability | Calculation of trust value for Sample processing and separation techniques took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-sep took 2.903287887573242s
Availability | SPARQL endpoint availability check for Student Health Record took 4.076957702636719e-05s
Availability | VoID file availability check for Student Health Record took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.2665064334869385s
Reputation | Calculation of the PageRank for Student Health Record took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004417896270751953s
Believability | Calculation of trust value for Student Health Record took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-shr took 2.848942518234253s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 6.508827209472656e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.24840688705444336s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.01998424530029297s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012238025665283203s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-sio took 2.829061985015869s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 3.8623809814453125e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0003025531768798828s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.2537386417388916s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.020986318588256836s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019478797912597656s
Believability | Calculation of trust value for Situation-Based Access Control took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-sitbac took 2.8177151679992676s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 4.506111145019531e-05s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.24893975257873535s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0018532276153564453s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-snomedct took 2.7894089221954346s
Availability | SPARQL endpoint availability check for SNP-Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.2562894821166992s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006725788116455078s
Believability | Calculation of trust value for SNP-Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-snpo took 2.842620611190796s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.00543212890625e-05s
Availability | VoID file availability check for Sequence types and features took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.2443561553955078s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020211219787597656s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0006358623504638672s
Believability | Calculation of trust value for Sequence types and features took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-so_x1 took 2.8305578231811523s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.0531158447265625e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.000244140625s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.2756943702697754s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for Suggested Ontology for Pharmacogenomics took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Suggested Ontology for Pharmacogenomics took 0.0006792545318603516s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015380382537841797s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 7.62939453125e-06s
INFO | --- Analysis for bioportal-sopharm took 2.8324813842773438s
Availability | SPARQL endpoint availability check for SoyOntology took 3.981590270996094e-05s
Availability | VoID file availability check for SoyOntology took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.2527580261230469s
Reputation | Calculation of the PageRank for SoyOntology took 0.020450353622436523s
Interlinking | Calculation of Degree of Connection for SoyOntology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for SoyOntology took 0.0008821487426757812s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.00014853477478027344s
Believability | Calculation of trust value for SoyOntology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-soy took 2.8649871349334717s
Availability | SPARQL endpoint availability check for Spider Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Spider Ontology took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.25289344787597656s
Reputation | Calculation of the PageRank for Spider Ontology took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Spider Ontology took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00034165382385253906s
Believability | Calculation of trust value for Spider Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-spd took 2.8755438327789307s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.2556908130645752s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.0202329158782959s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00027251243591308594s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-spto took 2.8665146827697754s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.26568603515625s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.020273685455322266s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.00043773651123046875s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-sso took 2.825423240661621s
Availability | SPARQL endpoint availability check for Software Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Software Ontology took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.2534613609313965s
Reputation | Calculation of the PageRank for Software Ontology took 0.020287275314331055s
Interlinking | Calculation of Degree of Connection for Software Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00041365623474121094s
Believability | Calculation of trust value for Software Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-swo took 2.778413772583008s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 3.981590270996094e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.2720801830291748s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.020084381103515625s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023174285888671875s
Believability | Calculation of trust value for Tick gross anatomy took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tads took 2.7854411602020264s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 5.221366882324219e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.278287410736084s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.020844221115112305s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0009338855743408203s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tao took 2.932482957839966s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.24689126014709473s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 0.0001163482666015625s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-taxrank took 2.8728420734405518s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 4.220008850097656e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.25441837310791016s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.02180767059326172s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0011546611785888672s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 9.632110595703125e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 8.58306884765625e-06s
INFO | --- Analysis for bioportal-teddy took 2.8227648735046387s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0003314018249511719s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.24984192848205566s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.020196199417114258s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0008120536804199219s
Believability | Calculation of trust value for Time Event Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-teo took 2.896077871322632s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 8.58306884765625e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.24869680404663086s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00037670135498046875s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-tgma took 2.8285701274871826s
Availability | SPARQL endpoint availability check for thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for thesaurus took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for thesaurus took 0.24620437622070312s
Reputation | Calculation of the PageRank for thesaurus took 0.020425796508789062s
Interlinking | Calculation of Degree of Connection for thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for thesaurus took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for thesaurus took 7.152557373046875e-05s
Believability | Calculation of trust value for thesaurus took 7.62939453125e-06s
INFO | --- Analysis for bioportal-thesaurus took 2.7550277709960938s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 4.100799560546875e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.25656867027282715s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003330707550048828s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 7.62939453125e-06s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.857189178466797s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 4.315376281738281e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.2686183452606201s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0007946491241455078s
Believability | Calculation of trust value for Translational Medicine Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-tmo took 3.0554022789001465s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.25988030433654785s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.0001518726348876953s
Believability | Calculation of trust value for Plant Trait Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-to took 2.885159969329834s
Availability | SPARQL endpoint availability check for TOK_Ontology took 5.14984130859375e-05s
Availability | VoID file availability check for TOK_Ontology took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.2471327781677246s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00017333030700683594s
Believability | Calculation of trust value for TOK_Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-tok took 2.8449902534484863s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 3.9577484130859375e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.2542283535003662s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00018477439880371094s
Believability | Calculation of trust value for Teleost taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-tto took 2.8201470375061035s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 5.269050598144531e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.23798727989196777s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.001064300537109375s
Believability | Calculation of trust value for Uber anatomy ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-uberon took 2.817640542984009s
Availability | SPARQL endpoint availability check for Units Ontology took 3.910064697265625e-05s
Availability | VoID file availability check for Units Ontology took 0.0003330707550048828s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.24930667877197266s
Reputation | Calculation of the PageRank for Units Ontology took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.0002243518829345703s
Believability | Calculation of trust value for Units Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-unitsontology took 2.839712142944336s
Availability | SPARQL endpoint availability check for Units of measurement took 4.00543212890625e-05s
Availability | VoID file availability check for Units of measurement took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.23204803466796875s
Reputation | Calculation of the PageRank for Units of measurement took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for Units of measurement took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00028252601623535156s
Believability | Calculation of trust value for Units of measurement took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-uo took 2.845703601837158s
Availability | SPARQL endpoint availability check for VANDF took 4.029273986816406e-05s
Availability | VoID file availability check for VANDF took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for VANDF took 0.25009751319885254s
Reputation | Calculation of the PageRank for VANDF took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for VANDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.000652313232421875s
Believability | Calculation of trust value for VANDF took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-vandf took 2.8844797611236572s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.2893362045288086s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020936250686645508s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.00043201446533203125s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-vao took 2.8646631240844727s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 0.00012183189392089844s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.00022149085998535156s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.24999117851257324s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.02032184600830078s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006000995635986328s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 6.198883056640625e-06s
INFO | --- Analysis for bioportal-vhog took 2.8549578189849854s
Availability | SPARQL endpoint availability check for VIVO took 4.029273986816406e-05s
Availability | VoID file availability check for VIVO took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for VIVO took 0.2762150764465332s
Reputation | Calculation of the PageRank for VIVO took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for VIVO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.00033211708068847656s
Believability | Calculation of trust value for VIVO took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-vivo took 2.844835042953491s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.24274921417236328s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012183189392089844s
Believability | Calculation of trust value for Vaccine Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-vo took 2.811920166015625s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.24209070205688477s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02024674415588379s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.00020694732666015625s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-vt took 2.782066583633423s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.172325134277344e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.2733948230743408s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.0203094482421875s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.00048065185546875s
Believability | Calculation of trust value for C. elegans gross anatomy took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-wbbt took 2.8490004539489746s
Availability | SPARQL endpoint availability check for C. elegans development took 3.933906555175781e-05s
Availability | VoID file availability check for C. elegans development took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.27215147018432617s
Reputation | Calculation of the PageRank for C. elegans development took 0.02019667625427246s
Interlinking | Calculation of Degree of Connection for C. elegans development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.220008850097656e-05s
Believability | Calculation of trust value for C. elegans development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-wbls took 2.9149563312530518s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 3.9577484130859375e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.2602393627166748s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.630752563476562e-05s
Believability | Calculation of trust value for C. elegans phenotype took 6.67572021484375e-06s
INFO | --- Analysis for bioportal-wbphenotype took 2.8477272987365723s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 4.100799560546875e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.2559163570404053s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.020380020141601562s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005698204040527344s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-who took 2.7399728298187256s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 3.981590270996094e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.24847102165222168s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.020239591598510742s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006880760192871094s
Believability | Calculation of trust value for Xenopus anatomy and development took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-xao took 2.8356072902679443s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.2607147693634033s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.020494699478149414s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.000263214111328125s
Believability | Calculation of trust value for Experimental Conditions Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-xco took 2.833571434020996s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 5.14984130859375e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.2662200927734375s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.021082162857055664s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.00027942657470703125s
Believability | Calculation of trust value for Yeast phenotypes took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-ypo took 2.818798065185547s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 4.1961669921875e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.2776072025299072s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007696151733398438s
Believability | Calculation of trust value for Zebrafish anatomy and development took 7.62939453125e-06s
INFO | --- Analysis for bioportal-zfa took 2.8557279109954834s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 4.363059997558594e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.2594575881958008s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020186662673950195s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1920928955078125e-05s
INFO | --- Analysis for Bioportal_link took 2.8186702728271484s
Availability | SPARQL endpoint availability check for BioSamples RDF took 3.981590270996094e-05s
Availability | VoID file availability check for BioSamples RDF took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.27208662033081055s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020264863967895508s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.0994415283203125e-05s
Believability | Calculation of trust value for BioSamples RDF took 9.059906005859375e-06s
INFO | --- Analysis for biosamples-rdf took 2.8245015144348145s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 4.100799560546875e-05s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.2643752098083496s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00013113021850585938s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for bis-linked-data took 2.8925886154174805s
Availability | SPARQL endpoint availability check for Bitzi took 3.886222839355469e-05s
Availability | VoID file availability check for Bitzi took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Bitzi took 0.2687556743621826s
Reputation | Calculation of the PageRank for Bitzi took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for Bitzi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.7179718017578125e-05s
Believability | Calculation of trust value for Bitzi took 1.0967254638671875e-05s
INFO | --- Analysis for bitzi took 2.802680015563965s
Availability | SPARQL endpoint availability check for BizkaiSense took 5.340576171875e-05s
Availability | VoID file availability check for BizkaiSense took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.27739620208740234s
Reputation | Calculation of the PageRank for BizkaiSense took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 3.0994415283203125e-05s
Believability | Calculation of trust value for BizkaiSense took 7.152557373046875e-06s
INFO | --- Analysis for bizkaisense took 2.956388235092163s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.029273986816406e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.24453353881835938s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.8371810913085938e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.152557373046875e-06s
INFO | --- Analysis for blabla-itemlist took 2.7734603881835938s
Availability | SPARQL endpoint availability check for blabla.itemlist took 4.0531158447265625e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.2461857795715332s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02008342742919922s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.86102294921875e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.152557373046875e-06s
INFO | --- Analysis for blabla_itemlist took 2.7675538063049316s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.2513589859008789s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.02001476287841797s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 4.220008850097656e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for bll-thesaurus took 2.840747117996216s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.296281337738037s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.23430776596069336s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02010798454284668s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.29425048828125e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 3.1948089599609375e-05s
INFO | --- Analysis for bluk-bnb took 4.291783571243286s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.24459528923034668s
Availability | VoID file availability check for Thesaurus BNCF took 0.0006639957427978516s
Extra | Recovery of all triples for Thesaurus BNCF took 45.96479368209839s
Performance | Total latancy measurement for Thesaurus BNCF took 0.6186611652374268s
Amount of data | Number of triples check for Thesaurus BNCF took 0.5945842266082764s
Interoperability | New terms check for Thesaurus BNCF took 1.8292195796966553s
Versatility | Languages check for Thesaurus BNCF took 7.281319856643677s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.9286658763885498s
Security | Check HTTPS for Thesaurus BNCF took 0.10687971115112305s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1008157730102539s
Versatility | Serialization formats check for Thesaurus BNCF took 0.10171699523925781s
Availability | RDF dump link check for Thesaurus BNCF took 0.10194873809814453s
License | MR license check for Thesaurus BNCF took 0.10430192947387695s
License | HR license check for Thesaurus BNCF took 0.18297123908996582s
Amount of data | Number of property check for Thesaurus BNCF took 0.10367798805236816s
Understandability | Number of label check for Thesaurus BNCF took 0.2925221920013428s
Understandability | URI regex check for Thesaurus BNCF took 0.18340659141540527s
Understandability | Vocabs check for Thesaurus BNCF took 0.09761524200439453s
Verifiability | Authors check for Thesaurus BNCF took 0.09405779838562012s
Verifiability | Publishers check for Thesaurus BNCF took 0.10210490226745605s
Performance | Throughput check for Thesaurus BNCF took 11.117571353912354s
Amount of data | Check the number of entities for Thesaurus BNCF took 0.00011205673217773438s
Verifiability | Contribs. check for Thesaurus BNCF took 0.09536170959472656s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.09187030792236328s
Interlinking | skos check for Thesaurus BNCF took 0.1420445442199707s
Interlinking | skos check for Thesaurus BNCF took 0.14409780502319336s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.10175752639770508s
Currency | Creation date check for Thesaurus BNCF took 0.1928691864013672s
Currency | Modification date check for Thesaurus BNCF took 0.19841861724853516s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.955071926116943s
Interoperability | New vocabularies check for Thesaurus BNCF took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.13221216201782227s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.09719657897949219s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.08610820770263672s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 12.08189868927002s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.5074563026428223s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.8820598125457764s
Consistency | Disjoint class check for Thesaurus BNCF took 0.10728907585144043s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.994758129119873s
Consistency | Misplaced classes for Thesaurus BNCF took 6.679407596588135s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 8.52454161643982s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.4867122173309326s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.4795353412628174s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.416069507598877s
Security | Sign check for Thesaurus BNCF took 0.10098433494567871s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.087608337402344s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.3003544807434082s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.019825458526611328s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.747245788574219e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.1920928955078125e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 7.867813110351562e-06s
INFO | --- Analysis for bncf-ns took 179.21512293815613s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.124641418457031e-05s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.2568666934967041s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.02039957046508789s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0009064674377441406s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 4.3392181396484375e-05s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.775161743164062e-06s
INFO | --- Analysis for bpr took 2.8362889289855957s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.00543212890625e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.26738953590393066s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.020374536514282227s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.009506225585938e-05s
Believability | Calculation of trust value for Brazilian Politicians took 7.3909759521484375e-06s
INFO | --- Analysis for brazilian-politicians took 2.841160535812378s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.076957702636719e-05s
Availability | VoID file availability check for BrazilianCities took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.2689518928527832s
Reputation | Calculation of the PageRank for BrazilianCities took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 3.0040740966796875e-05s
Believability | Calculation of trust value for BrazilianCities took 6.67572021484375e-06s
INFO | --- Analysis for braziliancities took 2.8978891372680664s
Availability | SPARQL endpoint availability check for Bricklink took 4.291534423828125e-05s
Availability | VoID file availability check for Bricklink took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for Bricklink took 0.25333189964294434s
Reputation | Calculation of the PageRank for Bricklink took 0.020267009735107422s
Interlinking | Calculation of Degree of Connection for Bricklink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bricklink took 0.0007712841033935547s
Interlinking | Calculation of Clustering coefficient for Bricklink took 7.581710815429688e-05s
Believability | Calculation of trust value for Bricklink took 1.1205673217773438e-05s
INFO | --- Analysis for bricklink took 2.8549115657806396s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.159115314483643s
Availability | VoID file availability check for British Museum Collection took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.2536277770996094s
Reputation | Calculation of the PageRank for British Museum Collection took 0.02004241943359375s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.86102294921875e-05s
Believability | Calculation of trust value for British Museum Collection took 7.3909759521484375e-06s
INFO | --- Analysis for british-museum-collection took 63.16033697128296s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 4.1484832763671875e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.2422349452972412s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.02057051658630371s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0008440017700195312s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 4.482269287109375e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.621246337890625e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.8453381061553955s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 4.220008850097656e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.25754475593566895s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.7894973754882812e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 8.58306884765625e-06s
INFO | --- Analysis for bsv took 2.9114794731140137s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 4.172325134277344e-05s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.2344226837158203s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0202023983001709s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3589859008789062e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.1205673217773438e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 2.7431161403656006s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 4.029273986816406e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.2640376091003418s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0008940696716308594s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 4.1961669921875e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.0728836059570312e-05s
INFO | --- Analysis for bund-offener-haushalt took 2.833374500274658s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 4.1961669921875e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0003223419189453125s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.2418205738067627s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.020148277282714844s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.1948089599609375e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 6.9141387939453125e-06s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.8974151611328125s
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.0002346038818359375s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.2449941635131836s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.020204544067382812s
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.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.673004150390625e-05s
Believability | Calculation of trust value for business.data.gov.uk took 7.62939453125e-06s
INFO | --- Analysis for business-data-gov-uk took 2.798616886138916s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4221644401550293s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0002961158752441406s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 1.9932973384857178s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.8192377090454102s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.3716561794281006s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.8022630214691162s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 43.76491665840149s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.30720949172973633s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.17180299758911133s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.3981657028198242s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.2572181224822998s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.25075602531433105s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.328275203704834s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 20.60676336288452s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.32517528533935547s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.6566011905670166s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.5575063228607178s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.2967240810394287s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.33842968940734863s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.3420379161834717s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.136255264282227s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 7.271766662597656e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2954277992248535s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.29196882247924805s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.3605794906616211s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.29009556770324707s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.30118775367736816s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.6480224132537842s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5948746204376221s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.188708066940308s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.2923440933227539s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4296426773071289s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4282970428466797s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 2.4966137409210205s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.03395700454711914s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.027430057525634766s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.32977938652038574s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.3742470741271973s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.33553123474121094s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 3.409201145172119s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.3646557331085205s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.478231191635132s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.031175851821899414s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.2631549835205078s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.25463032722473145s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1299.7127783298492s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 1.422435998916626s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02203083038330078s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0008022785186767578s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 0.00014352798461914062s
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 7.152557373046875e-06s
INFO | --- Analysis for BVMC took 1439.0766894817352s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 4.0531158447265625e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.260866641998291s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 7.3909759521484375e-06s
INFO | --- Analysis for cabbage took 3.176914691925049s
Availability | SPARQL endpoint availability check for cablegate took 4.076957702636719e-05s
Availability | VoID file availability check for cablegate took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for cablegate took 0.23399591445922852s
Reputation | Calculation of the PageRank for cablegate took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for cablegate took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.461143493652344e-05s
Believability | Calculation of trust value for cablegate took 1.1682510375976562e-05s
INFO | --- Analysis for cablegate took 3.1907262802124023s
Availability | SPARQL endpoint availability check for Calames took 4.220008850097656e-05s
Availability | VoID file availability check for Calames took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Calames took 0.26168322563171387s
Reputation | Calculation of the PageRank for Calames took 0.02015233039855957s
Interlinking | Calculation of Degree of Connection for Calames took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Calames took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Calames took 3.504753112792969e-05s
Believability | Calculation of trust value for Calames took 7.62939453125e-06s
INFO | --- Analysis for calames took 2.892914295196533s
Availability | SPARQL endpoint availability check for CaLiGraph took 4.1961669921875e-05s
Availability | VoID file availability check for CaLiGraph took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.27317166328430176s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02016615867614746s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0006825923919677734s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 2.7179718017578125e-05s
Believability | Calculation of trust value for CaLiGraph took 1.1920928955078125e-05s
INFO | --- Analysis for CaLiGraph took 2.8815982341766357s
Availability | SPARQL endpoint availability check for CaLiGraph took 4.124641418457031e-05s
Availability | VoID file availability check for CaLiGraph took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.26299142837524414s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 6.580352783203125e-05s
Believability | Calculation of trust value for CaLiGraph took 7.152557373046875e-06s
INFO | --- Analysis for caligraph took 2.798427104949951s
Availability | SPARQL endpoint availability check for can-link took 4.1484832763671875e-05s
Availability | VoID file availability check for can-link took 0.0013935565948486328s
Completeness | Calculation of interlinking completeness for can-link took 0.24275732040405273s
Reputation | Calculation of the PageRank for can-link took 0.020198583602905273s
Interlinking | Calculation of Degree of Connection for can-link took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for can-link took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for can-link took 2.8848648071289062e-05s
Believability | Calculation of trust value for can-link took 6.4373016357421875e-06s
INFO | --- Analysis for can-link took 2.7833001613616943s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 3.910064697265625e-05s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.00031280517578125s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.2660970687866211s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.020539283752441406s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for cap-italy-rdf took 2.8583929538726807s
Availability | SPARQL endpoint availability check for person took 4.00543212890625e-05s
Availability | VoID file availability check for person took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for person took 0.24941110610961914s
Reputation | Calculation of the PageRank for person took 0.021405696868896484s
Interlinking | Calculation of Degree of Connection for person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for person took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for person took 3.790855407714844e-05s
Believability | Calculation of trust value for person took 7.867813110351562e-06s
INFO | --- Analysis for card took 2.860591173171997s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.100799560546875e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.00025343894958496094s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.2471451759338379s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020575523376464844s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.9577484130859375e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 7.62939453125e-06s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 2.865532636642456s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 4.0531158447265625e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.25753235816955566s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 2.7179718017578125e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.1444091796875e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 2.8617029190063477s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 4.744529724121094e-05s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.25524425506591797s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 3.409385681152344e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 7.3909759521484375e-06s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 2.88962459564209s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 4.2438507080078125e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.2544710636138916s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.021147489547729492s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.001056671142578125s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00011777877807617188s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1682510375976562e-05s
INFO | --- Analysis for ce4r took 2.853215217590332s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.44551801681518555s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0003426074981689453s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.0856983661651611s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.9662876129150391s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2588787078857422s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7707762718200684s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.131654024124146s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1593337059020996s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.41428661346435547s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15629816055297852s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1491391658782959s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2914857864379883s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.31591224670410156s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1472148895263672s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.29947781562805176s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.3341639041900635s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15861248970031738s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.28751158714294434s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21892189979553223s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 10.802049398422241s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 7.557868957519531e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2054615020751953s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18979644775390625s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.30437564849853516s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1601111888885498s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15384674072265625s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.42327260971069336s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.34737467765808105s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 1.966468334197998s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 4.0531158447265625e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.15699291229248047s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.17175006866455078s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.1891496181488037s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.562279224395752s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.029381513595581055s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02809762954711914s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.18977570533752441s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.1894402503967285s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.004944324493408s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.3928112983703613s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.603661060333252s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.03312206268310547s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.19513416290283203s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16472649574279785s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 2021.468150138855s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 1.5747225284576416s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02225971221923828s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0007593631744384766s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 0.00017905235290527344s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.6689300537109375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 8.58306884765625e-06s
INFO | --- Analysis for ceo took 2149.908792734146s
Availability | SPARQL endpoint availability check for Charging Stations took 4.3392181396484375e-05s
Availability | VoID file availability check for Charging Stations took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.26038384437561035s
Reputation | Calculation of the PageRank for Charging Stations took 0.019894838333129883s
Interlinking | Calculation of Degree of Connection for Charging Stations took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Charging Stations took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 2.9802322387695312e-05s
Believability | Calculation of trust value for Charging Stations took 6.67572021484375e-06s
INFO | --- Analysis for charging-stations took 3.731022357940674s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.00543212890625e-05s
Availability | VoID file availability check for Chat Game corpus took 0.0002961158752441406s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.2604703903198242s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.020056486129760742s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.218650817871094e-05s
Believability | Calculation of trust value for Chat Game corpus took 7.3909759521484375e-06s
INFO | --- Analysis for chat-game-corpus took 2.892756223678589s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 4.124641418457031e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.24901390075683594s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.020329713821411133s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.123283386230469e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 6.9141387939453125e-06s
INFO | --- Analysis for chebi took 2.7652747631073s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 4.00543212890625e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.2656991481781006s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.078315734863281e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 7.62939453125e-06s
INFO | --- Analysis for chem2bio2rdf took 2.7805604934692383s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 4.029273986816406e-05s
Availability | VoID file availability check for ChEMBL RDF took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.25451231002807617s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020206451416015625s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.839897155761719e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.239776611328125e-05s
INFO | --- Analysis for chembl-rdf took 2.819838523864746s
Availability | SPARQL endpoint availability check for chemdb  dataset took 4.172325134277344e-05s
Availability | VoID file availability check for chemdb  dataset took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.2722816467285156s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.020443439483642578s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0009984970092773438s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 0.00015544891357421875s
Believability | Calculation of trust value for chemdb  dataset took 1.2636184692382812e-05s
INFO | --- Analysis for chemdb-basicInfo took 3.034013509750366s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 4.029273986816406e-05s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.2673916816711426s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020432233810424805s
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.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 4.267692565917969e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 7.867813110351562e-06s
INFO | --- Analysis for chemdb-estimatedProperties took 2.8396692276000977s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 3.9577484130859375e-05s
Availability | VoID file availability check for chemdb phase transition dataset took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.2622807025909424s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.020004749298095703s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.601478576660156e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 7.62939453125e-06s
INFO | --- Analysis for chemdb-phaseTransition took 2.868652820587158s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 4.100799560546875e-05s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.2671699523925781s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.020237445831298828s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.888938903808594e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 8.106231689453125e-06s
INFO | --- Analysis for chemdb-thermochemistry took 2.8724522590637207s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 6.0558319091796875e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.265211820602417s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 2.86102294921875e-05s
Believability | Calculation of trust value for ChemPedia RDF took 7.152557373046875e-06s
INFO | --- Analysis for chempedia-rdf took 2.810994863510132s
Availability | SPARQL endpoint availability check for Chiman Maru took 4.076957702636719e-05s
Availability | VoID file availability check for Chiman Maru took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.25249505043029785s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020626544952392578s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.0040740966796875e-05s
Believability | Calculation of trust value for Chiman Maru took 7.62939453125e-06s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 2.8884806632995605s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.5586552619934s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0006248950958251953s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.2766869068145752s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 3.647804260253906e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 7.152557373046875e-06s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 666.5170471668243s
Availability | SPARQL endpoint availability check for Chronicling America took 5.698204040527344e-05s
Availability | VoID file availability check for Chronicling America took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.6955366134643555s
Reputation | Calculation of the PageRank for Chronicling America took 0.02161407470703125s
Interlinking | Calculation of Degree of Connection for Chronicling America took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Chronicling America took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 0.00012135505676269531s
Believability | Calculation of trust value for Chronicling America took 6.9141387939453125e-06s
INFO | --- Analysis for chronicling-america took 4.160495042800903s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.5648910999298096s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0002551078796386719s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 77.62221693992615s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.7222809791564941s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6244370937347412s
Interoperability | New terms check for Cultural Heritage Thesaurus took 1.9262840747833252s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.549098253250122s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5608468055725098s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.3000349998474121s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.30214357376098633s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.701488494873047s
License | MR license check for Cultural Heritage Thesaurus took 0.28412914276123047s
License | HR license check for Cultural Heritage Thesaurus took 0.32851314544677734s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.3100590705871582s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.35239267349243164s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.580742359161377s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.29830360412597656s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2936675548553467s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.30541539192199707s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.670955419540405s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 7.390975952148438e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.2840454578399658s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.3169589042663574s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.33107757568359375s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.29293322563171387s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.2924380302429199s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.6005871295928955s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5536208152770996s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 31.059605360031128s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 2.6316370964050293s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2863318920135498s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.3051013946533203s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.2887916564941406s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 6.0418267250061035s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.22087883949279785s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.27083635330200195s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 1.0061140060424805s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.3077991008758545s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.92340874671936s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.2116312980651855s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.00014519691467285156s
Security | Sign check for Cultural Heritage Thesaurus took 0.28928041458129883s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 272.6821801662445s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.7353708744049072s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 9.918212890625e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.008296489715576s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for cht took 463.37649869918823s
Availability | SPARQL endpoint availability check for ciard-ring took 4.124641418457031e-05s
Availability | VoID file availability check for ciard-ring took 0.0005540847778320312s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.26363563537597656s
Reputation | Calculation of the PageRank for ciard-ring took 0.020337820053100586s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 5.030632019042969e-05s
Believability | Calculation of trust value for ciard-ring took 7.867813110351562e-06s
INFO | --- Analysis for ciard-ring took 3.2527406215667725s
Availability | SPARQL endpoint availability check for Cine Figure took 0.00011110305786132812s
Availability | VoID file availability check for Cine Figure took 0.0003135204315185547s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.2563815116882324s
Reputation | Calculation of the PageRank for Cine Figure took 0.02049112319946289s
Interlinking | Calculation of Degree of Connection for Cine Figure took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Cine Figure took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.315376281738281e-05s
Believability | Calculation of trust value for Cine Figure took 7.62939453125e-06s
INFO | --- Analysis for Cine_Figure took 2.883232355117798s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 1.36210036277771s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.26014137268066406s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.02100825309753418s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.00543212890625e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 4.5343756675720215s
Availability | SPARQL endpoint availability check for CIPFA took 4.1961669921875e-05s
Availability | VoID file availability check for CIPFA took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for CIPFA took 0.25022077560424805s
Reputation | Calculation of the PageRank for CIPFA took 0.020113468170166016s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0006744861602783203s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.2901763916015625e-05s
Believability | Calculation of trust value for CIPFA took 1.0728836059570312e-05s
INFO | --- Analysis for cipfa took 2.7715344429016113s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 4.982948303222656e-05s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.26132631301879883s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020180225372314453s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00038695335388183594s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 6.9141387939453125e-06s
INFO | --- Analysis for ckan took 2.901716470718384s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.9577484130859375e-05s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.00032782554626464844s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.26872730255126953s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.239776611328125e-05s
INFO | --- Analysis for CLaSSES took 2.768601417541504s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 4.2438507080078125e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.2498772144317627s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 2.9325485229492188e-05s
Believability | Calculation of trust value for Temples of the Classical World took 7.152557373046875e-06s
INFO | --- Analysis for classical_temples took 2.867403268814087s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.27424073219299316s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0008883476257324219s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 9.250640869140625e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 7.3909759521484375e-06s
INFO | --- Analysis for clean-energy-data-reegle took 2.813584566116333s
Availability | SPARQL endpoint availability check for CLLD-afbo took 4.076957702636719e-05s
Availability | VoID file availability check for CLLD-afbo took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.27091431617736816s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02019190788269043s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 7.43865966796875e-05s
Believability | Calculation of trust value for CLLD-afbo took 7.3909759521484375e-06s
INFO | --- Analysis for clld-afbo took 2.8054025173187256s
Availability | SPARQL endpoint availability check for CLLD-APICS took 4.076957702636719e-05s
Availability | VoID file availability check for CLLD-APICS took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.2718808650970459s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.367134094238281e-05s
Believability | Calculation of trust value for CLLD-APICS took 7.3909759521484375e-06s
INFO | --- Analysis for clld-apics took 2.8386454582214355s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 3.886222839355469e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.26564931869506836s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.719329833984375e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.2159347534179688e-05s
INFO | --- Analysis for clld-ewave took 2.931976318359375s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 3.910064697265625e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.25735974311828613s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0008590221405029297s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 0.00011134147644042969s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 7.62939453125e-06s
INFO | --- Analysis for clld-glottolog took 2.8362233638763428s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 3.838539123535156e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.0003368854522705078s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.23738622665405273s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.724761962890625e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 6.9141387939453125e-06s
INFO | --- Analysis for clld-phoible took 2.7836451530456543s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 3.910064697265625e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.2657949924468994s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.02203845977783203s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0012028217315673828s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 9.822845458984375e-05s
Believability | Calculation of trust value for CLLD-SAILS took 8.106231689453125e-06s
INFO | --- Analysis for clld-sails took 2.8786370754241943s
Availability | SPARQL endpoint availability check for CLLD-WALS took 4.0531158447265625e-05s
Availability | VoID file availability check for CLLD-WALS took 0.00030875205993652344s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.2660670280456543s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.273124694824219e-05s
Believability | Calculation of trust value for CLLD-WALS took 1.2159347534179688e-05s
INFO | --- Analysis for clld-wals took 2.783850908279419s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 3.9577484130859375e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.27435302734375s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.653236389160156e-05s
Believability | Calculation of trust value for CLLD-WOLD took 7.867813110351562e-06s
INFO | --- Analysis for clld-wold took 2.8406734466552734s
Availability | SPARQL endpoint availability check for COD inventory took 4.458427429199219e-05s
Availability | VoID file availability check for COD inventory took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for COD inventory took 0.24115419387817383s
Reputation | Calculation of the PageRank for COD inventory took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for COD inventory took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for COD inventory took 2.86102294921875e-05s
Believability | Calculation of trust value for COD inventory took 7.152557373046875e-06s
INFO | --- Analysis for cod-inventory took 2.776327610015869s
Availability | SPARQL endpoint availability check for Cooperation Databank took 5.125999450683594e-05s
Availability | VoID file availability check for Cooperation Databank took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.2636277675628662s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020116329193115234s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.24249267578125e-05s
Believability | Calculation of trust value for Cooperation Databank took 6.9141387939453125e-06s
INFO | --- Analysis for CoDa took 2.7855334281921387s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.029273986816406e-05s
Availability | VoID file availability check for CODE Endpoint took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.24474287033081055s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.019974708557128906s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 2.7894973754882812e-05s
Believability | Calculation of trust value for CODE Endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for code-endpoint took 2.8131892681121826s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 3.9577484130859375e-05s
Availability | VoID file availability check for OpenUpLabs COINS took 0.000244140625s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.259350061416626s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020165443420410156s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 2.6941299438476562e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 7.62939453125e-06s
INFO | --- Analysis for coins-openuplabs took 2.8064684867858887s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 4.029273986816406e-05s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.24645686149597168s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.02017045021057129s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 7.62939453125e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 6.198883056640625e-06s
INFO | --- Analysis for CoLChina_sp2000 took 2.8088717460632324s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 8.106231689453125e-05s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.26307249069213867s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020247220993041992s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.4332275390625e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for colinda took 2.8061041831970215s
Availability | SPARQL endpoint availability check for CN  2012 took 4.100799560546875e-05s
Availability | VoID file availability check for CN  2012 took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.25087809562683105s
Reputation | Calculation of the PageRank for CN  2012 took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0008027553558349609s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.981590270996094e-05s
Believability | Calculation of trust value for CN  2012 took 8.344650268554688e-06s
INFO | --- Analysis for combined-nomenclature-2012 took 2.8828248977661133s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 4.00543212890625e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.26436591148376465s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.02040863037109375s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 7.152557373046875e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 2.7951598167419434s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 4.5299530029296875e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.28981900215148926s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 3.0517578125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 7.152557373046875e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 2.8693201541900635s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.076957702636719e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.2518165111541748s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 2.9802322387695312e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.239776611328125e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 2.8304977416992188s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 4.0531158447265625e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0003864765167236328s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.2329394817352295s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020542383193969727s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 2.765655517578125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 7.62939453125e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 2.7878570556640625s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 4.1961669921875e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.2639443874359131s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 2.956390380859375e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 6.9141387939453125e-06s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.7918479442596436s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 4.076957702636719e-05s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.24680137634277344s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.02065730094909668s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 7.62939453125e-06s
INFO | --- Analysis for CompHistSem took 2.8696372509002686s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 4.0531158447265625e-05s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.2744557857513428s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.020879745483398438s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 4.57763671875e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 7.3909759521484375e-06s
INFO | --- Analysis for comsode-d3-2 took 2.8685076236724854s
Availability | SPARQL endpoint availability check for ConceptNet took 4.076957702636719e-05s
Availability | VoID file availability check for ConceptNet took 0.0003249645233154297s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.2840139865875244s
Reputation | Calculation of the PageRank for ConceptNet took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for ConceptNet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ConceptNet took 0.0007536411285400391s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.1948089599609375e-05s
Believability | Calculation of trust value for ConceptNet took 7.152557373046875e-06s
INFO | --- Analysis for conceptnet took 2.820516586303711s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 4.124641418457031e-05s
Availability | VoID file availability check for 2011 US Congress People took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.2651364803314209s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020528554916381836s
Interlinking | Calculation of Degree of Connection for 2011 US Congress People took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for 2011 US Congress People took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.273124694824219e-05s
Believability | Calculation of trust value for 2011 US Congress People took 8.106231689453125e-06s
INFO | --- Analysis for congresspeople took 2.8751938343048096s
Availability | SPARQL endpoint availability check for MIMO took 4.172325134277344e-05s
Availability | VoID file availability check for MIMO took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for MIMO took 0.274888277053833s
Reputation | Calculation of the PageRank for MIMO took 0.020517349243164062s
Interlinking | Calculation of Degree of Connection for MIMO took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.239776611328125e-05s
Believability | Calculation of trust value for MIMO took 7.3909759521484375e-06s
INFO | --- Analysis for CONNECTED took 2.8891568183898926s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 4.172325134277344e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.24561023712158203s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0006732940673828125s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.8162596225738525s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 4.0531158447265625e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.24785590171813965s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.02085709571838379s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.0040740966796875e-05s
Believability | Calculation of trust value for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 7.3909759521484375e-06s
INFO | --- Analysis for copac-library-catalogue took 2.8591368198394775s
Availability | SPARQL endpoint availability check for Copyright Free Music took 4.1961669921875e-05s
Availability | VoID file availability check for Copyright Free Music took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.28842592239379883s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 2.956390380859375e-05s
Believability | Calculation of trust value for Copyright Free Music took 7.152557373046875e-06s
INFO | --- Analysis for Copyright_Free_Music took 2.929633378982544s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 6.437301635742188e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.27738308906555176s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 7.081031799316406e-05s
Believability | Calculation of trust value for CopyrightTermBank took 8.106231689453125e-06s
INFO | --- Analysis for copyrighttermbank took 2.8442044258117676s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 4.291534423828125e-05s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.2655477523803711s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007793903350830078s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.981590270996094e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 7.152557373046875e-06s
INFO | --- Analysis for core took 2.869852066040039s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 5.2928924560546875e-05s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.26270580291748047s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02087569236755371s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Corine linked dataset @PSNC took 2.9325485229492188e-05s
Believability | Calculation of trust value for Corine linked dataset @PSNC took 7.152557373046875e-06s
INFO | --- Analysis for Corine_linked_dataset took 2.836254358291626s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 4.029273986816406e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.2596714496612549s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 3.0517578125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.106231689453125e-06s
INFO | --- Analysis for corn took 2.897181749343872s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.100799560546875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.2438220977783203s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007600784301757812s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.147125244140625e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 8.821487426757812e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 2.8072869777679443s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 4.1961669921875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.25115251541137695s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020123958587646484s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 2.6464462280273438e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 7.867813110351562e-06s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 2.7611289024353027s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 4.029273986816406e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.26555395126342773s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020917415618896484s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.793571472167969e-05s
Believability | Calculation of trust value for Cornetto1.2 took 8.344650268554688e-06s
INFO | --- Analysis for cornetto took 2.874423027038574s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 4.00543212890625e-05s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.2582709789276123s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.696846008300781e-05s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 6.198883056640625e-06s
INFO | --- Analysis for corporate-body took 2.925844430923462s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 4.2438507080078125e-05s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.2614407539367676s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020538806915283203s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0008039474487304688s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.790855407714844e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 7.62939453125e-06s
INFO | --- Analysis for CorpusFibonacci took 2.8272366523742676s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.2645747661590576s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 6.9141387939453125e-06s
INFO | --- Analysis for corscheck took 2.9137988090515137s
Availability | SPARQL endpoint availability check for Country Name Authority List took 4.00543212890625e-05s
Availability | VoID file availability check for Country Name Authority List took 0.0002903938293457031s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.26497459411621094s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.020958900451660156s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Country Name Authority List took 4.7206878662109375e-05s
Believability | Calculation of trust value for Country Name Authority List took 7.62939453125e-06s
INFO | --- Analysis for country-authority-list took 2.8580939769744873s
Availability | SPARQL endpoint availability check for Courts thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for Courts thesaurus took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.2753453254699707s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.532669067382812e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.5974044799804688e-05s
INFO | --- Analysis for courts-thesaurus took 2.885533571243286s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.2383897304534912s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.020377159118652344s
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.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.677078247070312e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for Covid-on-the-Web took 2.82741117477417s
Availability | SPARQL endpoint availability check for CPA 2008 took 7.176399230957031e-05s
Availability | VoID file availability check for CPA 2008 took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.2622358798980713s
Reputation | Calculation of the PageRank for CPA 2008 took 0.020927906036376953s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 4.00543212890625e-05s
Believability | Calculation of trust value for CPA 2008 took 7.62939453125e-06s
INFO | --- Analysis for cpa-2008 took 2.873800754547119s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 4.315376281738281e-05s
Availability | VoID file availability check for Cooperative Patent Classification took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.2819662094116211s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020664453506469727s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.528594970703125e-05s
Believability | Calculation of trust value for Cooperative Patent Classification took 7.867813110351562e-06s
INFO | --- Analysis for CPC took 2.9492383003234863s
Availability | SPARQL endpoint availability check for CPC 2008 took 4.076957702636719e-05s
Availability | VoID file availability check for CPC 2008 took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.2858142852783203s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020752668380737305s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.4332275390625e-05s
Believability | Calculation of trust value for CPC 2008 took 1.239776611328125e-05s
INFO | --- Analysis for cpc-2008 took 2.8148670196533203s
Availability | SPARQL endpoint availability check for CPV  2003 took 4.00543212890625e-05s
Availability | VoID file availability check for CPV  2003 took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.26047277450561523s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.123283386230469e-05s
Believability | Calculation of trust value for CPV  2003 took 1.1205673217773438e-05s
INFO | --- Analysis for cpv-2003 took 2.855247735977173s
Availability | SPARQL endpoint availability check for CPV 2008 took 3.981590270996094e-05s
Availability | VoID file availability check for CPV 2008 took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.26433300971984863s
Reputation | Calculation of the PageRank for CPV 2008 took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.38690185546875e-05s
Believability | Calculation of trust value for CPV 2008 took 8.106231689453125e-06s
INFO | --- Analysis for cpv-2008 took 2.868849277496338s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 4.124641418457031e-05s
Availability | VoID file availability check for crowdsourcing-fb took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.27454662322998047s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02064204216003418s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.7670135498046875e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 6.9141387939453125e-06s
INFO | --- Analysis for crowdsourcing-fb took 2.8066766262054443s
Availability | SPARQL endpoint availability check for CRTM took 4.00543212890625e-05s
Availability | VoID file availability check for CRTM took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for CRTM took 0.24804997444152832s
Reputation | Calculation of the PageRank for CRTM took 0.020130157470703125s
Interlinking | Calculation of Degree of Connection for CRTM took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for CRTM took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9087066650390625e-05s
Believability | Calculation of trust value for CRTM took 6.4373016357421875e-06s
INFO | --- Analysis for crtm took 2.7867705821990967s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 4.291534423828125e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.2623915672302246s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Crystal Eye: Aggregated Crystallographic Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for Crystal Eye: Aggregated Crystallographic Data took 6.9141387939453125e-06s
INFO | --- Analysis for crystal-eye took 3.189649820327759s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 3.9577484130859375e-05s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.00039696693420410156s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.2705566883087158s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.9114227294921875e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 6.4373016357421875e-06s
INFO | --- Analysis for ctic-public-dataset took 2.7999422550201416s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 3.981590270996094e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.26920127868652344s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.021241426467895508s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0008759498596191406s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.314018249511719e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 7.62939453125e-06s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 2.8572275638580322s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 0.7377471923828125s
Availability | VoID file availability check for CulturaLinkedData took 0.00028705596923828125s
Extra | Recovery of all triples for CulturaLinkedData took 126.97390460968018s
Performance | Total latancy measurement for CulturaLinkedData took 6.150422096252441s
Amount of data | Number of triples check for CulturaLinkedData took 3.1101346015930176s
Interoperability | New terms check for CulturaLinkedData took 2.244453191757202s
Versatility | Languages check for CulturaLinkedData took 63.81132650375366s
Interpretability | Number of blank nodes check for CulturaLinkedData took 0.19681692123413086s
Interpretability | RDF structures check for CulturaLinkedData took 2.148360013961792s
Versatility | Serialization formats check for CulturaLinkedData took 2.1814279556274414s
Availability | RDF dump link check for CulturaLinkedData took 2.007988214492798s
License | MR license check for CulturaLinkedData took 0.5140209197998047s
License | HR license check for CulturaLinkedData took 63.03578209877014s
Amount of data | Number of property check for CulturaLinkedData took 1.9276783466339111s
Understandability | Number of label check for CulturaLinkedData took 0.8205783367156982s
Understandability | URI regex check for CulturaLinkedData took 0.5097005367279053s
Understandability | Vocabs check for CulturaLinkedData took 0.22759413719177246s
Verifiability | Authors check for CulturaLinkedData took 0.2627992630004883s
Verifiability | Publishers check for CulturaLinkedData took 0.23592638969421387s
Performance | Throughput check for CulturaLinkedData took 20.823171615600586s
Amount of data | Check the number of entities for CulturaLinkedData took 6.866455078125e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.0243451595306396s
Interlinking | sameAs chians check for CulturaLinkedData took 2.1690118312835693s
Interlinking | skos check for CulturaLinkedData took 0.38536858558654785s
Interlinking | skos check for CulturaLinkedData took 0.19732165336608887s
Timeliness | dataset update frequency check for CulturaLinkedData took 0.2599608898162842s
Currency | Creation date check for CulturaLinkedData took 4.033052206039429s
Currency | Modification date check for CulturaLinkedData took 0.3813896179199219s
Rep.Conc. | URIs length for CulturaLinkedData took 65.16426014900208s
Interoperability | New vocabularies check for CulturaLinkedData took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 1.9907569885253906s
Accuracy | Check Functional Property for CulturaLinkedData took 2.001502513885498s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 0.16994023323059082s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 43.416104316711426s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.604557991027832s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.2874019145965576s
Consistency | Disjoint class check for CulturaLinkedData took 0.22403740882873535s
Consistency | Check Misplaced properties for CulturaLinkedData took 9.942927598953247s
Consistency | Misplaced classes for CulturaLinkedData took 4.24667501449585s
Consistency | Check Ontology hijacking for CulturaLinkedData took 47.193273305892944s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.4161584377288818s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.334023475646973s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.3516592979431152s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 2.0237643718719482s
Security | Sign check for CulturaLinkedData took 2.8194286823272705s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 15.95330023765564s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 1.3926622867584229s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021027803421020508s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 3.6716461181640625e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 1.6689300537109375e-06s
Believability | Calculation of trust value for CulturaLinkedData took 6.9141387939453125e-06s
INFO | --- Analysis for culturalinkeddata took 659.8730306625366s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 4.792213439941406e-05s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0003070831298828125s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.7130951881408691s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.02054309844970703s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 3.8623809814453125e-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 3.7081477642059326s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 4.00543212890625e-05s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.2611534595489502s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.457069396972656e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 5.7220458984375e-06s
INFO | --- Analysis for cz-ares-rzp took 2.8334720134735107s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 4.291534423828125e-05s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.25274038314819336s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.361701965332031e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 7.867813110351562e-06s
INFO | --- Analysis for cz-cenia-irz-chemicals took 2.7929370403289795s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 4.1484832763671875e-05s
Availability | VoID file availability check for Integrated pollution registry took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.25018811225891113s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020444631576538086s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 3.814697265625e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.2636184692382812e-05s
INFO | --- Analysis for cz-cenia-pollution took 2.8557770252227783s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 4.172325134277344e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.00033974647521972656s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.23819589614868164s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.0007200241088867188s
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 7.62939453125e-06s
INFO | --- Analysis for cz-contracts took 2.7830898761749268s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 4.172325134277344e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.23671603202819824s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.02065253257751465s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 3.0517578125e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-courts took 2.85613751411438s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 4.100799560546875e-05s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.28341054916381836s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.2901763916015625e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 7.62939453125e-06s
INFO | --- Analysis for cz-ctia-bans took 2.861262798309326s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 4.029273986816406e-05s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.26158833503723145s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020979881286621094s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0008480548858642578s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.814697265625e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-confiscations took 2.8518614768981934s
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.00026726722717285156s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.27343130111694336s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020293712615966797s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.409385681152344e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 8.344650268554688e-06s
INFO | --- Analysis for cz-ctia-focus took 2.8251824378967285s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 4.076957702636719e-05s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.2618827819824219s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020209550857543945s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 4.601478576660156e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 7.62939453125e-06s
INFO | --- Analysis for cz-ctia-inspections took 2.8370511531829834s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 4.124641418457031e-05s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.2672536373138428s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.457069396972656e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 7.3909759521484375e-06s
INFO | --- Analysis for cz-ctia-sanctions took 2.884291410446167s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 4.076957702636719e-05s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.28904056549072266s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.020751476287841797s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 3.600120544433594e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 6.9141387939453125e-06s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.8908088207244873s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 5.054473876953125e-05s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.24364948272705078s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.020180702209472656s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0006821155548095703s
Interlinking | Calculation of Clustering coefficient for Code lists of the legal relationships and documents took 3.62396240234375e-05s
Believability | Calculation of trust value for Code lists of the legal relationships and documents took 6.67572021484375e-06s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 2.91787052154541s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 4.792213439941406e-05s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.25954651832580566s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0007107257843017578s
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 7.62939453125e-06s
INFO | --- Analysis for cz-czso-average-salaries took 2.851295232772827s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 4.100799560546875e-05s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.26886916160583496s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0007424354553222656s
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 8.106231689453125e-06s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 2.8229148387908936s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 7.033348083496094e-05s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.2506275177001953s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.020859479904174805s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 3.62396240234375e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 7.3909759521484375e-06s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 2.8449015617370605s
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.0002644062042236328s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.2665531635284424s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 4.029273986816406e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-czso-job-applicants took 2.9068288803100586s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 4.029273986816406e-05s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.2551391124725342s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.02033519744873047s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 2.861233711242676s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 4.00543212890625e-05s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.2545149326324463s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0007491111755371094s
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.1444091796875e-05s
INFO | --- Analysis for cz-czso-regions took 2.8250255584716797s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 7.82012939453125e-05s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.25920987129211426s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.020361900329589844s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.719329833984375e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 2.8454737663269043s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 4.7206878662109375e-05s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.26553869247436523s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020529508590698242s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.695487976074219e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 8.344650268554688e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 2.800368070602417s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 4.673004150390625e-05s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.2730135917663574s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020699262619018555s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 2.8456833362579346s
Availability | SPARQL endpoint availability check for ATC groups took 4.7206878662109375e-05s
Availability | VoID file availability check for ATC groups took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for ATC groups took 0.2770507335662842s
Reputation | Calculation of the PageRank for ATC groups took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.985664367675781e-05s
Believability | Calculation of trust value for ATC groups took 7.3909759521484375e-06s
INFO | --- Analysis for cz-eh-1-atc took 2.812352180480957s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 4.124641418457031e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.2638840675354004s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020212650299072266s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Financial fulfillments took 3.62396240234375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Financial fulfillments took 1.0728836059570312e-05s
INFO | --- Analysis for cz-fulfillments took 2.7803409099578857s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 4.2438507080078125e-05s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.24913406372070312s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.458427429199219e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 6.67572021484375e-06s
INFO | --- Analysis for cz-ic took 2.849156618118286s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 3.981590270996094e-05s
Availability | VoID file availability check for List of Czech data boxes took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.26090574264526367s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020404338836669922s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 2.9325485229492188e-05s
Believability | Calculation of trust value for List of Czech data boxes took 6.9141387939453125e-06s
INFO | --- Analysis for cz-list-of-databoxes took 2.831587791442871s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 5.221366882324219e-05s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.23871850967407227s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.020688295364379883s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 7.867813110351562e-06s
INFO | --- Analysis for cz-nace took 2.877495765686035s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.100799560546875e-05s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.26701855659484863s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 2.8848648071289062e-05s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 6.67572021484375e-06s
INFO | --- Analysis for cz-nkod took 2.9071037769317627s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 5.1975250244140625e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.278933048248291s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020117998123168945s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0006787776947021484s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.1948089599609375e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.0967254638671875e-05s
INFO | --- Analysis for cz-orders took 2.7746477127075195s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 3.981590270996094e-05s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.24538660049438477s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.021011829376220703s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-ovm took 2.862448215484619s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 4.124641418457031e-05s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.26409220695495605s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.0207364559173584s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 6.67572021484375e-06s
INFO | --- Analysis for cz-ovm-agendas took 2.834794282913208s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 4.100799560546875e-05s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.2602543830871582s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.02012467384338379s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0006744861602783203s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.318092346191406e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-ruian took 2.8037314414978027s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 5.1021575927734375e-05s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.29170966148376465s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.020751237869262695s
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.0006809234619140625s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.581710815429688e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 7.867813110351562e-06s
INFO | --- Analysis for cz-sao-audited-subjects took 2.813664197921753s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 4.0531158447265625e-05s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.26389336585998535s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 3.6716461181640625e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 2.09808349609375e-05s
INFO | --- Analysis for cz-sao-check-actions took 2.8060944080352783s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 4.0531158447265625e-05s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.23959779739379883s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0007886886596679688s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 3.218650817871094e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 7.152557373046875e-06s
INFO | --- Analysis for cz-sao-check-actions-law took 2.8180809020996094s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 5.173683166503906e-05s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.2545914649963379s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.02044224739074707s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.3855438232421875e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 2.8554165363311768s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 5.030632019042969e-05s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.26660752296447754s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020620107650756836s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.170967102050781e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 7.152557373046875e-06s
INFO | --- Analysis for cz-sidc-drug-prices took 2.8138303756713867s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 3.9577484130859375e-05s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.28976941108703613s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0006754398345947266s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.600120544433594e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-sidc-drugs took 2.831578493118286s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 4.1961669921875e-05s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.2626838684082031s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.02042365074157715s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.218650817871094e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 7.62939453125e-06s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2.898587703704834s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 4.458427429199219e-05s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.26216697692871094s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.695487976074219e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 7.152557373046875e-06s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.81630277633667s
Availability | SPARQL endpoint availability check for State funding providers took 3.981590270996094e-05s
Availability | VoID file availability check for State funding providers took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for State funding providers took 0.26376771926879883s
Reputation | Calculation of the PageRank for State funding providers took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for State funding providers took 3.600120544433594e-05s
Believability | Calculation of trust value for State funding providers took 7.3909759521484375e-06s
INFO | --- Analysis for cz-vavai-funding-providers took 2.8611583709716797s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 4.029273986816406e-05s
Availability | VoID file availability check for Organizations active in R&D took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.23083734512329102s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.021259307861328125s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 3.790855407714844e-05s
Believability | Calculation of trust value for Organizations active in R&D took 7.867813110351562e-06s
INFO | --- Analysis for cz-vavai-organizations took 2.83145809173584s
Availability | SPARQL endpoint availability check for R&D Programmes took 4.1484832763671875e-05s
Availability | VoID file availability check for R&D Programmes took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.25551271438598633s
Reputation | Calculation of the PageRank for R&D Programmes took 0.02032303810119629s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0006783008575439453s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 3.8623809814453125e-05s
Believability | Calculation of trust value for R&D Programmes took 6.4373016357421875e-06s
INFO | --- Analysis for cz-vavai-programmes took 2.7958664894104004s
Availability | SPARQL endpoint availability check for R&D Projects took 3.9577484130859375e-05s
Availability | VoID file availability check for R&D Projects took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.2796916961669922s
Reputation | Calculation of the PageRank for R&D Projects took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 3.814697265625e-05s
Believability | Calculation of trust value for R&D Projects took 6.4373016357421875e-06s
INFO | --- Analysis for cz-vavai-projects took 2.898540496826172s
Availability | SPARQL endpoint availability check for Institutional research plans took 4.0531158447265625e-05s
Availability | VoID file availability check for Institutional research plans took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.2655825614929199s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 3.9577484130859375e-05s
Believability | Calculation of trust value for Institutional research plans took 7.152557373046875e-06s
INFO | --- Analysis for cz-vavai-research-plans took 2.8362948894500732s
Availability | SPARQL endpoint availability check for Results of R&D took 4.029273986816406e-05s
Availability | VoID file availability check for Results of R&D took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.25310444831848145s
Reputation | Calculation of the PageRank for Results of R&D took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for Results of R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Results of R&D took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 3.981590270996094e-05s
Believability | Calculation of trust value for Results of R&D took 7.3909759521484375e-06s
INFO | --- Analysis for cz-vavai-results took 2.8714356422424316s
Availability | SPARQL endpoint availability check for Tenders in R&D took 3.9577484130859375e-05s
Availability | VoID file availability check for Tenders in R&D took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.2580299377441406s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02032780647277832s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0006892681121826172s
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 6.9141387939453125e-06s
INFO | --- Analysis for cz-vavai-tenders took 2.78611421585083s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.267692565917969e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.26563596725463867s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020061254501342773s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.123283386230469e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 7.152557373046875e-06s
INFO | --- Analysis for czech_addresses took 2.7861852645874023s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 4.029273986816406e-05s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.2753942012786865s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020656108856201172s
Interlinking | Calculation of Degree of Connection for Dante Latin Loanwords in LiLa took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Dante Latin Loanwords in LiLa took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 3.9577484130859375e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.1682510375976562e-05s
INFO | --- Analysis for DanteLatinLoanwords took 2.9033305644989014s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 1.1137988567352295s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.00026702880859375s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 155.54438042640686s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.1057307720184326s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 14.084012269973755s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.397182464599609s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.27148199081421s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.18661284446716309s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.1097261905670166s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.9115169048309326s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.22179961204528809s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.1937558650970459s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.21364903450012207s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 74.43104958534241s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.20218300819396973s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 0.49395179748535156s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.3681907653808594s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.20225858688354492s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.20802855491638184s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.20730233192443848s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 11.537003755569458s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 8.559226989746094e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.18909692764282227s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.5040838718414307s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.6835927963256836s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.23994755744934082s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.18407559394836426s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 4.097011566162109s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 3.8647713661193848s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 85.69733047485352s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.2014617919921875s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.27542829513549805s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.8161094188690186s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 44.57959747314453s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.199350595474243s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.661517858505249s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.44925546646118164s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 21.936854362487793s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.738729000091553s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 47.31597852706909s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.6606132984161377s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 23.10915231704712s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.805246353149414s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2036266326904297s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.19713544845581055s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 13.100201845169067s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.8117828369140625s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.021105289459228516s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.0001418590545654297s
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 7.62939453125e-06s
INFO | --- Analysis for data-bnf-fr took 830.6986093521118s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 5.817413330078125e-05s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.26366281509399414s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.020709753036499023s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.67572021484375e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.1682510375976562e-05s
INFO | --- Analysis for data-cnr-it took 4.606196403503418s
Availability | SPARQL endpoint availability check for Data.gov took 4.172325134277344e-05s
Availability | VoID file availability check for Data.gov took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Data.gov took 0.2692537307739258s
Reputation | Calculation of the PageRank for Data.gov took 0.020505189895629883s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.170967102050781e-05s
Believability | Calculation of trust value for Data.gov took 7.3909759521484375e-06s
INFO | --- Analysis for data-gov took 2.837524890899658s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 4.601478576660156e-05s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.2720346450805664s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for DataGovIE - Irish Government Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DataGovIE - Irish Government Data took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.651878356933594e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 8.106231689453125e-06s
INFO | --- Analysis for data-gov-ie took 2.808422327041626s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 4.172325134277344e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.2630796432495117s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.020302772521972656s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 6.771087646484375e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 1.3589859008789062e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.8620691299438477s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 21.493520498275757s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.2750518321990967s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020348787307739258s
Interlinking | Calculation of Degree of Connection for data-hnm-hu - Hungarian National Museum Datasets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data-hnm-hu - Hungarian National Museum Datasets took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 5.7697296142578125e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 6.67572021484375e-06s
INFO | --- Analysis for data-hnm-hu took 54.526134729385376s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.13104748725891113s
Availability | VoID file availability check for Climb Dataincubator took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.23485565185546875s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.020893573760986328s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 7.367134094238281e-05s
Believability | Calculation of trust value for Climb Dataincubator took 9.775161743164062e-06s
INFO | --- Analysis for data-incubator-climb took 3.4528074264526367s
Availability | SPARQL endpoint availability check for Discogs in RDF took 8.463859558105469e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0006508827209472656s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.25765085220336914s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.020198822021484375s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 9.059906005859375e-05s
Believability | Calculation of trust value for Discogs in RDF took 1.0251998901367188e-05s
INFO | --- Analysis for data-incubator-discogs took 5.49720025062561s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 4.1961669921875e-05s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.26827001571655273s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.7220458984375e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-metoffice took 2.7577691078186035s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.052171945571899414s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0015368461608886719s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.25029897689819336s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.726119995117188e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 3.4809112548828125e-05s
INFO | --- Analysis for data-incubator-moseley took 4.979201555252075s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.04834580421447754s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.2633991241455078s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020542144775390625s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.012222290039062e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-musicbrainz took 3.039346218109131s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 4.076957702636719e-05s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.27788567543029785s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.020281314849853516s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 8.416175842285156e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 8.106231689453125e-06s
INFO | --- Analysis for data-incubator-nasa took 2.8941736221313477s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 4.220008850097656e-05s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.2562994956970215s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.02032756805419922s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 7.2479248046875e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 7.152557373046875e-06s
INFO | --- Analysis for data-incubator-our-airports took 2.87418532371521s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 4.5299530029296875e-05s
Availability | VoID file availability check for Pokedex data in RDF took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.2693495750427246s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.02044367790222168s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 9.083747863769531e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 6.67572021484375e-06s
INFO | --- Analysis for data-incubator-pokedex took 2.880949020385742s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 4.0531158447265625e-05s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00060272216796875s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.2748692035675049s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020499229431152344s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 8.916854858398438e-05s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 6.4373016357421875e-06s
INFO | --- Analysis for data-incubator-smcjournals took 2.8211915493011475s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 3.9577484130859375e-05s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.2757296562194824s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.02029895782470703s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.532669067382812e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 7.62939453125e-06s
INFO | --- Analysis for data-open-ac-uk took 2.829164505004883s
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.0002319812774658203s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.24035406112670898s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for Persée in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Persée in RDF took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00010395050048828125s
Believability | Calculation of trust value for Persée in RDF took 6.198883056640625e-06s
INFO | --- Analysis for data-persee-fr took 2.808924913406372s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 4.076957702636719e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.2523462772369385s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.02012777328491211s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 2.7418136596679688e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 6.9141387939453125e-06s
INFO | --- Analysis for data-southampton-ac-uk took 2.866617441177368s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 5.248675584793091s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.25431227684020996s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00010704994201660156s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 6.67572021484375e-06s
INFO | --- Analysis for data-szepmuveszeti-hu took 8.665102481842041s
Availability | SPARQL endpoint availability check for Open Data Web took 6.0558319091796875e-05s
Availability | VoID file availability check for Open Data Web took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.24924421310424805s
Reputation | Calculation of the PageRank for Open Data Web took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.2901763916015625e-05s
Believability | Calculation of trust value for Open Data Web took 6.9141387939453125e-06s
INFO | --- Analysis for data.odw.tw took 2.8320484161376953s
Availability | SPARQL endpoint availability check for DataFAQs took 4.029273986816406e-05s
Availability | VoID file availability check for DataFAQs took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.26238203048706055s
Reputation | Calculation of the PageRank for DataFAQs took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for DataFAQs took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DataFAQs took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.123283386230469e-05s
Believability | Calculation of trust value for DataFAQs took 7.62939453125e-06s
INFO | --- Analysis for datafaqs took 2.8445823192596436s
Availability | SPARQL endpoint availability check for datahub took 6.723403930664062e-05s
Availability | VoID file availability check for datahub took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for datahub took 0.25876712799072266s
Reputation | Calculation of the PageRank for datahub took 0.02055191993713379s
Interlinking | Calculation of Degree of Connection for datahub took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for datahub took 0.0008301734924316406s
Interlinking | Calculation of Clustering coefficient for datahub took 5.364418029785156e-05s
Believability | Calculation of trust value for datahub took 7.867813110351562e-06s
INFO | --- Analysis for datahub took 2.8469696044921875s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0003314018249511719s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.2489321231842041s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020357131958007812s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 6.9141387939453125e-06s
INFO | --- Analysis for datahub-kr-datamap took 2.839468240737915s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 4.291534423828125e-05s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.2571268081665039s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.020447254180908203s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0008580684661865234s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.534027099609375e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 7.62939453125e-06s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 2.878471851348877s
Availability | SPARQL endpoint availability check for datos-artium-org took 20.94743537902832s
Availability | VoID file availability check for datos-artium-org took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.257404088973999s
Reputation | Calculation of the PageRank for datos-artium-org took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011229515075683594s
Believability | Calculation of trust value for datos-artium-org took 8.344650268554688e-06s
INFO | --- Analysis for datos-artium-org took 53.86872887611389s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 4.076957702636719e-05s
Availability | VoID file availability check for Datos.bcn.cl took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.25200939178466797s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020676136016845703s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.152557373046875e-05s
Believability | Calculation of trust value for Datos.bcn.cl took 6.9141387939453125e-06s
INFO | --- Analysis for datos-bcn-cl took 2.8092806339263916s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.39207959175109863s
Availability | VoID file availability check for datos.bne.es took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.2646453380584717s
Reputation | Calculation of the PageRank for datos.bne.es took 0.020974397659301758s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011515617370605469s
Believability | Calculation of trust value for datos.bne.es took 1.2159347534179688e-05s
INFO | --- Analysis for datos-bne-es took 3.5094857215881348s
Availability | SPARQL endpoint availability check for dbacademic took 6.818771362304688e-05s
Availability | VoID file availability check for dbacademic took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for dbacademic took 0.2537069320678711s
Reputation | Calculation of the PageRank for dbacademic took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for dbacademic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for dbacademic took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for dbacademic took 3.3855438232421875e-05s
Believability | Calculation of trust value for dbacademic took 8.106231689453125e-06s
INFO | --- Analysis for dbacademic took 2.8504855632781982s
Availability | SPARQL endpoint availability check for DBkWik took 5.245208740234375e-05s
Availability | VoID file availability check for DBkWik took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for DBkWik took 0.23902440071105957s
Reputation | Calculation of the PageRank for DBkWik took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.890296936035156e-05s
Believability | Calculation of trust value for DBkWik took 7.3909759521484375e-06s
INFO | --- Analysis for dbkwik took 2.8875672817230225s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 4.029273986816406e-05s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.26816415786743164s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.0001049041748046875s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 2.84578013420105s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 4.0531158447265625e-05s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0003886222839355469s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.25194621086120605s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.33514404296875e-05s
Believability | Calculation of trust value for dblp Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for dblp-kg took 2.8964011669158936s
Availability | SPARQL endpoint availability check for dbnary took 4.696846008300781e-05s
Availability | VoID file availability check for dbnary took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for dbnary took 0.251082181930542s
Reputation | Calculation of the PageRank for dbnary took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for dbnary took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for dbnary took 7.915496826171875e-05s
Believability | Calculation of trust value for dbnary took 8.58306884765625e-06s
INFO | --- Analysis for dbnary took 2.8024191856384277s
Availability | SPARQL endpoint availability check for DBpedia took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia took 0.00035381317138671875s
Completeness | Calculation of interlinking completeness for DBpedia took 0.25646185874938965s
Reputation | Calculation of the PageRank for DBpedia took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008816719055175781s
Believability | Calculation of trust value for DBpedia took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia took 2.831723928451538s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.2533431053161621s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.747245788574219e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 7.152557373046875e-06s
INFO | --- Analysis for dbpedia-abstract-corpus took 2.871938705444336s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.220008850097656e-05s
Availability | VoID file availability check for DBpedia Commons took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.24442672729492188s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.020981311798095703s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 7.152557373046875e-05s
Believability | Calculation of trust value for DBpedia Commons took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-commons took 2.8457584381103516s
Availability | SPARQL endpoint availability check for DBpedia in German took 4.267692565917969e-05s
Availability | VoID file availability check for DBpedia in German took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.26117920875549316s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.890296936035156e-05s
Believability | Calculation of trust value for DBpedia in German took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-de took 2.8226771354675293s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia in Greek took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.2596554756164551s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0006821155548095703s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00018715858459472656s
Believability | Calculation of trust value for DBpedia in Greek took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-el took 2.888162136077881s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 4.029273986816406e-05s
Availability | VoID file availability check for DBpedia in Spanish took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.25467419624328613s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 0.00010204315185546875s
Believability | Calculation of trust value for DBpedia in Spanish took 8.58306884765625e-06s
INFO | --- Analysis for dbpedia-es took 2.752208948135376s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 4.076957702636719e-05s
Availability | VoID file availability check for DBpedia in Basque took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.27988696098327637s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 3.314018249511719e-05s
Believability | Calculation of trust value for DBpedia in Basque took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-eu took 2.826080560684204s
Availability | SPARQL endpoint availability check for DBpedia in French took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia in French took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.2729020118713379s
Reputation | Calculation of the PageRank for DBpedia in French took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 8.749961853027344e-05s
Believability | Calculation of trust value for DBpedia in French took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia-fr took 2.809187173843384s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 4.172325134277344e-05s
Availability | VoID file availability check for DBpedia in Japanese took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.24332141876220703s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.020621061325073242s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.5367431640625e-05s
Believability | Calculation of trust value for DBpedia in Japanese took 7.3909759521484375e-06s
INFO | --- Analysis for dbpedia-ja took 2.770832061767578s
Availability | SPARQL endpoint availability check for dbpedia lite took 4.029273986816406e-05s
Availability | VoID file availability check for dbpedia lite took 0.00034427642822265625s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.25681328773498535s
Reputation | Calculation of the PageRank for dbpedia lite took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 0.00010180473327636719s
Believability | Calculation of trust value for dbpedia lite took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-lite took 2.798330783843994s
Availability | SPARQL endpoint availability check for DBpedia-Live took 4.124641418457031e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.24395203590393066s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.1948089599609375e-05s
Believability | Calculation of trust value for DBpedia-Live took 1.1205673217773438e-05s
INFO | --- Analysis for dbpedia-live took 2.8680460453033447s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia in Dutch took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.2601776123046875s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020407676696777344s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.0001621246337890625s
Believability | Calculation of trust value for DBpedia in Dutch took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia-nl took 2.895421028137207s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 4.100799560546875e-05s
Availability | VoID file availability check for DBpedia in Portuguese took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.25884580612182617s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.022659778594970703s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0011675357818603516s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 0.00010371208190917969s
Believability | Calculation of trust value for DBpedia in Portuguese took 6.9141387939453125e-06s
INFO | --- Analysis for dbpedia-pt took 2.882355213165283s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 4.0531158447265625e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.0003387928009033203s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.23961353302001953s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020125389099121094s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.075599670410156e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 6.67572021484375e-06s
INFO | --- Analysis for dbpedia-spotlight took 2.874727964401245s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 4.506111145019531e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.2746703624725342s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.747245788574219e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 2.9391469955444336s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 5.1021575927734375e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.2570011615753174s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.218650817871094e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.239776611328125e-05s
INFO | --- Analysis for dbpedia-wikidata took 2.9003982543945312s
Availability | SPARQL endpoint availability check for DBpedia took 4.00543212890625e-05s
Availability | VoID file availability check for DBpedia took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for DBpedia took 0.27626466751098633s
Reputation | Calculation of the PageRank for DBpedia took 0.02016139030456543s
Interlinking | Calculation of Degree of Connection for DBpedia took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia took 0.0006825923919677734s
Interlinking | Calculation of Clustering coefficient for DBpedia took 4.7206878662109375e-05s
Believability | Calculation of trust value for DBpedia took 8.106231689453125e-06s
INFO | --- Analysis for dbpedia_ took 2.8381078243255615s
Availability | SPARQL endpoint availability check for DBTropes took 4.172325134277344e-05s
Availability | VoID file availability check for DBTropes took 0.0005645751953125s
Completeness | Calculation of interlinking completeness for DBTropes took 0.28089284896850586s
Reputation | Calculation of the PageRank for DBTropes took 0.020415306091308594s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.679794311523438e-05s
Believability | Calculation of trust value for DBTropes took 1.1444091796875e-05s
INFO | --- Analysis for dbtropes took 3.1619365215301514s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.124641418457031e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.25940394401550293s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 3.838539123535156e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 6.9141387939453125e-06s
INFO | --- Analysis for dbtune took 2.791381597518921s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.3392181396484375e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.25188755989074707s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.459785461425781e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 2.8288140296936035s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.172325134277344e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.275132417678833s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.3855438232421875e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.152557373046875e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 2.8644847869873047s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 9.242829322814941s
Availability | VoID file availability check for DBTune.org/classical took 0.00035858154296875s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.2636139392852783s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.02158212661743164s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0010564327239990234s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 9.560585021972656e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.2159347534179688e-05s
INFO | --- Analysis for dbtune-classical took 18.812671422958374s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 8.333122730255127s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.0005078315734863281s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.24317049980163574s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.02041912078857422s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.914138793945312e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 17.88475227355957s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 8.352463245391846s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.2747213840484619s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020398855209350586s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.580352783203125e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 6.67572021484375e-06s
INFO | --- Analysis for dbtune-magnatune took 17.88456416130066s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 8.310413599014282s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.25858020782470703s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00010991096496582031s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 1.1444091796875e-05s
INFO | --- Analysis for dbtune-musicbrainz took 17.882124185562134s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 8.35258960723877s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.26462459564208984s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 5.221366882324219e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.049041748046875e-05s
INFO | --- Analysis for dbtune-myspace took 17.88141107559204s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.00022912025451660156s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.2437732219696045s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.02263927459716797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 3.552436828613281e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 6.67572021484375e-06s
INFO | --- Analysis for dclg-openuplabs took 2.849466323852539s
Availability | SPARQL endpoint availability check for data.dcs took 4.0531158447265625e-05s
Availability | VoID file availability check for data.dcs took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for data.dcs took 0.27774977684020996s
Reputation | Calculation of the PageRank for data.dcs took 0.020491838455200195s
Interlinking | Calculation of Degree of Connection for data.dcs took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for data.dcs took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.413459777832031e-05s
Believability | Calculation of trust value for data.dcs took 6.9141387939453125e-06s
INFO | --- Analysis for dcs-sheffield took 2.853210926055908s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.172325134277344e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.26114559173583984s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Germany - Bundesministerium der Finanzen - Budget took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Germany - Bundesministerium der Finanzen - Budget took 3.552436828613281e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.62939453125e-06s
INFO | --- Analysis for de-budget took 2.8612990379333496s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.124641418457031e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.2552647590637207s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.021401166915893555s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 3.933906555175781e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 7.62939453125e-06s
INFO | --- Analysis for de-gaap-ontology-lexicon took 2.8863770961761475s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 3.9577484130859375e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.24604439735412598s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.020569562911987305s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.673004150390625e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 6.9141387939453125e-06s
INFO | --- Analysis for debian-package-tracking-system took 2.9258923530578613s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 9.274482727050781e-05s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.26590943336486816s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.020213603973388672s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 3.0517578125e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 2.790883779525757s
Availability | SPARQL endpoint availability check for Demografie took 4.076957702636719e-05s
Availability | VoID file availability check for Demografie took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Demografie took 0.2489020824432373s
Reputation | Calculation of the PageRank for Demografie took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for Demografie took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Demografie took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Demografie took 3.075599670410156e-05s
Believability | Calculation of trust value for Demografie took 6.9141387939453125e-06s
INFO | --- Analysis for demografie took 2.755699872970581s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 7.224082946777344e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.27518606185913086s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.528594970703125e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 6.67572021484375e-06s
INFO | --- Analysis for desaparecidos took 2.8626317977905273s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 4.1961669921875e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.24465203285217285s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.918212890625e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 5.9604644775390625e-06s
INFO | --- Analysis for deustoentrepreneurship took 2.8746497631073s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 4.1961669921875e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.2646796703338623s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.000102996826171875s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 7.3909759521484375e-06s
INFO | --- Analysis for deustotech took 2.821477174758911s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.3448143005371094s
Availability | VoID file availability check for Deutsche Biographie took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.29210591316223145s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.02084636688232422s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 4.124641418457031e-05s
Believability | Calculation of trust value for Deutsche Biographie took 7.867813110351562e-06s
INFO | --- Analysis for deutsche-biographie took 4.46587610244751s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 4.172325134277344e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.26575136184692383s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.02074122428894043s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.53131103515625e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 2.91334867477417s
Availability | SPARQL endpoint availability check for dev8d took 4.029273986816406e-05s
Availability | VoID file availability check for dev8d took 0.0003299713134765625s
Completeness | Calculation of interlinking completeness for dev8d took 0.25476765632629395s
Reputation | Calculation of the PageRank for dev8d took 0.020880699157714844s
Interlinking | Calculation of Degree of Connection for dev8d took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for dev8d took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.961822509765625e-05s
Believability | Calculation of trust value for dev8d took 6.4373016357421875e-06s
INFO | --- Analysis for dev8d took 2.8594400882720947s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 4.0531158447265625e-05s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.252152681350708s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.021869897842407227s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 5.555152893066406e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 7.152557373046875e-06s
INFO | --- Analysis for dewey_decimal_classification took 2.793998956680298s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.100799560546875e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.0003082752227783203s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.28340864181518555s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.020674705505371094s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 3.361701965332031e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 7.3909759521484375e-06s
INFO | --- Analysis for DHSVM took 2.8531694412231445s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 4.291534423828125e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.2665231227874756s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.0208280086517334s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 3.218650817871094e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 7.62939453125e-06s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 2.832197427749634s
Availability | SPARQL endpoint availability check for Diavgeia took 4.124641418457031e-05s
Availability | VoID file availability check for Diavgeia took 0.0003314018249511719s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.24389171600341797s
Reputation | Calculation of the PageRank for Diavgeia took 0.020239591598510742s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.392333984375e-05s
Believability | Calculation of trust value for Diavgeia took 5.9604644775390625e-06s
INFO | --- Analysis for diavgeia took 2.7606256008148193s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 4.172325134277344e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.23770499229431152s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011515617370605469s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.344650268554688e-06s
INFO | --- Analysis for didactalia took 2.8049843311309814s
Availability | SPARQL endpoint availability check for diigo.feed took 4.100799560546875e-05s
Availability | VoID file availability check for diigo.feed took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.25977659225463867s
Reputation | Calculation of the PageRank for diigo.feed took 0.020572662353515625s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 3.075599670410156e-05s
Believability | Calculation of trust value for diigo.feed took 8.344650268554688e-06s
INFO | --- Analysis for diigo-feed took 2.7783567905426025s
Availability | SPARQL endpoint availability check for DisGeNET took 4.124641418457031e-05s
Availability | VoID file availability check for DisGeNET took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.2536802291870117s
Reputation | Calculation of the PageRank for DisGeNET took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for DisGeNET took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DisGeNET took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.00020551681518554688s
Believability | Calculation of trust value for DisGeNET took 7.3909759521484375e-06s
INFO | --- Analysis for disgenet took 2.7997829914093018s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 4.458427429199219e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.25792598724365234s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 3.0040740966796875e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 8.344650268554688e-06s
INFO | --- Analysis for disk took 2.8294143676757812s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 4.00543212890625e-05s
Availability | VoID file availability check for Distritos de Zaragoza took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.271742582321167s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 3.0279159545898438e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 7.3909759521484375e-06s
INFO | --- Analysis for distritos-zaragoza took 2.7845399379730225s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 7.724761962890625e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0003108978271484375s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.2344043254852295s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020563364028930664s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 3.3855438232421875e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.2159347534179688e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 2.7961206436157227s
Availability | SPARQL endpoint availability check for DM2E took 4.315376281738281e-05s
Availability | VoID file availability check for DM2E took 0.0006775856018066406s
Completeness | Calculation of interlinking completeness for DM2E took 0.2739372253417969s
Reputation | Calculation of the PageRank for DM2E took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.0001068115234375s
Believability | Calculation of trust value for DM2E took 1.0967254638671875e-05s
INFO | --- Analysis for dm2e took 3.554582118988037s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 7.009506225585938e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.27488088607788086s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.02074909210205078s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.170967102050781e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 7.152557373046875e-06s
INFO | --- Analysis for dmoz_rdf_dump took 2.930720567703247s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 7.081031799316406e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0006325244903564453s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.25559115409851074s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.02150869369506836s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.000986337661743164s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.0001766681671142578s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 6.4373016357421875e-06s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 2.8338029384613037s
Availability | SPARQL endpoint availability check for DOAP Store took 4.00543212890625e-05s
Availability | VoID file availability check for DOAP Store took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.27315664291381836s
Reputation | Calculation of the PageRank for DOAP Store took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for DOAP Store took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DOAP Store took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 3.147125244140625e-05s
Believability | Calculation of trust value for DOAP Store took 7.3909759521484375e-06s
INFO | --- Analysis for doap_store took 2.8255815505981445s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 6.413459777832031e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.2630584239959717s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020587682723999023s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 6.604194641113281e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 7.867813110351562e-06s
INFO | --- Analysis for doi took 2.8881053924560547s
Availability | SPARQL endpoint availability check for Driggu Florentino took 4.124641418457031e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.2541975975036621s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 3.0517578125e-05s
Believability | Calculation of trust value for Driggu Florentino took 7.3909759521484375e-06s
INFO | --- Analysis for Driggu took 2.866086959838867s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 4.100799560546875e-05s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.2625241279602051s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.7670135498046875e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 7.867813110351562e-06s
INFO | --- Analysis for drug-data-hifm took 2.8854286670684814s
Availability | SPARQL endpoint availability check for dspace took 8.249282836914062e-05s
Availability | VoID file availability check for dspace took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for dspace took 0.2764010429382324s
Reputation | Calculation of the PageRank for dspace took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for dspace took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dspace took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for dspace took 3.147125244140625e-05s
Believability | Calculation of trust value for dspace took 7.3909759521484375e-06s
INFO | --- Analysis for dspace took 2.8211352825164795s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 4.100799560546875e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.24769902229309082s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.02092909812927246s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.361701965332031e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 7.867813110351562e-06s
INFO | --- Analysis for duraark-linked-building-data took 2.803931951522827s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 4.1484832763671875e-05s
Availability | VoID file availability check for MetaLex Document Server took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.26041078567504883s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.0207822322845459s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.457069396972656e-05s
Believability | Calculation of trust value for MetaLex Document Server took 8.106231689453125e-06s
INFO | --- Analysis for dutch-national-regulations-metalex took 2.821521520614624s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.633453369140625s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.0007359981536865234s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.25626468658447266s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.814697265625e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 6.9141387939453125e-06s
INFO | --- Analysis for dutch-ships-and-sailors took 7.7503743171691895s
Availability | SPARQL endpoint availability check for DWS-Group took 4.220008850097656e-05s
Availability | VoID file availability check for DWS-Group took 0.0003254413604736328s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.23875737190246582s
Reputation | Calculation of the PageRank for DWS-Group took 0.025031328201293945s
Interlinking | Calculation of Degree of Connection for DWS-Group took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for DWS-Group took 0.0011970996856689453s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00013589859008789062s
Believability | Calculation of trust value for DWS-Group took 1.0013580322265625e-05s
INFO | --- Analysis for dws-group took 2.888253927230835s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.100799560546875e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.25298523902893066s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.02067708969116211s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 3.170967102050781e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 9.5367431640625e-06s
INFO | --- Analysis for E1 took 2.7784526348114014s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 4.029273986816406e-05s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.2509932518005371s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00013113021850585938s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-alaska took 2.7448418140411377s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.2603282928466797s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.021114826202392578s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.5789947509765625e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 7.867813110351562e-06s
INFO | --- Analysis for eagle-i-cau took 2.865510940551758s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 4.291534423828125e-05s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.24886655807495117s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 6.556510925292969e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 8.344650268554688e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.7718050479888916s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.24987196922302246s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.632110595703125e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-cdrewu took 2.803311586380005s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 4.839897155761719e-05s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.254396915435791s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.02099442481994629s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00013875961303710938s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-dartmouth took 2.894326686859131s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 4.4345855712890625e-05s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.2516176700592041s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.028226852416992188s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0010488033294677734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 0.00010800361633300781s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 7.152557373046875e-06s
INFO | --- Analysis for eagle-i-famu took 2.85908579826355s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.26134777069091797s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.021146774291992188s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.0001323223114013672s
Believability | Calculation of trust value for eagle-i @ Harvard University took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-harvard took 2.848705530166626s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 4.124641418457031e-05s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.25447988510131836s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020900726318359375s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.00012612342834472656s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-hawaii took 2.8476016521453857s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 5.745887756347656e-05s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.25699353218078613s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.02095317840576172s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 7.176399230957031e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-howard took 2.8042821884155273s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 4.00543212890625e-05s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.25542306900024414s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020395278930664062s
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.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 6.246566772460938e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-hunter-cuny took 2.852938652038574s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 4.124641418457031e-05s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.261246919631958s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00012612342834472656s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-jsu took 2.785039186477661s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 5.459785461425781e-05s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.23976445198059082s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.0208895206451416s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 3.9577484130859375e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-meharry took 2.795609712600708s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 4.076957702636719e-05s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.24786090850830078s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02063775062561035s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 0.00010037422180175781s
Believability | Calculation of trust value for eagle-i @ Montana State University took 8.106231689453125e-06s
INFO | --- Analysis for eagle-i-montana took 2.8563687801361084s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 8.821487426757812e-05s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.25499606132507324s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.020378828048706055s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.608268737792969e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-msm took 2.8702051639556885s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 4.172325134277344e-05s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.2435901165008545s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02058124542236328s
Interlinking | Calculation of Degree of Connection for eagle-i @ Oregon Health and Science University took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i @ Oregon Health and Science University took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001289844512939453s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 7.62939453125e-06s
INFO | --- Analysis for eagle-i-ohsu took 2.7763888835906982s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 4.1961669921875e-05s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.24626970291137695s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.103515625e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-psm took 2.795337438583374s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 4.124641418457031e-05s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.27605485916137695s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02054882049560547s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-tsu took 2.847289562225342s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 4.8160552978515625e-05s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.2471780776977539s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.021485090255737305s
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.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 9.059906005859375e-06s
INFO | --- Analysis for eagle-i-tuskegee took 2.8624470233917236s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.25780344009399414s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.02029871940612793s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Universidad Central del Caribe took 9.775161743164062e-05s
Believability | Calculation of trust value for eagle-i @ Universidad Central del Caribe took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-uccaribe took 2.788011312484741s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.24293875694274902s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.027042150497436523s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00015997886657714844s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 3.337860107421875e-05s
INFO | --- Analysis for eagle-i-upr took 2.8998830318450928s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 4.076957702636719e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.2530364990234375s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.02084183692932129s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007817745208740234s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.437301635742188e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.3589859008789062e-05s
INFO | --- Analysis for eagle-i-utep took 2.8435370922088623s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 4.315376281738281e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.273937463760376s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.020607709884643555s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.699562072753906e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 6.9141387939453125e-06s
INFO | --- Analysis for eagle-i-utsa took 2.9102420806884766s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 4.100799560546875e-05s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.26523590087890625s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 9.083747863769531e-05s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-vanderbilt took 3.2020535469055176s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 4.38690185546875e-05s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.2563512325286865s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.020772457122802734s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.390975952148438e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 7.3909759521484375e-06s
INFO | --- Analysis for eagle-i-xula took 2.8280389308929443s
Availability | SPARQL endpoint availability check for Emergency situation took 4.220008850097656e-05s
Availability | VoID file availability check for Emergency situation took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.26314568519592285s
Reputation | Calculation of the PageRank for Emergency situation took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 5.984306335449219e-05s
Believability | Calculation of trust value for Emergency situation took 7.152557373046875e-06s
INFO | --- Analysis for Earthquake took 2.9298508167266846s
Availability | SPARQL endpoint availability check for ESO took 4.0531158447265625e-05s
Availability | VoID file availability check for ESO took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for ESO took 0.2761569023132324s
Reputation | Calculation of the PageRank for ESO took 0.020736217498779297s
Interlinking | Calculation of Degree of Connection for ESO took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for ESO took 8.058547973632812e-05s
Believability | Calculation of trust value for ESO took 8.106231689453125e-06s
INFO | --- Analysis for Earthquake_case took 2.845226287841797s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 4.124641418457031e-05s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.26174497604370117s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.021107196807861328s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010228157043457031s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ecb-linked-data took 2.836808204650879s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 7.319450378417969e-05s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0002827644348144531s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.25893735885620117s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020570039749145508s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 3.814697265625e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 1.33514404296875e-05s
INFO | --- Analysis for ecb-statistics-linked-data took 2.843201160430908s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.6136431694030762s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.2553095817565918s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.02057170867919922s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 7.128715515136719e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for ecco-tcp-linked-data took 5.392247915267944s
Availability | SPARQL endpoint availability check for ECLAP took 21.119823217391968s
Availability | VoID file availability check for ECLAP took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for ECLAP took 0.25795865058898926s
Reputation | Calculation of the PageRank for ECLAP took 0.020937204360961914s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.000978231430053711s
Interlinking | Calculation of Clustering coefficient for ECLAP took 4.935264587402344e-05s
Believability | Calculation of trust value for ECLAP took 3.4809112548828125e-05s
INFO | --- Analysis for eclap took 54.167651414871216s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 4.267692565917969e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.2599301338195801s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.020905256271362305s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007688999176025391s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.2636184692382812e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 7.3909759521484375e-06s
INFO | --- Analysis for ECNU-GISer took 2.839200258255005s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.1961669921875e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.23912811279296875s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020656347274780273s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.4836273193359375e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.821487426757812e-06s
INFO | --- Analysis for ecs took 2.7590343952178955s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 4.220008850097656e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.27921414375305176s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020674467086791992s
Interlinking | Calculation of Degree of Connection for Edificios Históricos en Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Edificios Históricos en Zaragoza took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 3.147125244140625e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 7.152557373046875e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 2.8622853755950928s
Availability | SPARQL endpoint availability check for Edublogs took 4.0531158447265625e-05s
Availability | VoID file availability check for Edublogs took 0.0003933906555175781s
Completeness | Calculation of interlinking completeness for Edublogs took 0.28090810775756836s
Reputation | Calculation of the PageRank for Edublogs took 0.021457195281982422s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0010595321655273438s
Interlinking | Calculation of Clustering coefficient for Edublogs took 0.0001251697540283203s
Believability | Calculation of trust value for Edublogs took 1.2874603271484375e-05s
INFO | --- Analysis for edublogs took 2.9207797050476074s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 4.124641418457031e-05s
Availability | VoID file availability check for education.data.gov.uk took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.248978853225708s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.0206756591796875s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 9.012222290039062e-05s
Believability | Calculation of trust value for education.data.gov.uk took 8.106231689453125e-06s
INFO | --- Analysis for education-data-gov-uk took 2.789315700531006s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.029273986816406e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.27335691452026367s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.2901763916015625e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 7.152557373046875e-06s
INFO | --- Analysis for education-openuplabs took 2.8370723724365234s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 8.106231689453125e-05s
Availability | VoID file availability check for Educational programs - SISVU took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.24971866607666016s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.020598888397216797s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 4.76837158203125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 7.3909759521484375e-06s
INFO | --- Analysis for educationalprograms_sisvu took 2.8293871879577637s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 4.124641418457031e-05s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.2492203712463379s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.02067422866821289s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.000804901123046875s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 4.029273986816406e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.3113021850585938e-05s
INFO | --- Analysis for eea took 2.787283182144165s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 4.0531158447265625e-05s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.26342129707336426s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.021387338638305664s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.984306335449219e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 7.62939453125e-06s
INFO | --- Analysis for eea-rod took 2.8347017765045166s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 4.076957702636719e-05s
Availability | VoID file availability check for EEA Vocabularies took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.2595841884613037s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 8.726119995117188e-05s
Believability | Calculation of trust value for EEA Vocabularies took 7.152557373046875e-06s
INFO | --- Analysis for eea-vocabularies took 2.824953317642212s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 5.888938903808594e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.25663208961486816s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020695924758911133s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.361701965332031e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for ege-university-linked-open-data took 2.8340675830841064s
Availability | SPARQL endpoint availability check for E-Government Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for E-Government Ontology took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.24659442901611328s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020598649978637695s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for E-Government Ontology took 7.867813110351562e-06s
INFO | --- Analysis for EGovOntology took 2.699993371963501s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 3.981590270996094e-05s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.23712563514709473s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.02399420738220215s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0011529922485351562s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 6.175041198730469e-05s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 7.62939453125e-06s
INFO | --- Analysis for ei2a took 2.8366475105285645s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.4345855712890625e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.26343250274658203s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010442733764648438s
Believability | Calculation of trust value for EIONET RDF Data took 1.1682510375976562e-05s
INFO | --- Analysis for eionet-rdf took 2.883960485458374s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 5.054473876953125e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.29019618034362793s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 2.956390380859375e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 7.62939453125e-06s
INFO | --- Analysis for ElgooG_ took 2.8978536128997803s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 4.0531158447265625e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.2741231918334961s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 3.0279159545898438e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.1205673217773438e-05s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 2.8213350772857666s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.25655174255371094s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.020214080810546875s
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.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.176399230957031e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 8.344650268554688e-06s
INFO | --- Analysis for elviajero took 2.8656694889068604s
Availability | SPARQL endpoint availability check for EMN took 3.981590270996094e-05s
Availability | VoID file availability check for EMN took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for EMN took 0.263338565826416s
Reputation | Calculation of the PageRank for EMN took 0.020821571350097656s
Interlinking | Calculation of Degree of Connection for EMN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EMN took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for EMN took 3.981590270996094e-05s
Believability | Calculation of trust value for EMN took 1.33514404296875e-05s
INFO | --- Analysis for emn took 2.8445777893066406s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 5.364418029785156e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.0003254413604736328s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.2634153366088867s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.0207521915435791s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 5.4836273193359375e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for enakting-co2emission took 2.8407604694366455s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 4.76837158203125e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.24865055084228516s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.02066206932067871s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.410743713378906e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for enakting-crime took 2.879361391067505s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.25821590423583984s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 4.1484832763671875e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 8.106231689453125e-06s
INFO | --- Analysis for enakting-energy took 2.8384335041046143s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 4.1961669921875e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.2543671131134033s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.202957153320312e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 9.059906005859375e-06s
INFO | --- Analysis for enakting-mortality took 2.8285975456237793s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.887580871582031e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.24332141876220703s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.023404359817504883s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0011548995971679688s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.9114227294921875e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for enakting-nhs took 2.8379976749420166s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.24972867965698242s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.054473876953125e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for enakting-population took 2.7858877182006836s
Availability | SPARQL endpoint availability check for Enel Shops took 3.9577484130859375e-05s
Availability | VoID file availability check for Enel Shops took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.2708263397216797s
Reputation | Calculation of the PageRank for Enel Shops took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Enel Shops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.075599670410156e-05s
Believability | Calculation of trust value for Enel Shops took 7.152557373046875e-06s
INFO | --- Analysis for enel-shops took 2.8958001136779785s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.982948303222656e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.2601957321166992s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007517337799072266s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.1948089599609375e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 7.3909759521484375e-06s
INFO | --- Analysis for energy-efficiency took 2.7736480236053467s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.00033664703369140625s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.25280237197875977s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.020757436752319336s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 2.8510446548461914s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 7.915496826171875e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.2533993721008301s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 6.4373016357421875e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 2.8629910945892334s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 5.078315734863281e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.2684152126312256s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.02025628089904785s
Interlinking | Calculation of Degree of Connection for English Heritage Components Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Components Thesaurus took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 2.86102294921875e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.9104623794555664s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.23956036567687988s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 2.8481712341308594s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.24381709098815918s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 2.9325485229492188e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 2.857189893722534s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 5.3882598876953125e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.258831262588501s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.020051956176757812s
Interlinking | Calculation of Degree of Connection for English Heritage Maritime Craft Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Heritage Maritime Craft Thesaurus took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 2.864053249359131s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 4.029273986816406e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.25871825218200684s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 2.8133392333984375e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.833474636077881s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 0.6426486968994141s
Availability | VoID file availability check for English Heritage Periods List took 0.00025463104248046875s
Extra | Recovery of all triples for English Heritage Periods List took 0.31854248046875s
Performance | Total latancy measurement for English Heritage Periods List took 1.545487880706787s
Amount of data | Number of triples check for English Heritage Periods List took 0.535921573638916s
Versatility | Languages check for English Heritage Periods List took 0.2472972869873047s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5496673583984375s
Security | Check HTTPS for English Heritage Periods List took 0.23535609245300293s
Interpretability | RDF structures check for English Heritage Periods List took 0.26932764053344727s
Versatility | Serialization formats check for English Heritage Periods List took 0.5036396980285645s
Availability | RDF dump link check for English Heritage Periods List took 0.3204340934753418s
License | MR license check for English Heritage Periods List took 0.42537426948547363s
License | HR license check for English Heritage Periods List took 0.34440088272094727s
Amount of data | Number of property check for English Heritage Periods List took 0.351959228515625s
Understandability | Number of label check for English Heritage Periods List took 0.3868386745452881s
Understandability | URI regex check for English Heritage Periods List took 0.71738600730896s
Understandability | Vocabs check for English Heritage Periods List took 0.4327363967895508s
Verifiability | Authors check for English Heritage Periods List took 0.5378367900848389s
Verifiability | Publishers check for English Heritage Periods List took 0.35683774948120117s
Performance | Throughput check for English Heritage Periods List took 12.080096244812012s
Amount of data | Check the number of entities for English Heritage Periods List took 7.843971252441406e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.34000158309936523s
Interlinking | sameAs chians check for English Heritage Periods List took 0.29458189010620117s
Interlinking | skos check for English Heritage Periods List took 0.31114745140075684s
Interlinking | skos check for English Heritage Periods List took 0.3442411422729492s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.4125335216522217s
Currency | Creation date check for English Heritage Periods List took 0.7403078079223633s
Currency | Modification date check for English Heritage Periods List took 1.7756435871124268s
Rep.Conc. | URIs length for English Heritage Periods List took 0.6226747035980225s
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.34218454360961914s
Accuracy | Check Functional Property for English Heritage Periods List took 0.29360270500183105s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.30709028244018555s
Consistency | Disjoint class check for English Heritage Periods List took 0.2926304340362549s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.3201563358306885s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.7195148468017578s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.00014162063598632812s
Security | Sign check for English Heritage Periods List took 0.3614935874938965s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.26940274238586426s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.361701965332031e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.1920928955078125e-06s
Believability | Calculation of trust value for English Heritage Periods List took 7.152557373046875e-06s
INFO | --- Analysis for english-heritage-periods-list took 49.253501415252686s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 4.076957702636719e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.2763943672180176s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.170967102050781e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 6.67572021484375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 2.855694532394409s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Score 2010 took 4.029273986816406e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Score 2010 took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.25022363662719727s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 3.1948089599609375e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 6.198883056640625e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 2.7876508235931396s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 4.2438507080078125e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.23481297492980957s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 2.86102294921875e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 6.4373016357421875e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 2.8924832344055176s
Availability | SPARQL endpoint availability check for English WordNet took 3.981590270996094e-05s
Availability | VoID file availability check for English WordNet took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for English WordNet took 0.24231767654418945s
Reputation | Calculation of the PageRank for English WordNet took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for English WordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English WordNet took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.337860107421875e-05s
Believability | Calculation of trust value for English WordNet took 1.0967254638671875e-05s
INFO | --- Analysis for english-wordnet took 2.834779739379883s
Availability | SPARQL endpoint availability check for English Heritage Places took 4.076957702636719e-05s
Availability | VoID file availability check for English Heritage Places took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.25215673446655273s
Reputation | Calculation of the PageRank for English Heritage Places took 0.020497560501098633s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.1948089599609375e-05s
Believability | Calculation of trust value for English Heritage Places took 7.62939453125e-06s
INFO | --- Analysis for englishheritage_places took 2.9064443111419678s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 4.100799560546875e-05s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.00036525726318359375s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.2651371955871582s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.02053046226501465s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.58306884765625e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 7.152557373046875e-06s
INFO | --- Analysis for enipedia took 2.8985843658447266s
Availability | SPARQL endpoint availability check for Enslaved.org took 4.0531158447265625e-05s
Availability | VoID file availability check for Enslaved.org took 0.0006201267242431641s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.2606618404388428s
Reputation | Calculation of the PageRank for Enslaved.org took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 2.8371810913085938e-05s
Believability | Calculation of trust value for Enslaved.org took 1.1920928955078125e-05s
INFO | --- Analysis for enslaved.org took 3.6259961128234863s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 4.029273986816406e-05s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.23463988304138184s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020557641983032227s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 4.839897155761719e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for entice-graph took 2.7642738819122314s
Availability | SPARQL endpoint availability check for Entrez Gene took 7.867813110351562e-05s
Availability | VoID file availability check for Entrez Gene took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.2786827087402344s
Reputation | Calculation of the PageRank for Entrez Gene took 0.020609378814697266s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0006778240203857422s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 3.647804260253906e-05s
Believability | Calculation of trust value for Entrez Gene took 1.239776611328125e-05s
INFO | --- Analysis for entrez_gene took 2.8334827423095703s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 4.100799560546875e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.24912548065185547s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0006775856018066406s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 2.8848648071289062e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 1.9550323486328125e-05s
INFO | --- Analysis for entrez_gene_extract took 2.7858548164367676s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 4.0531158447265625e-05s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.26579904556274414s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.020670175552368164s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0008099079132080078s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.269050598144531e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 6.67572021484375e-06s
INFO | --- Analysis for environment-agency-bathing-water-quality took 2.826948642730713s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 3.886222839355469e-05s
Availability | VoID file availability check for environment.data.gov.uk took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.27842259407043457s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.020461320877075195s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0006809234619140625s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.267692565917969e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.33514404296875e-05s
INFO | --- Analysis for environment-data-gov-uk took 2.87585186958313s
Availability | SPARQL endpoint availability check for EARTh took 4.172325134277344e-05s
Availability | VoID file availability check for EARTh took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for EARTh took 0.25407862663269043s
Reputation | Calculation of the PageRank for EARTh took 0.02051520347595215s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.369850158691406e-05s
Believability | Calculation of trust value for EARTh took 7.152557373046875e-06s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 2.8585963249206543s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 4.076957702636719e-05s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.253659725189209s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 2.9087066650390625e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 7.62939453125e-06s
INFO | --- Analysis for EO_metadata took 2.853667974472046s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 3.9577484130859375e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.2539536952972412s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0007748603820800781s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 2.86102294921875e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 7.62939453125e-06s
INFO | --- Analysis for EOKP-Datasets took 2.8577892780303955s
Availability | SPARQL endpoint availability check for EPA-CDR took 4.1961669921875e-05s
Availability | VoID file availability check for EPA-CDR took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.25179409980773926s
Reputation | Calculation of the PageRank for EPA-CDR took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.838539123535156e-05s
Believability | Calculation of trust value for EPA-CDR took 7.867813110351562e-06s
INFO | --- Analysis for epa-cdr took 2.8748018741607666s
Availability | SPARQL endpoint availability check for EPA-FRS took 4.1484832763671875e-05s
Availability | VoID file availability check for EPA-FRS took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.24478793144226074s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020919084548950195s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.772445678710938e-05s
Believability | Calculation of trust value for EPA-FRS took 7.3909759521484375e-06s
INFO | --- Analysis for epa-frs took 2.8310067653656006s
Availability | SPARQL endpoint availability check for EPA-RCRA took 4.00543212890625e-05s
Availability | VoID file availability check for EPA-RCRA took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.24319052696228027s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020483970642089844s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.170967102050781e-05s
Believability | Calculation of trust value for EPA-RCRA took 7.3909759521484375e-06s
INFO | --- Analysis for epa-rcra took 2.8420886993408203s
Availability | SPARQL endpoint availability check for EPA-SRS took 5.1021575927734375e-05s
Availability | VoID file availability check for EPA-SRS took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.26416492462158203s
Reputation | Calculation of the PageRank for EPA-SRS took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.176399230957031e-05s
Believability | Calculation of trust value for EPA-SRS took 8.344650268554688e-06s
INFO | --- Analysis for epa-srs took 2.808370590209961s
Availability | SPARQL endpoint availability check for EPA-TRI took 4.458427429199219e-05s
Availability | VoID file availability check for EPA-TRI took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.2534475326538086s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020801305770874023s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 4.172325134277344e-05s
Believability | Calculation of trust value for EPA-TRI took 6.198883056640625e-06s
INFO | --- Analysis for epa-tri took 2.7961013317108154s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.076957702636719e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.2679939270019531s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 6.914138793945312e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 6.67572021484375e-06s
INFO | --- Analysis for epo took 2.7773492336273193s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 4.887580871582031e-05s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.2548513412475586s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.020232677459716797s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.00012493133544921875s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 6.198883056640625e-06s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 2.8209269046783447s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 4.00543212890625e-05s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.25025272369384766s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 8.559226989746094e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 6.67572021484375e-06s
INFO | --- Analysis for eprtr took 2.8988170623779297s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 4.0531158447265625e-05s
Availability | VoID file availability check for Railway Infrastructure KG took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.27227020263671875s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 2.9325485229492188e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 6.67572021484375e-06s
INFO | --- Analysis for ERAKG took 2.8938300609588623s
Availability | SPARQL endpoint availability check for reg took 4.124641418457031e-05s
Availability | VoID file availability check for reg took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for reg took 0.27118492126464844s
Reputation | Calculation of the PageRank for reg took 0.020400524139404297s
Interlinking | Calculation of Degree of Connection for reg took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for reg took 0.0006682872772216797s
Interlinking | Calculation of Clustering coefficient for reg took 1.1205673217773438e-05s
Believability | Calculation of trust value for reg took 7.3909759521484375e-06s
INFO | --- Analysis for erg took 2.88836932182312s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 3.981590270996094e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.2522122859954834s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 2.8133392333984375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 7.152557373046875e-06s
INFO | --- Analysis for es-msssi-drug-prices took 2.89164137840271s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 5.2928924560546875e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0005407333374023438s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.2754697799682617s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.020659446716308594s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 8.749961853027344e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 6.9141387939453125e-06s
INFO | --- Analysis for esd-standards took 2.9843597412109375s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 4.124641418457031e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.25574707984924316s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0006785392761230469s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 8.988380432128906e-05s
Believability | Calculation of trust value for ESD-Toolkit took 6.9141387939453125e-06s
INFO | --- Analysis for esd-toolkit took 2.7829360961914062s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.839897155761719e-05s
Availability | VoID file availability check for Dataset Esis took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.26361751556396484s
Reputation | Calculation of the PageRank for Dataset Esis took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.075599670410156e-05s
Believability | Calculation of trust value for Dataset Esis took 7.152557373046875e-06s
INFO | --- Analysis for esislearning took 2.8391075134277344s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 4.1484832763671875e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.25273680686950684s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 2.9802322387695312e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 8.106231689453125e-06s
INFO | --- Analysis for ESV took 2.865205764770508s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 4.124641418457031e-05s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.26691150665283203s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 6.4373016357421875e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 2.8734025955200195s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 5.459785461425781e-05s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.2646949291229248s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0006787776947021484s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.176399230957031e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 7.152557373046875e-06s
INFO | --- Analysis for eu-agencies-bodies took 2.9122495651245117s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.9577484130859375e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.269258975982666s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.0517578125e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.1444091796875e-05s
INFO | --- Analysis for eu-dgt-tm took 2.843083381652832s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 4.029273986816406e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.248612642288208s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for Institutions and Bodies of the European Union took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Institutions and Bodies of the European Union took 0.0006775856018066406s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.176399230957031e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 7.152557373046875e-06s
INFO | --- Analysis for eu-institutions took 2.8377578258514404s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 4.100799560546875e-05s
Availability | VoID file availability check for EU Parliament Media Library took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.26790499687194824s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.020397424697875977s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0006799697875976562s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.075599670410156e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 6.67572021484375e-06s
INFO | --- Analysis for eu-parliament-media took 2.860813856124878s
Availability | SPARQL endpoint availability check for EU Who Is Who took 4.1961669921875e-05s
Availability | VoID file availability check for EU Who Is Who took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.23301196098327637s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020599842071533203s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.4332275390625e-05s
Believability | Calculation of trust value for EU Who Is Who took 7.867813110351562e-06s
INFO | --- Analysis for eu-who-is-who took 2.839831829071045s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 4.887580871582031e-05s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.2620875835418701s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.02056431770324707s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 3.743171691894531e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 5.9604644775390625e-06s
INFO | --- Analysis for eumida-linked-data took 2.9307467937469482s
Availability | SPARQL endpoint availability check for European Nature Information System took 4.029273986816406e-05s
Availability | VoID file availability check for European Nature Information System took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.2683415412902832s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.0001347064971923828s
Believability | Calculation of trust value for European Nature Information System took 6.67572021484375e-06s
INFO | --- Analysis for eunis took 2.830315589904785s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.2438507080078125e-05s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.26111769676208496s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 7.009506225585938e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for eur-lex-rdf took 2.8651037216186523s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 5.340576171875e-05s
Availability | VoID file availability check for Standard Eurobarometer took 0.0002956390380859375s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.24260449409484863s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.029273986816406e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 1.1682510375976562e-05s
INFO | --- Analysis for eurobarometer-standard took 2.80523681640625s
Availability | SPARQL endpoint availability check for European Election Results took 4.1484832763671875e-05s
Availability | VoID file availability check for European Election Results took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for European Election Results took 0.26663875579833984s
Reputation | Calculation of the PageRank for European Election Results took 0.02042841911315918s
Interlinking | Calculation of Degree of Connection for European Election Results took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Election Results took 0.00083160400390625s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.4332275390625e-05s
Believability | Calculation of trust value for European Election Results took 6.9141387939453125e-06s
INFO | --- Analysis for european-election-results took 2.8134512901306152s
Availability | SPARQL endpoint availability check for EPO patents took 4.0531158447265625e-05s
Availability | VoID file availability check for EPO patents took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for EPO patents took 0.2515897750854492s
Reputation | Calculation of the PageRank for EPO patents took 0.02017998695373535s
Interlinking | Calculation of Degree of Connection for EPO patents took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPO patents took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for EPO patents took 3.6716461181640625e-05s
Believability | Calculation of trust value for EPO patents took 6.67572021484375e-06s
INFO | --- Analysis for European_Patent_Information took 2.8634696006774902s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 4.172325134277344e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.27755284309387207s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020224809646606445s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.0006799697875976562s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 2.7894973754882812e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 1.1920928955078125e-05s
INFO | --- Analysis for europeana-lod took 2.8048527240753174s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 4.363059997558594e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.2520720958709717s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02034759521484375s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.274482727050781e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 6.4373016357421875e-06s
INFO | --- Analysis for europeana-lod-v1 took 2.728863477706909s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.051727294921875s
Availability | VoID file availability check for Europeana SPARQL took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.28401613235473633s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.021798372268676758s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 5.125999450683594e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.1444091796875e-05s
INFO | --- Analysis for europeana-sparql took 2.986353635787964s
Availability | SPARQL endpoint availability check for EuroSentiment took 5.4836273193359375e-05s
Availability | VoID file availability check for EuroSentiment took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.23901653289794922s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020284175872802734s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.933906555175781e-05s
Believability | Calculation of trust value for EuroSentiment took 7.867813110351562e-06s
INFO | --- Analysis for eurosentiment took 2.873281717300415s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 4.00543212890625e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.26281166076660156s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.653236389160156e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 7.3909759521484375e-06s
INFO | --- Analysis for eurostat-rdf took 2.807537078857422s
Availability | SPARQL endpoint availability check for EuroVoc took 4.1484832763671875e-05s
Availability | VoID file availability check for EuroVoc took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.27692651748657227s
Reputation | Calculation of the PageRank for EuroVoc took 0.02057480812072754s
Interlinking | Calculation of Degree of Connection for EuroVoc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for EuroVoc took 0.0007696151733398438s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 7.2479248046875e-05s
Believability | Calculation of trust value for EuroVoc took 7.3909759521484375e-06s
INFO | --- Analysis for eurovoc took 2.853421449661255s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 8.797645568847656e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.26606249809265137s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.020859241485595703s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 3.7670135498046875e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 1.2159347534179688e-05s
INFO | --- Analysis for eurovoc-in-skos took 2.858114004135132s
Availability | SPARQL endpoint availability check for European Television Heritage took 5.2928924560546875e-05s
Availability | VoID file availability check for European Television Heritage took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.24471187591552734s
Reputation | Calculation of the PageRank for European Television Heritage took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 2.956390380859375e-05s
Believability | Calculation of trust value for European Television Heritage took 6.9141387939453125e-06s
INFO | --- Analysis for euscreen took 2.8112058639526367s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.1484832763671875e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0005280971527099609s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.2606532573699951s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.021439075469970703s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0006761550903320312s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.673004150390625e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 6.9141387939453125e-06s
INFO | --- Analysis for euskadi-farmacias took 2.811924695968628s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 4.601478576660156e-05s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.28043675422668457s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.0279159545898438e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 6.9141387939453125e-06s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 2.886897563934326s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 4.291534423828125e-05s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.27484130859375s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Edinburgh University Theatre Company Productions took 7.05718994140625e-05s
Believability | Calculation of trust value for Edinburgh University Theatre Company Productions took 6.67572021484375e-06s
INFO | --- Analysis for eutc-productions took 2.87007737159729s
Availability | SPARQL endpoint availability check for EventMedia took 0.31714773178100586s
Availability | VoID file availability check for EventMedia took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for EventMedia took 0.2559041976928711s
Reputation | Calculation of the PageRank for EventMedia took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010752677917480469s
Believability | Calculation of trust value for EventMedia took 7.3909759521484375e-06s
INFO | --- Analysis for event-media took 3.4335782527923584s
Availability | SPARQL endpoint availability check for EventKG took 4.673004150390625e-05s
Availability | VoID file availability check for EventKG took 0.0006518363952636719s
Completeness | Calculation of interlinking completeness for EventKG took 0.2513546943664551s
Reputation | Calculation of the PageRank for EventKG took 0.02143263816833496s
Interlinking | Calculation of Degree of Connection for EventKG took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for EventKG took 0.0008144378662109375s
Interlinking | Calculation of Clustering coefficient for EventKG took 9.918212890625e-05s
Believability | Calculation of trust value for EventKG took 7.62939453125e-06s
INFO | --- Analysis for eventkg took 4.385318279266357s
Availability | SPARQL endpoint availability check for Eventseer took 4.315376281738281e-05s
Availability | VoID file availability check for Eventseer took 0.00031185150146484375s
Completeness | Calculation of interlinking completeness for Eventseer took 0.2613687515258789s
Reputation | Calculation of the PageRank for Eventseer took 0.020464420318603516s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.8160552978515625e-05s
Believability | Calculation of trust value for Eventseer took 7.62939453125e-06s
INFO | --- Analysis for eventseer took 2.8174610137939453s
Availability | SPARQL endpoint availability check for Face Link took 4.0531158447265625e-05s
Availability | VoID file availability check for Face Link took 0.0004100799560546875s
Completeness | Calculation of interlinking completeness for Face Link took 0.2658851146697998s
Reputation | Calculation of the PageRank for Face Link took 0.02042102813720703s
Interlinking | Calculation of Degree of Connection for Face Link took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Face Link took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.743171691894531e-05s
Believability | Calculation of trust value for Face Link took 6.198883056640625e-06s
INFO | --- Analysis for Face_Link took 2.815114974975586s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 4.029273986816406e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.24440431594848633s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.020586252212524414s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.0517578125e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 6.9141387939453125e-06s
INFO | --- Analysis for facebook-lids took 2.7249205112457275s
Availability | SPARQL endpoint availability check for Fact Forge took 4.887580871582031e-05s
Availability | VoID file availability check for Fact Forge took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.24676775932312012s
Reputation | Calculation of the PageRank for Fact Forge took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for Fact Forge took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Fact Forge took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 2.86102294921875e-05s
Believability | Calculation of trust value for Fact Forge took 7.867813110351562e-06s
INFO | --- Analysis for fact-forge took 2.8029236793518066s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.291534423828125e-05s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.2592175006866455s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0006783008575439453s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 3.814697265625e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for FADN_(2019) took 2.8311378955841064s
Availability | SPARQL endpoint availability check for FAMEData took 4.1961669921875e-05s
Availability | VoID file availability check for FAMEData took 0.0003802776336669922s
Completeness | Calculation of interlinking completeness for FAMEData took 0.27953243255615234s
Reputation | Calculation of the PageRank for FAMEData took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for FAMEData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FAMEData took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.123283386230469e-05s
Believability | Calculation of trust value for FAMEData took 7.3909759521484375e-06s
INFO | --- Analysis for famedata took 2.7977092266082764s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 5.245208740234375e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.2496960163116455s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.020473718643188477s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.226799011230469e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 7.3909759521484375e-06s
INFO | --- Analysis for fao-geopolitical-ontology took 2.826470375061035s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 3.9577484130859375e-05s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.24603867530822754s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.000675201416015625s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.799003601074219e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for fao-linked-data took 2.799112319946289s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 5.054473876953125e-05s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.25092124938964844s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0006792545318603516s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 2.765655517578125e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 1.2159347534179688e-05s
INFO | --- Analysis for FAO_species took 2.7856192588806152s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 4.601478576660156e-05s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.25014233589172363s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for ChEMBL-RDF (@ Uppsala University) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChEMBL-RDF (@ Uppsala University) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.1961669921875e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 1.239776611328125e-05s
INFO | --- Analysis for farmbio-chembl took 2.8401730060577393s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 3.981590270996094e-05s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.26480865478515625s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 7.62939453125e-06s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.7905635833740234s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 4.029273986816406e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.25995302200317383s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.02035832405090332s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.239776611328125e-05s
INFO | --- Analysis for farolapp-dataset took 2.883533477783203s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.0531158447265625e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.24710893630981445s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.020604372024536133s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 2.9325485229492188e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 6.67572021484375e-06s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.7581756114959717s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.1961669921875e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.2510383129119873s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.0204770565032959s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.0040740966796875e-05s
Believability | Calculation of trust value for I4.0-Onto took 7.62939453125e-06s
INFO | --- Analysis for fatimazahra took 2.7661898136138916s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.24493956565856934s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007660388946533203s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.1948089599609375e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 6.67572021484375e-06s
INFO | --- Analysis for federal-economic-rdf took 2.783174753189087s
Availability | SPARQL endpoint availability check for Feed Wrapper took 4.100799560546875e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.24787306785583496s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 2.956390380859375e-05s
Believability | Calculation of trust value for Feed Wrapper took 6.67572021484375e-06s
INFO | --- Analysis for feedwrapper-lids took 2.834472894668579s
Availability | SPARQL endpoint availability check for FHIR STU3 took 4.100799560546875e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.24120879173278809s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.020473241806030273s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.337860107421875e-05s
Believability | Calculation of trust value for FHIR STU3 took 7.3909759521484375e-06s
INFO | --- Analysis for FHIR_STU3 took 2.796776294708252s
Availability | SPARQL endpoint availability check for FiESTA took 4.8160552978515625e-05s
Availability | VoID file availability check for FiESTA took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for FiESTA took 0.2522585391998291s
Reputation | Calculation of the PageRank for FiESTA took 0.021432161331176758s
Interlinking | Calculation of Degree of Connection for FiESTA took 4.0531158447265625e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for FiESTA took 3.981590270996094e-05s
Believability | Calculation of trust value for FiESTA took 1.0251998901367188e-05s
INFO | --- Analysis for fiesta took 2.8560075759887695s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.2438507080078125e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0003094673156738281s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.25627684593200684s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.02073812484741211s
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.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.147125244140625e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 7.152557373046875e-06s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.8538103103637695s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 4.076957702636719e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.2531399726867676s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007872581481933594s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.534027099609375e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 7.3909759521484375e-06s
INFO | --- Analysis for finnish-municipalities took 2.9304428100585938s
Availability | SPARQL endpoint availability check for firmao took 4.100799560546875e-05s
Availability | VoID file availability check for firmao took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for firmao took 0.25614428520202637s
Reputation | Calculation of the PageRank for firmao took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for firmao took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for firmao took 3.1948089599609375e-05s
Believability | Calculation of trust value for firmao took 1.239776611328125e-05s
INFO | --- Analysis for firmao took 2.8930091857910156s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.2592945098876953s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.8704440593719482s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 4.1484832763671875e-05s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.2549879550933838s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.020229339599609375s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset @PSNC took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 2.8848648071289062e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 7.62939453125e-06s
INFO | --- Analysis for Fishery_Stock_Dataset took 2.8795857429504395s
Availability | SPARQL endpoint availability check for Fishes of Texas took 5.7697296142578125e-05s
Availability | VoID file availability check for Fishes of Texas took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.25963830947875977s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02068614959716797s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.678436279296875e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.0013580322265625e-05s
INFO | --- Analysis for fishes-of-texas took 2.8737592697143555s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.1484832763671875e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.26225972175598145s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020514965057373047s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.274482727050781e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.2874603271484375e-05s
INFO | --- Analysis for flickr-wrappr took 2.8745272159576416s
Availability | SPARQL endpoint availability check for flickr.person took 7.2479248046875e-05s
Availability | VoID file availability check for flickr.person took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for flickr.person took 0.250241756439209s
Reputation | Calculation of the PageRank for flickr.person took 0.020145893096923828s
Interlinking | Calculation of Degree of Connection for flickr.person took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for flickr.person took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.0279159545898438e-05s
Believability | Calculation of trust value for flickr.person took 7.152557373046875e-06s
INFO | --- Analysis for flickr_person took 2.8040130138397217s
Availability | SPARQL endpoint availability check for flickr.videoobject took 4.029273986816406e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.24079132080078125s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.020437240600585938s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.0517578125e-05s
Believability | Calculation of trust value for flickr.videoobject took 7.152557373046875e-06s
INFO | --- Analysis for flickr_videoobject took 2.767789363861084s
Availability | SPARQL endpoint availability check for Future land use simulation model took 3.910064697265625e-05s
Availability | VoID file availability check for Future land use simulation model took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.24828267097473145s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.02215743064880371s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0010907649993896484s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.814697265625e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.0967254638671875e-05s
INFO | --- Analysis for FLUS took 2.791024684906006s
Availability | SPARQL endpoint availability check for Fly-TED took 4.124641418457031e-05s
Availability | VoID file availability check for Fly-TED took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.2600100040435791s
Reputation | Calculation of the PageRank for Fly-TED took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for Fly-TED took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fly-TED took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 2.86102294921875e-05s
Believability | Calculation of trust value for Fly-TED took 6.4373016357421875e-06s
INFO | --- Analysis for fly-ted took 2.7926254272460938s
Availability | SPARQL endpoint availability check for FlyAtlas took 3.981590270996094e-05s
Availability | VoID file availability check for FlyAtlas took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.24997234344482422s
Reputation | Calculation of the PageRank for FlyAtlas took 0.0200955867767334s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 2.8371810913085938e-05s
Believability | Calculation of trust value for FlyAtlas took 1.1444091796875e-05s
INFO | --- Analysis for flyatlas took 2.802326202392578s
Availability | SPARQL endpoint availability check for Flybase took 6.699562072753906e-05s
Availability | VoID file availability check for Flybase took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Flybase took 0.23845958709716797s
Reputation | Calculation of the PageRank for Flybase took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Flybase took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Flybase took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.361701965332031e-05s
Believability | Calculation of trust value for Flybase took 1.1205673217773438e-05s
INFO | --- Analysis for flybase took 2.78224515914917s
Availability | SPARQL endpoint availability check for Flyted took 4.124641418457031e-05s
Availability | VoID file availability check for Flyted took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Flyted took 0.26630687713623047s
Reputation | Calculation of the PageRank for Flyted took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Flyted took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Flyted took 0.0006814002990722656s
Interlinking | Calculation of Clustering coefficient for Flyted took 2.8848648071289062e-05s
Believability | Calculation of trust value for Flyted took 1.1205673217773438e-05s
INFO | --- Analysis for flyted took 2.851189613342285s
Availability | SPARQL endpoint availability check for Foodista took 4.00543212890625e-05s
Availability | VoID file availability check for Foodista took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Foodista took 0.2732400894165039s
Reputation | Calculation of the PageRank for Foodista took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.9087066650390625e-05s
Believability | Calculation of trust value for Foodista took 6.198883056640625e-06s
INFO | --- Analysis for foodista took 2.9045138359069824s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 4.00543212890625e-05s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.2789769172668457s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 6.914138793945312e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 6.67572021484375e-06s
INFO | --- Analysis for foodpedia took 2.8743414878845215s
Availability | SPARQL endpoint availability check for FORGE Course information took 6.580352783203125e-05s
Availability | VoID file availability check for FORGE Course information took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.2529017925262451s
Reputation | Calculation of the PageRank for FORGE Course information took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 2.86102294921875e-05s
Believability | Calculation of trust value for FORGE Course information took 1.0967254638671875e-05s
INFO | --- Analysis for forge-course-information took 2.8121745586395264s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.076957702636719e-05s
Availability | VoID file availability check for FrameBase schema took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.2767045497894287s
Reputation | Calculation of the PageRank for FrameBase schema took 0.02016592025756836s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.3392181396484375e-05s
Believability | Calculation of trust value for FrameBase schema took 6.4373016357421875e-06s
INFO | --- Analysis for framebase-schema took 2.9083375930786133s
Availability | SPARQL endpoint availability check for FrameNet took 4.0531158447265625e-05s
Availability | VoID file availability check for FrameNet took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for FrameNet took 0.24808835983276367s
Reputation | Calculation of the PageRank for FrameNet took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for FrameNet took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for FrameNet took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for FrameNet took 2.9087066650390625e-05s
Believability | Calculation of trust value for FrameNet took 8.106231689453125e-06s
INFO | --- Analysis for framenet took 2.8324391841888428s
Availability | SPARQL endpoint availability check for Framester took 8.106231689453125e-05s
Availability | VoID file availability check for Framester took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Framester took 0.2435131072998047s
Reputation | Calculation of the PageRank for Framester took 0.020651817321777344s
Interlinking | Calculation of Degree of Connection for Framester took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Framester took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Framester took 7.367134094238281e-05s
Believability | Calculation of trust value for Framester took 6.9141387939453125e-06s
INFO | --- Analysis for framester took 2.8412508964538574s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 4.220008850097656e-05s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.2662081718444824s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.702278137207031e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 6.9141387939453125e-06s
INFO | --- Analysis for frb-linked-data took 2.848304033279419s
Availability | SPARQL endpoint availability check for Freebase took 4.1484832763671875e-05s
Availability | VoID file availability check for Freebase took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for Freebase took 0.26096415519714355s
Reputation | Calculation of the PageRank for Freebase took 0.02047586441040039s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00026416778564453125s
Believability | Calculation of trust value for Freebase took 6.9141387939453125e-06s
INFO | --- Analysis for freebase took 2.756340265274048s
Availability | SPARQL endpoint availability check for Freeyork took 4.2438507080078125e-05s
Availability | VoID file availability check for Freeyork took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Freeyork took 0.26218152046203613s
Reputation | Calculation of the PageRank for Freeyork took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Freeyork took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Freeyork took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010347366333007812s
Believability | Calculation of trust value for Freeyork took 7.62939453125e-06s
INFO | --- Analysis for freeyork-org took 2.8162505626678467s
Availability | SPARQL endpoint availability check for French School Program took 5.888938903808594e-05s
Availability | VoID file availability check for French School Program took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for French School Program took 0.24506521224975586s
Reputation | Calculation of the PageRank for French School Program took 0.021055936813354492s
Interlinking | Calculation of Degree of Connection for French School Program took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for French School Program took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.7670135498046875e-05s
Believability | Calculation of trust value for French School Program took 8.344650268554688e-06s
INFO | --- Analysis for french-school-program took 2.8446414470672607s
Availability | SPARQL endpoint availability check for French School System took 4.0531158447265625e-05s
Availability | VoID file availability check for French School System took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for French School System took 0.2877013683319092s
Reputation | Calculation of the PageRank for French School System took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for French School System took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for French School System took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for French School System took 3.123283386230469e-05s
Believability | Calculation of trust value for French School System took 7.867813110351562e-06s
INFO | --- Analysis for french-school-system took 2.892664670944214s
Availability | SPARQL endpoint availability check for French TimeBank took 4.2438507080078125e-05s
Availability | VoID file availability check for French TimeBank took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.26570773124694824s
Reputation | Calculation of the PageRank for French TimeBank took 0.020629167556762695s
Interlinking | Calculation of Degree of Connection for French TimeBank took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.4332275390625e-05s
Believability | Calculation of trust value for French TimeBank took 6.67572021484375e-06s
INFO | --- Analysis for french-timebank took 2.7970547676086426s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 5.2928924560546875e-05s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.00030517578125s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.26212143898010254s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.367134094238281e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-cordis took 2.8033571243286133s
Availability | SPARQL endpoint availability check for DailyMed took 7.009506225585938e-05s
Availability | VoID file availability check for DailyMed took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for DailyMed took 0.2346053123474121s
Reputation | Calculation of the PageRank for DailyMed took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for DailyMed took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DailyMed took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.274482727050781e-05s
Believability | Calculation of trust value for DailyMed took 5.9604644775390625e-06s
INFO | --- Analysis for fu-berlin-dailymed took 2.795738458633423s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 4.0531158447265625e-05s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.26560521125793457s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0008523464202880859s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 9.417533874511719e-05s
Believability | Calculation of trust value for DBLP Bibliography Database in RDF (FU Berlin) took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-dblp took 2.850008010864258s
Availability | SPARQL endpoint availability check for Diseasome took 4.124641418457031e-05s
Availability | VoID file availability check for Diseasome took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Diseasome took 0.24360966682434082s
Reputation | Calculation of the PageRank for Diseasome took 0.020320415496826172s
Interlinking | Calculation of Degree of Connection for Diseasome took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Diseasome took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010514259338378906s
Believability | Calculation of trust value for Diseasome took 3.409385681152344e-05s
INFO | --- Analysis for fu-berlin-diseasome took 2.8369038105010986s
Availability | SPARQL endpoint availability check for DrugBank took 4.172325134277344e-05s
Availability | VoID file availability check for DrugBank took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2664785385131836s
Reputation | Calculation of the PageRank for DrugBank took 0.022271394729614258s
Interlinking | Calculation of Degree of Connection for DrugBank took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DrugBank took 0.00086212158203125s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00012755393981933594s
Believability | Calculation of trust value for DrugBank took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-drugbank took 2.842341661453247s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 4.4345855712890625e-05s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.2522134780883789s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.02043437957763672s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.9087066650390625e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 2.850282907485962s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 4.029273986816406e-05s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.24723267555236816s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.390975952148438e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 7.152557373046875e-06s
INFO | --- Analysis for fu-berlin-euraxess took 2.7708539962768555s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 4.00543212890625e-05s
Availability | VoID file availability check for European Employment Services (EURES) took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.2662196159362793s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for European Employment Services (EURES) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Employment Services (EURES) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 0.00010347366333007812s
Believability | Calculation of trust value for European Employment Services (EURES) took 7.3909759521484375e-06s
INFO | --- Analysis for fu-berlin-eures took 2.7905478477478027s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 0.00010514259338378906s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.2608354091644287s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.020244836807250977s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 0.00010013580322265625s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 3.8623809814453125e-05s
INFO | --- Analysis for fu-berlin-eurostat took 2.7966814041137695s
Availability | SPARQL endpoint availability check for MediCare took 4.029273986816406e-05s
Availability | VoID file availability check for MediCare took 0.0002830028533935547s
Completeness | Calculation of interlinking completeness for MediCare took 0.256638765335083s
Reputation | Calculation of the PageRank for MediCare took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for MediCare took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MediCare took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for MediCare took 4.076957702636719e-05s
Believability | Calculation of trust value for MediCare took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-medicare took 2.7886769771575928s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 4.100799560546875e-05s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.2802543640136719s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg in RDF (FU Berlin) took 7.104873657226562e-05s
Believability | Calculation of trust value for Project Gutenberg in RDF (FU Berlin) took 7.62939453125e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 2.788105010986328s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 4.57763671875e-05s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.2757396697998047s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 8.7738037109375e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-sider took 2.813880205154419s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 3.981590270996094e-05s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.2672123908996582s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020612239837646484s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.295608520507812e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-stitch took 2.766472339630127s
Availability | SPARQL endpoint availability check for fvdb took 4.7206878662109375e-05s
Availability | VoID file availability check for fvdb took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for fvdb took 0.2729156017303467s
Reputation | Calculation of the PageRank for fvdb took 0.020615339279174805s
Interlinking | Calculation of Degree of Connection for fvdb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for fvdb took 2.86102294921875e-05s
Believability | Calculation of trust value for fvdb took 3.2901763916015625e-05s
INFO | --- Analysis for fv took 2.8510396480560303s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 5.14984130859375e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.2666041851043701s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0006818771362304688s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 2.9087066650390625e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 9.298324584960938e-06s
INFO | --- Analysis for GACS took 2.869311809539795s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 4.172325134277344e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.2794528007507324s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020114898681640625s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0006787776947021484s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 2.8848648071289062e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 6.9141387939453125e-06s
INFO | --- Analysis for galen_from_co-odeorg took 2.832183837890625s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 4.2438507080078125e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.26403188705444336s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.021102428436279297s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0008034706115722656s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.410743713378906e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 7.3909759521484375e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 2.8791630268096924s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 4.00543212890625e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.27706074714660645s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020667076110839844s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 0.00011086463928222656s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for garnicaplywood took 2.8457343578338623s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.482269287109375e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.2549326419830322s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.822845458984375e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 7.62939453125e-06s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 2.8233842849731445s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0003707408905029297s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.26658105850219727s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 8.821487426757812e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for gemet took 2.837695360183716s
Availability | SPARQL endpoint availability check for gemet-annotated took 3.9577484130859375e-05s
Availability | VoID file availability check for gemet-annotated took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.26334166526794434s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.5762786865234375e-05s
Believability | Calculation of trust value for gemet-annotated took 6.9141387939453125e-06s
INFO | --- Analysis for gemet-annotated took 2.9067676067352295s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.2538313865661621s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.02057504653930664s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 3.886222839355469e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 7.152557373046875e-06s
INFO | --- Analysis for gene-expression-atlas-rdf took 2.7932546138763428s
Availability | SPARQL endpoint availability check for Super Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Super Ontology took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.28895044326782227s
Reputation | Calculation of the PageRank for Super Ontology took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Super Ontology took 7.152557373046875e-06s
INFO | --- Analysis for Generalized_Super_Ontology took 2.7965264320373535s
Availability | SPARQL endpoint availability check for geo.place took 7.200241088867188e-05s
Availability | VoID file availability check for geo.place took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for geo.place took 0.24334716796875s
Reputation | Calculation of the PageRank for geo.place took 0.020496368408203125s
Interlinking | Calculation of Degree of Connection for geo.place took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for geo.place took 3.075599670410156e-05s
Believability | Calculation of trust value for geo.place took 7.3909759521484375e-06s
INFO | --- Analysis for geo_place took 2.865640878677368s
Availability | SPARQL endpoint availability check for Geographic detector model took 7.271766662597656e-05s
Availability | VoID file availability check for Geographic detector model took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.25620150566101074s
Reputation | Calculation of the PageRank for Geographic detector model took 0.02149176597595215s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0010883808135986328s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.790855407714844e-05s
Believability | Calculation of trust value for Geographic detector model took 7.62939453125e-06s
INFO | --- Analysis for GeoDetector took 2.832279920578003s
Availability | SPARQL endpoint availability check for geodomainwn took 5.459785461425781e-05s
Availability | VoID file availability check for geodomainwn took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.2647678852081299s
Reputation | Calculation of the PageRank for geodomainwn took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for geodomainwn took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for geodomainwn took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 5.030632019042969e-05s
Believability | Calculation of trust value for geodomainwn took 7.3909759521484375e-06s
INFO | --- Analysis for geodomainwn took 2.826467275619507s
Availability | SPARQL endpoint availability check for GeoEcuador took 4.076957702636719e-05s
Availability | VoID file availability check for GeoEcuador took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.2540092468261719s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.723403930664062e-05s
Believability | Calculation of trust value for GeoEcuador took 8.106231689453125e-06s
INFO | --- Analysis for geoecuador took 2.7989413738250732s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2367920875549316s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.32990193367004395s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.0206148624420166s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.842613220214844e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 8.106231689453125e-06s
INFO | --- Analysis for geographic-names-information-system-gnis took 7.545490264892578s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 4.124641418457031e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.2526068687438965s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020964860916137695s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 7.152557373046875e-06s
INFO | --- Analysis for geographic-openuplabs took 2.8392093181610107s
Availability | SPARQL endpoint availability check for GeoLinkedData took 4.220008850097656e-05s
Availability | VoID file availability check for GeoLinkedData took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.26195383071899414s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.021018028259277344s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0008299350738525391s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 9.560585021972656e-05s
Believability | Calculation of trust value for GeoLinkedData took 7.62939453125e-06s
INFO | --- Analysis for geolinkeddata took 2.858771324157715s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 4.076957702636719e-05s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.26746129989624023s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.021352767944335938s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.535385131835938e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 2.9025471210479736s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 4.172325134277344e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.28041601181030273s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02068471908569336s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 3.337860107421875e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0004734992980957031s
Believability | Calculation of trust value for GeoNames Semantic Web took 7.3909759521484375e-06s
INFO | --- Analysis for geonames-semantic-web took 2.8167977333068848s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.076957702636719e-05s
Availability | VoID file availability check for Geospatial World  took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.25404977798461914s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00010371208190917969s
Believability | Calculation of trust value for Geospatial World  took 7.62939453125e-06s
INFO | --- Analysis for geospatialworld-net took 2.8119490146636963s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 3.981590270996094e-05s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.26656174659729004s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.02175426483154297s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0010902881622314453s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00015592575073242188s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 6.4373016357421875e-06s
INFO | --- Analysis for geospecies took 2.7951362133026123s
Availability | SPARQL endpoint availability check for GeoWordNet took 4.0531158447265625e-05s
Availability | VoID file availability check for GeoWordNet took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.2587873935699463s
Reputation | Calculation of the PageRank for GeoWordNet took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 5.173683166503906e-05s
Believability | Calculation of trust value for GeoWordNet took 6.9141387939453125e-06s
INFO | --- Analysis for geowordnet took 2.808320999145508s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for German labor law thesaurus took 0.00034165382385253906s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.267580509185791s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02085423469543457s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007560253143310547s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 8.416175842285156e-05s
Believability | Calculation of trust value for German labor law thesaurus took 7.152557373046875e-06s
INFO | --- Analysis for german-labor-law-thesaurus took 2.863645553588867s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.24844741821289062s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.000774383544921875s
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 6.67572021484375e-06s
INFO | --- Analysis for germlex took 2.8730835914611816s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.319450378417969e-05s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.2454242706298828s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.02052760124206543s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.001417398452758789s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 9.465217590332031e-05s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 7.3909759521484375e-06s
INFO | --- Analysis for gesis-thesoz took 2.8072404861450195s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.8296546936035156s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.00029206275939941406s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.2510251998901367s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.021500349044799805s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.867813110351562e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 6.198883056640625e-06s
INFO | --- Analysis for getty-aat took 8.661582708358765s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.2683680057525635s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.24599432945251465s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 5.459785461425781e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 7.3909759521484375e-06s
INFO | --- Analysis for getty-tgn took 5.870878219604492s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 4.172325134277344e-05s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.26110029220581055s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.020785808563232422s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 3.1948089599609375e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 7.867813110351562e-06s
INFO | --- Analysis for gipuzkoademografia took 2.878422260284424s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.124641418457031e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0010898113250732422s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.26422977447509766s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.147125244140625e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 2.5272369384765625e-05s
INFO | --- Analysis for glastonbury-2011 took 2.8690969944000244s
Availability | SPARQL endpoint availability check for Global Change Information System took 3.933906555175781e-05s
Availability | VoID file availability check for Global Change Information System took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.27337074279785156s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020855188369750977s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 3.24249267578125e-05s
Believability | Calculation of trust value for Global Change Information System took 7.867813110351562e-06s
INFO | --- Analysis for global-change-information-system took 2.8312926292419434s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 5.459785461425781e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.258037805557251s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 5.0067901611328125e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.3828277587890625e-05s
INFO | --- Analysis for global-hunger-index-2011 took 2.852055549621582s
Availability | SPARQL endpoint availability check for Glottolog took 4.172325134277344e-05s
Availability | VoID file availability check for Glottolog took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Glottolog took 0.2634315490722656s
Reputation | Calculation of the PageRank for Glottolog took 0.020728588104248047s
Interlinking | Calculation of Degree of Connection for Glottolog took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Glottolog took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.935264587402344e-05s
Believability | Calculation of trust value for Glottolog took 7.867813110351562e-06s
INFO | --- Analysis for glottolog took 2.8877005577087402s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 5.507469177246094e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.2644236087799072s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.02056097984313965s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010418891906738281s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 7.867813110351562e-06s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 2.7613942623138428s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 4.1961669921875e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.27493858337402344s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.020478248596191406s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 3.0994415283203125e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 6.67572021484375e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 2.893311023712158s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 4.291534423828125e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.2595818042755127s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 3.1948089599609375e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 6.67572021484375e-06s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 2.9181418418884277s
Availability | SPARQL endpoint availability check for 1121 took 4.076957702636719e-05s
Availability | VoID file availability check for 1121 took 0.00029921531677246094s
Completeness | Calculation of interlinking completeness for 1121 took 0.23976469039916992s
Reputation | Calculation of the PageRank for 1121 took 0.02062225341796875s
Interlinking | Calculation of Degree of Connection for 1121 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for 1121 took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for 1121 took 3.0517578125e-05s
Believability | Calculation of trust value for 1121 took 7.152557373046875e-06s
INFO | --- Analysis for God_ took 2.7905166149139404s
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.00024008750915527344s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.2445695400238037s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.030632019042969e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 6.198883056640625e-06s
INFO | --- Analysis for gold took 2.78716778755188s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 4.9591064453125e-05s
Availability | VoID file availability check for GoogleArt wrapper took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.26765966415405273s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.020647764205932617s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.081031799316406e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 7.152557373046875e-06s
INFO | --- Analysis for googleart-wrapper took 2.7983715534210205s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 4.00543212890625e-05s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.2565157413482666s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020723819732666016s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.6716461181640625e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 8.106231689453125e-06s
INFO | --- Analysis for govagribus-denmark took 2.839759349822998s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 4.100799560546875e-05s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.2633967399597168s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020580530166625977s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 7.987022399902344e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for government-web-integration-for-linked-data took 2.898409843444824s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 3.9577484130859375e-05s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.2472834587097168s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.020273923873901367s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.869171142578125e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 6.4373016357421875e-06s
INFO | --- Analysis for govtrack took 2.7844536304473877s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 4.124641418457031e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.27852559089660645s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.6743621826171875e-05s
Believability | Calculation of trust value for greek-administrative-geography took 6.9141387939453125e-06s
INFO | --- Analysis for greek-administrative-geography took 2.9220616817474365s
Availability | SPARQL endpoint availability check for Greek Wordnet took 4.00543212890625e-05s
Availability | VoID file availability check for Greek Wordnet took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.26258349418640137s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.790855407714844e-05s
Believability | Calculation of trust value for Greek Wordnet took 6.9141387939453125e-06s
INFO | --- Analysis for greek-wordnet took 2.8309414386749268s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 3.981590270996094e-05s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.2640974521636963s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.020719051361083984s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.9550323486328125e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.1920928955078125e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 6.198883056640625e-06s
INFO | --- Analysis for greek_prisons_releases took 2.779672384262085s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 1.788830041885376s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.2698636054992676s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.486343383789062e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.9141387939453125e-06s
INFO | --- Analysis for greekchildrensartmuseum took 5.032011985778809s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 6.103515625e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.23814916610717773s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02013087272644043s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 0.00010275840759277344s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 7.3909759521484375e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 2.840902090072632s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 4.458427429199219e-05s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.25310635566711426s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.410743713378906e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 8.344650268554688e-06s
INFO | --- Analysis for grrp took 2.9147119522094727s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 4.076957702636719e-05s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.26140522956848145s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.02031993865966797s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.604194641113281e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 1.1920928955078125e-05s
INFO | --- Analysis for grrt took 2.863759756088257s
Availability | SPARQL endpoint availability check for Geological Timescale took 4.0531158447265625e-05s
Availability | VoID file availability check for Geological Timescale took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.25595784187316895s
Reputation | Calculation of the PageRank for Geological Timescale took 0.02034282684326172s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.723403930664062e-05s
Believability | Calculation of trust value for Geological Timescale took 7.152557373046875e-06s
INFO | --- Analysis for GTS took 2.8672549724578857s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.2554781436920166s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.020673274993896484s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 6.67572021484375e-06s
INFO | --- Analysis for GTS-ont took 2.810561418533325s
Availability | SPARQL endpoint availability check for GUTSTOK  took 4.267692565917969e-05s
Availability | VoID file availability check for GUTSTOK  took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.23700857162475586s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02005791664123535s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.8848648071289062e-05s
Believability | Calculation of trust value for GUTSTOK  took 7.3909759521484375e-06s
INFO | --- Analysis for Guillaume_Forget took 2.8771941661834717s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.267692565917969e-05s
Availability | VoID file availability check for Project Gutenberg took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.2664616107940674s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.0269927978515625s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0011200904846191406s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 8.511543273925781e-05s
Believability | Calculation of trust value for Project Gutenberg took 7.152557373046875e-06s
INFO | --- Analysis for gutenberg took 3.4563143253326416s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 4.100799560546875e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.28537464141845703s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.020260095596313477s
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.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.361701965332031e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 6.9141387939453125e-06s
INFO | --- Analysis for gwa-ili took 2.8545706272125244s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.172325134277344e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.2613210678100586s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02026677131652832s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 3.0040740966796875e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 6.9141387939453125e-06s
INFO | --- Analysis for GWR took 2.809026002883911s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.553794860839844e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.29068994522094727s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020482540130615234s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.4332275390625e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 6.9141387939453125e-06s
INFO | --- Analysis for HASM took 2.9017651081085205s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 4.00543212890625e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.00029730796813964844s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.2530639171600342s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.021214008331298828s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0009109973907470703s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 3.552436828613281e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for hcls-knowledge-base took 2.917950391769409s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for HealthCare Ontology took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.24149680137634277s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020916461944580078s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.7670135498046875e-05s
Believability | Calculation of trust value for HealthCare Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for HealthCare_Ontology took 2.7659997940063477s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 4.076957702636719e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.25119638442993164s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 5.8650970458984375e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 7.3909759521484375e-06s
INFO | --- Analysis for heartfailure took 2.821767568588257s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 22.010253429412842s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.24730563163757324s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.02061295509338379s
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.2159347534179688e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 4.124641418457031e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 6.9141387939453125e-06s
INFO | --- Analysis for hebis-bibliographic-resources took 54.92465925216675s
Availability | SPARQL endpoint availability check for Hedatuz took 0.3201639652252197s
Availability | VoID file availability check for Hedatuz took 0.0003619194030761719s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.26198339462280273s
Reputation | Calculation of the PageRank for Hedatuz took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.267692565917969e-05s
Believability | Calculation of trust value for Hedatuz took 7.62939453125e-06s
INFO | --- Analysis for hedatuz took 3.3474016189575195s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 4.076957702636719e-05s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.26404881477355957s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012612342834472656s
Believability | Calculation of trust value for Hellenic Fire Brigade took 7.62939453125e-06s
INFO | --- Analysis for hellenic-fire-brigade took 2.848039150238037s
Availability | SPARQL endpoint availability check for Hellenic Police took 4.3392181396484375e-05s
Availability | VoID file availability check for Hellenic Police took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.2520158290863037s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02071094512939453s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0006780624389648438s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012826919555664062s
Believability | Calculation of trust value for Hellenic Police took 8.106231689453125e-06s
INFO | --- Analysis for hellenic-police took 2.938231945037842s
Availability | SPARQL endpoint availability check for Hermos took 5.14984130859375e-05s
Availability | VoID file availability check for Hermos took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Hermos took 0.26543140411376953s
Reputation | Calculation of the PageRank for Hermos took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Hermos took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Hermos took 0.0008161067962646484s
Interlinking | Calculation of Clustering coefficient for Hermos took 3.457069396972656e-05s
Believability | Calculation of trust value for Hermos took 9.5367431640625e-06s
INFO | --- Analysis for Hermos took 2.8498685359954834s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 4.0531158447265625e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.2474803924560547s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020369529724121094s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 3.0040740966796875e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 7.867813110351562e-06s
INFO | --- Analysis for Himanshu_Mahawar took 2.843114137649536s
Availability | SPARQL endpoint availability check for HITO took 7.390975952148438e-05s
Availability | VoID file availability check for HITO took 0.00032210350036621094s
Completeness | Calculation of interlinking completeness for HITO took 0.23930597305297852s
Reputation | Calculation of the PageRank for HITO took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for HITO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HITO took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for HITO took 7.05718994140625e-05s
Believability | Calculation of trust value for HITO took 8.344650268554688e-06s
INFO | --- Analysis for hito took 2.831509828567505s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 4.124641418457031e-05s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.27875208854675293s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 3.266334533691406e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 8.106231689453125e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 2.912933826446533s
Availability | SPARQL endpoint availability check for Homologene took 4.220008850097656e-05s
Availability | VoID file availability check for Homologene took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Homologene took 0.25435590744018555s
Reputation | Calculation of the PageRank for Homologene took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Homologene took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Homologene took 3.337860107421875e-05s
Believability | Calculation of trust value for Homologene took 7.62939453125e-06s
INFO | --- Analysis for homologene took 2.820415496826172s
Availability | SPARQL endpoint availability check for gseg took 4.315376281738281e-05s
Availability | VoID file availability check for gseg took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for gseg took 0.29062819480895996s
Reputation | Calculation of the PageRank for gseg took 0.021548986434936523s
Interlinking | Calculation of Degree of Connection for gseg took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for gseg took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for gseg took 3.3855438232421875e-05s
Believability | Calculation of trust value for gseg took 7.867813110351562e-06s
INFO | --- Analysis for hongse took 2.8826189041137695s
Availability | SPARQL endpoint availability check for Noticias Universia took 4.029273986816406e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.27858424186706543s
Reputation | Calculation of the PageRank for Noticias Universia took 0.02082657814025879s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 3.457069396972656e-05s
Believability | Calculation of trust value for Noticias Universia took 7.867813110351562e-06s
INFO | --- Analysis for http-data-noticias-universia-net took 2.8312437534332275s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 4.076957702636719e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.24274969100952148s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02005624771118164s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.9802322387695312e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.3909759521484375e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 2.786396026611328s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.292290210723877s
Availability | VoID file availability check for COURAGE Dataset took 0.00035119056701660156s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.255993127822876s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for COURAGE Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for http:cultural-opposition.eu took 4.948572874069214s
Availability | SPARQL endpoint availability check for RoadTrb took 4.124641418457031e-05s
Availability | VoID file availability check for RoadTrb took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.27536535263061523s
Reputation | Calculation of the PageRank for RoadTrb took 0.02028679847717285s
Interlinking | Calculation of Degree of Connection for RoadTrb took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.956390380859375e-05s
Believability | Calculation of trust value for RoadTrb took 6.198883056640625e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 2.8667945861816406s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.100799560546875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2664179801940918s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.020546436309814453s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 7.152557373046875e-06s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 2.8371922969818115s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 4.076957702636719e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.26715683937072754s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02045464515686035s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.9325485229492188e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 6.67572021484375e-06s
INFO | --- Analysis for http:pakistan.com took 2.8337910175323486s
Availability | SPARQL endpoint availability check for CEDICT took 4.363059997558594e-05s
Availability | VoID file availability check for CEDICT took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for CEDICT took 0.2437739372253418s
Reputation | Calculation of the PageRank for CEDICT took 0.020463943481445312s
Interlinking | Calculation of Degree of Connection for CEDICT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CEDICT took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.0994415283203125e-05s
Believability | Calculation of trust value for CEDICT took 7.152557373046875e-06s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 2.8492555618286133s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 5.245208740234375e-05s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2786273956298828s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020618438720703125s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.866455078125e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.3909759521484375e-06s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 2.9162049293518066s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 4.076957702636719e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.2657303810119629s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020212650299072266s
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.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 7.3909759521484375e-06s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.867837429046631s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 4.5299530029296875e-05s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0002834796905517578s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.2597646713256836s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.956390380859375e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 7.867813110351562e-06s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.8326852321624756s
Availability | SPARQL endpoint availability check for Soccer Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for Soccer Dataset took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.24921607971191406s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.9325485229492188e-05s
Believability | Calculation of trust value for Soccer Dataset took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.msm.com took 2.8621885776519775s
Availability | SPARQL endpoint availability check for Game Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Game Ontology took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.27957653999328613s
Reputation | Calculation of the PageRank for Game Ontology took 0.021509647369384766s
Interlinking | Calculation of Degree of Connection for Game Ontology took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007534027099609375s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Game Ontology took 8.821487426757812e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 2.8996331691741943s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 4.029273986816406e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.2488853931427002s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0007119178771972656s
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 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 2.8194117546081543s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 4.100799560546875e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.2762117385864258s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.02048945426940918s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.123283386230469e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 6.9141387939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.8306782245635986s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.076957702636719e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.2664804458618164s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006756782531738281s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.62396240234375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 2.855217456817627s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 5.173683166503906e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26202893257141113s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020496606826782227s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0994415283203125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.867813110351562e-06s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.8279261589050293s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.0531158447265625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.25865626335144043s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02062845230102539s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.9802322387695312e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.049041748046875e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 2.885650634765625s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 4.124641418457031e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26438426971435547s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.0517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.62939453125e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 2.8434336185455322s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 3.933906555175781e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0003552436828613281s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.26279544830322266s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 3.170967102050781e-05s
Believability | Calculation of trust value for Indian Biodiversity took 7.3909759521484375e-06s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.886173725128174s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 4.2438507080078125e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.000583648681640625s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.2509145736694336s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.1948089599609375e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 7.62939453125e-06s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 2.838806629180908s
Availability | SPARQL endpoint availability check for Bookkeeping took 4.482269287109375e-05s
Availability | VoID file availability check for Bookkeeping took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.28452301025390625s
Reputation | Calculation of the PageRank for Bookkeeping took 0.020250558853149414s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bookkeeping took 6.198883056640625e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 2.8020384311676025s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Legal Ontology took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.2860743999481201s
Reputation | Calculation of the PageRank for Legal Ontology took 0.02012801170349121s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.3855438232421875e-05s
Believability | Calculation of trust value for Legal Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 2.8172948360443115s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.1961669921875e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.24500226974487305s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020288467407226562s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.00067901611328125s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.534027099609375e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 6.9141387939453125e-06s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 2.720518112182617s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 4.2438507080078125e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0002269744873046875s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.2501499652862549s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.020175457000732422s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.956390380859375e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 5.9604644775390625e-06s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 2.8222126960754395s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 5.841255187988281e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.26149940490722656s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 4.291534423828125e-05s
Believability | Calculation of trust value for Hua Hin Health Tourism Data Set took 6.67572021484375e-06s
INFO | --- Analysis for hua-hin-health-tourism-data-set took 3.064070463180542s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 4.029273986816406e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.2594428062438965s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 3.314018249511719e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.1682510375976562e-05s
INFO | --- Analysis for hud-library-usagedata took 2.874549388885498s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.3479454517364502s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0003571510314941406s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.26657652854919434s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.02056741714477539s
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.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.00010442733764648438s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 8.821487426757812e-06s
INFO | --- Analysis for hungarian-national-library-catalog took 4.595278263092041s
Availability | SPARQL endpoint availability check for IATE RDF took 4.124641418457031e-05s
Availability | VoID file availability check for IATE RDF took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.27661752700805664s
Reputation | Calculation of the PageRank for IATE RDF took 0.020430803298950195s
Interlinking | Calculation of Degree of Connection for IATE RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IATE RDF took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for IATE RDF took 7.867813110351562e-06s
INFO | --- Analysis for iate-rdf took 2.8195693492889404s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 4.029273986816406e-05s
Availability | VoID file availability check for IATI as Linked Data took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.26440882682800293s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.020156145095825195s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 0.00012683868408203125s
Believability | Calculation of trust value for IATI as Linked Data took 9.5367431640625e-06s
INFO | --- Analysis for iati-as-linked-data took 2.826395273208618s
Availability | SPARQL endpoint availability check for ICANE took 4.029273986816406e-05s
Availability | VoID file availability check for ICANE took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for ICANE took 0.27645230293273926s
Reputation | Calculation of the PageRank for ICANE took 0.020421981811523438s
Interlinking | Calculation of Degree of Connection for ICANE took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ICANE took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.559226989746094e-05s
Believability | Calculation of trust value for ICANE took 1.239776611328125e-05s
INFO | --- Analysis for icane took 2.8801581859588623s
Availability | SPARQL endpoint availability check for ichoose took 4.0531158447265625e-05s
Availability | VoID file availability check for ichoose took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for ichoose took 0.25502777099609375s
Reputation | Calculation of the PageRank for ichoose took 0.020391225814819336s
Interlinking | Calculation of Degree of Connection for ichoose took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ichoose took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.270408630371094e-05s
Believability | Calculation of trust value for ichoose took 6.9141387939453125e-06s
INFO | --- Analysis for ichoose took 2.8389129638671875s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 4.100799560546875e-05s
Availability | VoID file availability check for The Iconology Dataset took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.2781510353088379s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02016901969909668s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0006780624389648438s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.2636184692382812e-05s
Believability | Calculation of trust value for The Iconology Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for iconology-dataset took 2.852473020553589s
Availability | SPARQL endpoint availability check for Identifiers.org took 4.1961669921875e-05s
Availability | VoID file availability check for Identifiers.org took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.2514975070953369s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.647804260253906e-05s
Believability | Calculation of trust value for Identifiers.org took 6.67572021484375e-06s
INFO | --- Analysis for identifiers-org took 2.8153648376464844s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 5.602836608886719e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.2471461296081543s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02044057846069336s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.486343383789062e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 1.1682510375976562e-05s
INFO | --- Analysis for idreffr took 2.8096745014190674s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 4.00543212890625e-05s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.24282431602478027s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.02010512351989746s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.8160552978515625e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 8.106231689453125e-06s
INFO | --- Analysis for ids took 2.871398687362671s
Availability | SPARQL endpoint availability check for ietflang took 5.507469177246094e-05s
Availability | VoID file availability check for ietflang took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for ietflang took 0.2622559070587158s
Reputation | Calculation of the PageRank for ietflang took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for ietflang took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0006747245788574219s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.2438507080078125e-05s
Believability | Calculation of trust value for ietflang took 1.1682510375976562e-05s
INFO | --- Analysis for ietflang took 2.8140571117401123s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 3.981590270996094e-05s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.272244930267334s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.020275354385375977s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.695487976074219e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for IGVLL took 2.8742520809173584s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 4.267692565917969e-05s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.24242615699768066s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.02048039436340332s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0006783008575439453s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for IHE took 2.8757059574127197s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 0.15690970420837402s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.24535489082336426s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 6.9141387939453125e-06s
INFO | --- Analysis for iislod-test took 3.0145351886749268s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.00543212890625e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.2621583938598633s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.020499467849731445s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 3.0517578125e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 6.9141387939453125e-06s
INFO | --- Analysis for ILUSOC took 2.8812437057495117s
Availability | SPARQL endpoint availability check for im@sparql took 4.00543212890625e-05s
Availability | VoID file availability check for im@sparql took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for im@sparql took 0.25379419326782227s
Reputation | Calculation of the PageRank for im@sparql took 0.021148681640625s
Interlinking | Calculation of Degree of Connection for im@sparql took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for im@sparql took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.956390380859375e-05s
Believability | Calculation of trust value for im@sparql took 7.867813110351562e-06s
INFO | --- Analysis for im@sparql took 2.800302028656006s
Availability | SPARQL endpoint availability check for imagery bailingniao took 5.340576171875e-05s
Availability | VoID file availability check for imagery bailingniao took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.28804469108581543s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.8848648071289062e-05s
Believability | Calculation of trust value for imagery bailingniao took 6.4373016357421875e-06s
INFO | --- Analysis for imagery_bailingniao took 2.8450722694396973s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 4.0531158447265625e-05s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.26729679107666016s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 9.179115295410156e-05s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 7.62939453125e-06s
INFO | --- Analysis for imagesnippets took 2.887007474899292s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 4.029273986816406e-05s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.252000093460083s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020644426345825195s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 9.489059448242188e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.049041748046875e-05s
INFO | --- Analysis for imf-linked-data took 2.853041172027588s
Availability | SPARQL endpoint availability check for IMGpedia took 4.2438507080078125e-05s
Availability | VoID file availability check for IMGpedia took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.2552804946899414s
Reputation | Calculation of the PageRank for IMGpedia took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for IMGpedia took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for IMGpedia took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.123283386230469e-05s
Believability | Calculation of trust value for IMGpedia took 6.67572021484375e-06s
INFO | --- Analysis for imgpedia took 2.876431703567505s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 3.910064697265625e-05s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.25368475914001465s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.020500659942626953s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.9802322387695312e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 6.67572021484375e-06s
INFO | --- Analysis for import-status-of-gmo-crops took 2.8509771823883057s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 3.9577484130859375e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.274996280670166s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.3113021850585938e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 7.62939453125e-06s
INFO | --- Analysis for Imtiaz took 2.833279848098755s
Availability | SPARQL endpoint availability check for Royalty Free Music took 4.00543212890625e-05s
Availability | VoID file availability check for Royalty Free Music took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.2570044994354248s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.02023482322692871s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.9325485229492188e-05s
Believability | Calculation of trust value for Royalty Free Music took 6.9141387939453125e-06s
INFO | --- Analysis for inaudio.org took 2.8512959480285645s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.8160552978515625e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00036597251892089844s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.2736060619354248s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 3.3855438232421875e-05s
Believability | Calculation of trust value for Income and production cost of grape by year took 7.62939453125e-06s
INFO | --- Analysis for income-and-production-cost-of-grape-by-year took 2.8151979446411133s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 4.3392181396484375e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.24988579750061035s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 3.314018249511719e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 8.106231689453125e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 2.780973196029663s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 4.315376281738281e-05s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.2605407238006592s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 4.76837158203125e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 7.62939453125e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 2.881117820739746s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 4.220008850097656e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.2742302417755127s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.020537614822387695s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.3855438232421875e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 8.344650268554688e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 2.853698968887329s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 4.696846008300781e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.2776026725769043s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020856857299804688s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0008387565612792969s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 0.00011801719665527344s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.3909759521484375e-06s
INFO | --- Analysis for ineverycrea took 2.886013984680176s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 4.506111145019531e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.2774465084075928s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02093791961669922s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 9.775161743164062e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.344650268554688e-06s
INFO | --- Analysis for ineverycrea-argentina took 2.885284185409546s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 5.435943603515625e-05s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0003654956817626953s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.25085902214050293s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02089214324951172s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 7.009506225585938e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for influence-tracker-dataset took 2.802795648574829s
Availability | SPARQL endpoint availability check for INSEMTIVES took 4.076957702636719e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.26383209228515625s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020920991897583008s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 3.24249267578125e-05s
Believability | Calculation of trust value for INSEMTIVES took 8.344650268554688e-06s
INFO | --- Analysis for insemtives took 2.8683559894561768s
Availability | SPARQL endpoint availability check for instagram.person took 4.076957702636719e-05s
Availability | VoID file availability check for instagram.person took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for instagram.person took 0.2349076271057129s
Reputation | Calculation of the PageRank for instagram.person took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for instagram.person took 2.9087066650390625e-05s
Believability | Calculation of trust value for instagram.person took 8.106231689453125e-06s
INFO | --- Analysis for instagram_person took 2.749753475189209s
Availability | SPARQL endpoint availability check for instagram.videoobject took 4.1484832763671875e-05s
Availability | VoID file availability check for instagram.videoobject took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.24214529991149902s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020760059356689453s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.24249267578125e-05s
Believability | Calculation of trust value for instagram.videoobject took 7.62939453125e-06s
INFO | --- Analysis for instagram_videoobject took 2.843968391418457s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 4.315376281738281e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.2609395980834961s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.020598173141479492s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 3.2901763916015625e-05s
Believability | Calculation of trust value for Instance Hub Countries took 8.344650268554688e-06s
INFO | --- Analysis for instance-hub-countries took 2.8246009349823s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 4.1484832763671875e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.2537062168121338s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020631074905395508s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 3.457069396972656e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-fiscal-years took 2.8573620319366455s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 4.2438507080078125e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.26003193855285645s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.314018249511719e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.1682510375976562e-05s
INFO | --- Analysis for instance-hub-organizations took 2.8030753135681152s
Availability | SPARQL endpoint availability check for Instance Hub People took 4.00543212890625e-05s
Availability | VoID file availability check for Instance Hub People took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.2651994228363037s
Reputation | Calculation of the PageRank for Instance Hub People took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.218650817871094e-05s
Believability | Calculation of trust value for Instance Hub People took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-people took 3.3438258171081543s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 8.797645568847656e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.24739575386047363s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.266334533691406e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 8.821487426757812e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.7737975120544434s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 4.076957702636719e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.2749462127685547s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 6.9141387939453125e-06s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.8304121494293213s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 4.124641418457031e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.000347137451171875s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.2616896629333496s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.020179033279418945s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 1.2159347534179688e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.91083025932312s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 3.9577484130859375e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.2623934745788574s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0040740966796875e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.859957218170166s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 3.981590270996094e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.25498461723327637s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0007524490356445312s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.075599670410156e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-federal-agencies took 2.858654260635376s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 4.00543212890625e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.25052595138549805s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.020733118057250977s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.814697265625e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 7.152557373046875e-06s
INFO | --- Analysis for instance-hub-us-states-and-territories took 2.821497917175293s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 3.933906555175781e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.2673487663269043s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.02073502540588379s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.2901763916015625e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 6.67572021484375e-06s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 2.8592052459716797s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 4.124641418457031e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.23734450340270996s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.24249267578125e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.0251998901367188e-05s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 2.8223538398742676s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.1961669921875e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.26456785202026367s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00012445449829101562s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for interactivemaps-gnoss took 2.8532378673553467s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 7.796287536621094e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.2662205696105957s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020829439163208008s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.361701965332031e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.2636184692382812e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 2.8469669818878174s
Availability | SPARQL endpoint availability check for intervalue took 4.124641418457031e-05s
Availability | VoID file availability check for intervalue took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for intervalue took 0.27739810943603516s
Reputation | Calculation of the PageRank for intervalue took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for intervalue took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for intervalue took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for intervalue took 7.009506225585938e-05s
Believability | Calculation of trust value for intervalue took 6.4373016357421875e-06s
INFO | --- Analysis for intervalue took 2.8920671939849854s
Availability | SPARQL endpoint availability check for Inztrow took 4.6253204345703125e-05s
Availability | VoID file availability check for Inztrow took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Inztrow took 0.27329397201538086s
Reputation | Calculation of the PageRank for Inztrow took 0.020699501037597656s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0007572174072265625s
Interlinking | Calculation of Clustering coefficient for Inztrow took 3.170967102050781e-05s
Believability | Calculation of trust value for Inztrow took 7.62939453125e-06s
INFO | --- Analysis for Inztrow took 2.887690782546997s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.0004963874816894531s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.26935315132141113s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.020350933074951172s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for ipbes took 2.8835344314575195s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.172325134277344e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.00022411346435546875s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.2625424861907959s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.02049565315246582s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.9114227294921875e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.3909759521484375e-06s
INFO | --- Analysis for iptc-newscodes took 2.8610105514526367s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.38690185546875e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.000274658203125s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.26662349700927734s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 3.361701965332031e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 7.152557373046875e-06s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 2.8676185607910156s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 8.249282836914062e-05s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.24985837936401367s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.02064371109008789s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007417201995849609s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.608268737792969e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 7.3909759521484375e-06s
INFO | --- Analysis for iserve took 2.790595054626465s
Availability | SPARQL endpoint availability check for ISIC V4 took 4.1484832763671875e-05s
Availability | VoID file availability check for ISIC V4 took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.23518586158752441s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020371198654174805s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.933906555175781e-05s
Believability | Calculation of trust value for ISIC V4 took 1.1205673217773438e-05s
INFO | --- Analysis for isic-v4 took 2.859999656677246s
Availability | SPARQL endpoint availability check for Isidore took 4.124641418457031e-05s
Availability | VoID file availability check for Isidore took 0.0002486705780029297s
Completeness | Calculation of interlinking completeness for Isidore took 0.2532510757446289s
Reputation | Calculation of the PageRank for Isidore took 0.02042078971862793s
Interlinking | Calculation of Degree of Connection for Isidore took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.0517578125e-05s
Believability | Calculation of trust value for Isidore took 1.1444091796875e-05s
INFO | --- Analysis for isidore took 2.827122211456299s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 4.2438507080078125e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.26990532875061035s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020282506942749023s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 7.05718994140625e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 7.152557373046875e-06s
INFO | --- Analysis for isil-dbpedia took 2.8245623111724854s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 4.6253204345703125e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0005517005920410156s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.28014683723449707s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.020826339721679688s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 7.3909759521484375e-06s
INFO | --- Analysis for iso-3166-2-data took 2.828690767288208s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 4.0531158447265625e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.00034356117248535156s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.2708609104156494s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.020853757858276367s
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.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.838539123535156e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 7.3909759521484375e-06s
INFO | --- Analysis for iso-639-oasis took 2.88216233253479s
Availability | SPARQL endpoint availability check for ISOcat took 4.0531158447265625e-05s
Availability | VoID file availability check for ISOcat took 0.0005819797515869141s
Completeness | Calculation of interlinking completeness for ISOcat took 0.26541948318481445s
Reputation | Calculation of the PageRank for ISOcat took 0.020813465118408203s
Interlinking | Calculation of Degree of Connection for ISOcat took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for ISOcat took 0.0012226104736328125s
Interlinking | Calculation of Clustering coefficient for ISOcat took 8.392333984375e-05s
Believability | Calculation of trust value for ISOcat took 7.62939453125e-06s
INFO | --- Analysis for isocat took 2.8674371242523193s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 4.00543212890625e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.26993751525878906s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.020300865173339844s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.62396240234375e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.239776611328125e-05s
INFO | --- Analysis for isocat-metadata took 2.9158530235290527s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 4.172325134277344e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.23804378509521484s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 4.029273986816406e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 1.2159347534179688e-05s
INFO | --- Analysis for ispra-lod-ihi took 2.8507630825042725s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.124641418457031e-05s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.262345552444458s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0010542869567871094s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.000102996826171875s
Believability | Calculation of trust value for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 7.152557373046875e-06s
INFO | --- Analysis for ispra-lod-place took 2.808494806289673s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 4.124641418457031e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.24995946884155273s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.075599670410156e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 7.3909759521484375e-06s
INFO | --- Analysis for ispra-lod-rmn took 2.869896650314331s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 4.482269287109375e-05s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.2538642883300781s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020758390426635742s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.504753112792969e-05s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 8.58306884765625e-06s
INFO | --- Analysis for ispra-lod-ron took 2.8277902603149414s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 3.886222839355469e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.2541515827178955s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.02037644386291504s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 2.956390380859375e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 6.9141387939453125e-06s
INFO | --- Analysis for ispra-lod-sc took 2.8173365592956543s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 4.124641418457031e-05s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.2744579315185547s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.02015995979309082s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.00067901611328125s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 9.131431579589844e-05s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 6.4373016357421875e-06s
INFO | --- Analysis for issa-agritrop took 2.91036057472229s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.4345855712890625e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0003006458282470703s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.25994229316711426s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.0205533504486084s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.0279159545898438e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 8.821487426757812e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.7781550884246826s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.029273986816406e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.00031304359436035156s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.25249242782592773s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.021460771560668945s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0009243488311767578s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.790855407714844e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.152557373046875e-06s
INFO | --- Analysis for ISSN:_0080-3626 took 2.7978076934814453s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 4.553794860839844e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.25623059272766113s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.0040740966796875e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 7.62939453125e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 2.752995729446411s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 5.316734313964844e-05s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.26276659965515137s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.020642995834350586s
Interlinking | Calculation of Degree of Connection for ISTAT Immigration (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ISTAT Immigration (LinkedOpenData.it) took 0.0007736682891845703s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.845329284667969e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for istat-immigration took 2.8578805923461914s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 4.0531158447265625e-05s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.24347543716430664s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.020241498947143555s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.8848648071289062e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 7.867813110351562e-06s
INFO | --- Analysis for istat-immigrazione took 2.7967076301574707s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 4.100799560546875e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.26571106910705566s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.86102294921875e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 7.62939453125e-06s
INFO | --- Analysis for it-aifa-drug-prices took 2.904538869857788s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 4.0531158447265625e-05s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.26026391983032227s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020023345947265625s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 7.486343383789062e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 7.152557373046875e-06s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.8460512161254883s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 4.00543212890625e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.25021815299987793s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0008015632629394531s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 3.24249267578125e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 7.152557373046875e-06s
INFO | --- Analysis for iucr-acta-cryst-e took 2.818913698196411s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.172325134277344e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.28885865211486816s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 2.8371810913085938e-05s
Believability | Calculation of trust value for IWMI Research Reports took 7.62939453125e-06s
INFO | --- Analysis for iwmi-research-reports took 2.854431390762329s
Availability | SPARQL endpoint availability check for IWN took 4.1961669921875e-05s
Availability | VoID file availability check for IWN took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for IWN took 0.2535114288330078s
Reputation | Calculation of the PageRank for IWN took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for IWN took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IWN took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for IWN took 3.790855407714844e-05s
Believability | Calculation of trust value for IWN took 6.67572021484375e-06s
INFO | --- Analysis for iwn took 2.8399219512939453s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 5.030632019042969e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0003962516784667969s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.27516651153564453s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 3.743171691894531e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 7.3909759521484375e-06s
INFO | --- Analysis for j-global-knowledge took 2.8035812377929688s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 4.982948303222656e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.2483675479888916s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.02027273178100586s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 2.9802322387695312e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 7.62939453125e-06s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.8540256023406982s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 7.993045806884766s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.2552778720855713s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.02033686637878418s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 6.008148193359375e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 7.867813110351562e-06s
INFO | --- Analysis for jamendo-dbtune took 17.548117876052856s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 5.14984130859375e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.24991369247436523s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020344972610473633s
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.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.458427429199219e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 6.4373016357421875e-06s
INFO | --- Analysis for japan-radioactivity-stat took 2.848365306854248s
Availability | SPARQL endpoint availability check for JEL Classification took 5.173683166503906e-05s
Availability | VoID file availability check for JEL Classification took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.24544239044189453s
Reputation | Calculation of the PageRank for JEL Classification took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for JEL Classification took 2.4080276489257812e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0006780624389648438s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 2.765655517578125e-05s
Believability | Calculation of trust value for JEL Classification took 1.1205673217773438e-05s
INFO | --- Analysis for jel-classification took 2.8318071365356445s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.045938491821289s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0003123283386230469s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.2599451541900635s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007200241088867188s
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 7.3909759521484375e-06s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 4.053650617599487s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 261.8816747665405s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0007059574127197266s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.2722651958465576s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.020543575286865234s
Interlinking | Calculation of Degree of Connection for JITA Classification System of Library and Information Science took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for JITA Classification System of Library and Information Science took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 7.033348083496094e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 7.152557373046875e-06s
INFO | --- Analysis for jita took 536.6848258972168s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 4.029273986816406e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.6915435791015625s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 3.170967102050781e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 7.152557373046875e-06s
INFO | --- Analysis for jmdict took 3.6923108100891113s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.083234786987305s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.2523496150970459s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.02071833610534668s
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.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 9.131431579589844e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 7.3909759521484375e-06s
INFO | --- Analysis for john-goodwins-family-tree took 23.089607000350952s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.0531158447265625e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.0010995864868164062s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.262664794921875s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.314018249511719e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 6.198883056640625e-06s
INFO | --- Analysis for jp-cos took 2.793174982070923s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.124641418457031e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.26885509490966797s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020931005477905273s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 4.482269287109375e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 7.62939453125e-06s
INFO | --- Analysis for jp-textbook took 2.8017170429229736s
Availability | SPARQL endpoint availability check for JRC-Names took 4.029273986816406e-05s
Availability | VoID file availability check for JRC-Names took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.25073766708374023s
Reputation | Calculation of the PageRank for JRC-Names took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for JRC-Names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.2901763916015625e-05s
Believability | Calculation of trust value for JRC-Names took 1.2159347534179688e-05s
INFO | --- Analysis for jrc-names-ec took 2.8389573097229004s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 4.0531158447265625e-05s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.2643885612487793s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.02071833610534668s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0008599758148193359s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 7.677078247070312e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 9.775161743164062e-06s
INFO | --- Analysis for jrc-names-mlode took 2.9128358364105225s
Availability | SPARQL endpoint availability check for JudaicaLink took 4.1961669921875e-05s
Availability | VoID file availability check for JudaicaLink took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.25386857986450195s
Reputation | Calculation of the PageRank for JudaicaLink took 0.021911144256591797s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0008893013000488281s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.00011563301086425781s
Believability | Calculation of trust value for JudaicaLink took 6.198883056640625e-06s
INFO | --- Analysis for judaicalink took 2.827997922897339s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 3.981590270996094e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.27457356452941895s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.020431995391845703s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 2.956390380859375e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 7.3909759521484375e-06s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.8626174926757812s
Availability | SPARQL endpoint availability check for KAKEN took 4.100799560546875e-05s
Availability | VoID file availability check for KAKEN took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for KAKEN took 0.25358152389526367s
Reputation | Calculation of the PageRank for KAKEN took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for KAKEN took 2.9325485229492188e-05s
Believability | Calculation of trust value for KAKEN took 6.9141387939453125e-06s
INFO | --- Analysis for kaken took 2.7906317710876465s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 4.029273986816406e-05s
Availability | VoID file availability check for Kallikratis municipalities took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.2423863410949707s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.020197391510009766s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 9.465217590332031e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 6.67572021484375e-06s
INFO | --- Analysis for kallikratis-municipalities took 2.8265833854675293s
Availability | SPARQL endpoint availability check for Openflights Routes took 4.029273986816406e-05s
Availability | VoID file availability check for Openflights Routes took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.24173259735107422s
Reputation | Calculation of the PageRank for Openflights Routes took 0.02001023292541504s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 2.8133392333984375e-05s
Believability | Calculation of trust value for Openflights Routes took 2.47955322265625e-05s
INFO | --- Analysis for kasabi-openflights-routes took 2.7072207927703857s
Availability | SPARQL endpoint availability check for EU Soccer League took 5.030632019042969e-05s
Availability | VoID file availability check for EU Soccer League took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.26842808723449707s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0006785392761230469s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.0517578125e-05s
Believability | Calculation of trust value for EU Soccer League took 8.106231689453125e-06s
INFO | --- Analysis for KG:Course_Submission took 2.7967498302459717s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 4.267692565917969e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.00039076805114746094s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.23604083061218262s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.239776611328125e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for KING took 2.7747128009796143s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 4.100799560546875e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.24817490577697754s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.028955936431884766s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.890296936035156e-05s
Believability | Calculation of trust value for Klappstuhlclub took 1.0251998901367188e-05s
INFO | --- Analysis for klappstuhlclub took 2.8323800563812256s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 4.029273986816406e-05s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.25748252868652344s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020286083221435547s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 5.91278076171875e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 7.152557373046875e-06s
INFO | --- Analysis for knoesis-linked-sensor-data took 2.7341179847717285s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.00543212890625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.26188182830810547s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0517578125e-05s
Believability | Calculation of trust value for Knowledge Forest took 8.344650268554688e-06s
INFO | --- Analysis for knowledge-map took 2.829029083251953s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.5299530029296875e-05s
Availability | VoID file availability check for Knowledge Forest took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.24893736839294434s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0040740966796875e-05s
Believability | Calculation of trust value for Knowledge Forest took 8.106231689453125e-06s
INFO | --- Analysis for KnowledgeFusion took 2.8105101585388184s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.00543212890625e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.279552698135376s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02049851417541504s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007944107055664062s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.556510925292969e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 8.58306884765625e-06s
INFO | --- Analysis for kore-50-nif-ner-corpus took 2.8463408946990967s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 8.535385131835938e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.25831031799316406s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 2.956390380859375e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 6.9141387939453125e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 2.849630832672119s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 4.4345855712890625e-05s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00029754638671875s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.24901199340820312s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.020096778869628906s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 2.9325485229492188e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 8.106231689453125e-06s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.747453212738037s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 3.933906555175781e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.25404810905456543s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020260095596313477s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.86102294921875e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 7.3909759521484375e-06s
INFO | --- Analysis for ktr took 2.8013486862182617s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.1961669921875e-05s
Availability | VoID file availability check for Informatics Studies took 0.0003390312194824219s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.23745417594909668s
Reputation | Calculation of the PageRank for Informatics Studies took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0006792545318603516s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.86102294921875e-05s
Believability | Calculation of trust value for Informatics Studies took 6.9141387939453125e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.7400174140930176s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 3.9577484130859375e-05s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.2527124881744385s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.02014327049255371s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 4.6253204345703125e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 6.9141387939453125e-06s
INFO | --- Analysis for kupkb took 2.8673768043518066s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.076957702636719e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.2530679702758789s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 2.86102294921875e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 6.67572021484375e-06s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 2.780777931213379s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 3.9577484130859375e-05s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.0002999305725097656s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.26244235038757324s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.390975952148438e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 7.152557373046875e-06s
INFO | --- Analysis for l3s-dblp took 2.853050947189331s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0002739429473876953s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.2561147212982178s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.0200958251953125s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.604194641113281e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 7.152557373046875e-06s
INFO | --- Analysis for lak-dataset took 2.9028420448303223s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 5.698204040527344e-05s
Availability | VoID file availability check for  Language Name Authority List  took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.23911285400390625s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 9.131431579589844e-05s
Believability | Calculation of trust value for  Language Name Authority List  took 6.198883056640625e-06s
INFO | --- Analysis for language-authority-list took 2.7981984615325928s
Availability | SPARQL endpoint availability check for Lark took 3.9577484130859375e-05s
Availability | VoID file availability check for Lark took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Lark took 0.25777387619018555s
Reputation | Calculation of the PageRank for Lark took 0.020153284072875977s
Interlinking | Calculation of Degree of Connection for Lark took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lark took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for Lark took 6.628036499023438e-05s
Believability | Calculation of trust value for Lark took 5.9604644775390625e-06s
INFO | --- Analysis for LARK took 2.78566312789917s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 3.9577484130859375e-05s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.2538137435913086s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 4.00543212890625e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 7.152557373046875e-06s
INFO | --- Analysis for LASLA took 2.7629716396331787s
Availability | SPARQL endpoint availability check for LATC Linksets took 7.295608520507812e-05s
Availability | VoID file availability check for LATC Linksets took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.24851632118225098s
Reputation | Calculation of the PageRank for LATC Linksets took 0.020319700241088867s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 3.218650817871094e-05s
Believability | Calculation of trust value for LATC Linksets took 7.3909759521484375e-06s
INFO | --- Analysis for latc-linksets took 2.755460262298584s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 5.412101745605469e-05s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.2636528015136719s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.020540714263916016s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.933906555175781e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 7.62939453125e-06s
INFO | --- Analysis for Latin_Vallex2.0 took 2.812526226043701s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 3.9577484130859375e-05s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.24568462371826172s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LatinAffectus took 2.841580867767334s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 4.00543212890625e-05s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.24657344818115234s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.100799560546875e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 7.62939453125e-06s
INFO | --- Analysis for LatinWordnetLiLa took 2.756361961364746s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 4.1484832763671875e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.2548542022705078s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 8.106231689453125e-06s
INFO | --- Analysis for lcc took 2.7892119884490967s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 4.1484832763671875e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0006055831909179688s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.2604334354400635s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02061152458190918s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00012135505676269531s
Believability | Calculation of trust value for Library of Congress Subject Headings took 6.9141387939453125e-06s
INFO | --- Analysis for lcsh took 3.461974859237671s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 7.486343383789062e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.24448204040527344s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.020328760147094727s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 8.654594421386719e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 7.3909759521484375e-06s
INFO | --- Analysis for lcsubjects took 2.998471975326538s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 4.029273986816406e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.2493288516998291s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.019980907440185547s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.0040740966796875e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 7.3909759521484375e-06s
INFO | --- Analysis for ldqm-dbpedia-2016 took 2.878042221069336s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.602020978927612s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.254244327545166s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.02056717872619629s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.124641418457031e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 6.198883056640625e-06s
INFO | --- Analysis for ldt@library took 16.060944318771362s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 4.792213439941406e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.26476335525512695s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020491600036621094s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Eng took 2.956390380859375e-05s
Believability | Calculation of trust value for Learned Genre Ontology Eng took 6.198883056640625e-06s
INFO | --- Analysis for learned-genre-ontology-eng took 2.866947650909424s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.267692565917969e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.2651221752166748s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 3.409385681152344e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 8.58306884765625e-06s
INFO | --- Analysis for learned-genre-ontology-intl took 2.867147445678711s
Availability | SPARQL endpoint availability check for U ime Legije took 4.172325134277344e-05s
Availability | VoID file availability check for U ime Legije took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.24746394157409668s
Reputation | Calculation of the PageRank for U ime Legije took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 2.86102294921875e-05s
Believability | Calculation of trust value for U ime Legije took 6.67572021484375e-06s
INFO | --- Analysis for LEGIJA_STRANACA took 2.8380634784698486s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 8.463859558105469e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.26450586318969727s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.022871971130371094s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0009233951568603516s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 4.00543212890625e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.239776611328125e-05s
INFO | --- Analysis for legislation-openuplabs took 2.8575518131256104s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 5.3882598876953125e-05s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.26091885566711426s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.176399230957031e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 7.62939453125e-06s
INFO | --- Analysis for LemmaBank took 2.8398025035858154s
Availability | SPARQL endpoint availability check for lemonUby took 4.00543212890625e-05s
Availability | VoID file availability check for lemonUby took 0.0003387928009033203s
Completeness | Calculation of interlinking completeness for lemonUby took 0.24287033081054688s
Reputation | Calculation of the PageRank for lemonUby took 0.020234346389770508s
Interlinking | Calculation of Degree of Connection for lemonUby took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lemonUby took 0.000743865966796875s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.699562072753906e-05s
Believability | Calculation of trust value for lemonUby took 5.9604644775390625e-06s
INFO | --- Analysis for lemonuby took 2.863492488861084s
Availability | SPARQL endpoint availability check for LemonWiktionary took 6.532669067382812e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.2623329162597656s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 3.600120544433594e-05s
Believability | Calculation of trust value for LemonWiktionary took 7.3909759521484375e-06s
INFO | --- Analysis for lemonwiktionary took 2.8843002319335938s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 4.8160552978515625e-05s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.24763989448547363s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.020769119262695312s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007781982421875s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 4.4345855712890625e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 8.821487426757812e-06s
INFO | --- Analysis for LewisShort took 2.826453924179077s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 3.9577484130859375e-05s
Availability | VoID file availability check for LEXIN-RDF took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.2737853527069092s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020878076553344727s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.266334533691406e-05s
Believability | Calculation of trust value for LEXIN-RDF took 8.58306884765625e-06s
INFO | --- Analysis for lexin-rdf took 2.790666103363037s
Availability | SPARQL endpoint availability check for lexinfo took 3.9577484130859375e-05s
Availability | VoID file availability check for lexinfo took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for lexinfo took 0.24938678741455078s
Reputation | Calculation of the PageRank for lexinfo took 0.02008676528930664s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.654594421386719e-05s
Believability | Calculation of trust value for lexinfo took 7.3909759521484375e-06s
INFO | --- Analysis for lexinfo took 2.818788528442383s
Availability | SPARQL endpoint availability check for Lexvo took 4.1484832763671875e-05s
Availability | VoID file availability check for Lexvo took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for Lexvo took 0.27783989906311035s
Reputation | Calculation of the PageRank for Lexvo took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.00017499923706054688s
Believability | Calculation of trust value for Lexvo took 7.62939453125e-06s
INFO | --- Analysis for lexvo took 2.866675853729248s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.1961669921875e-05s
Availability | VoID file availability check for Lexvo.org took 0.00022840499877929688s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.2639584541320801s
Reputation | Calculation of the PageRank for Lexvo.org took 0.02017831802368164s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.414817810058594e-05s
Believability | Calculation of trust value for Lexvo.org took 1.1682510375976562e-05s
INFO | --- Analysis for lexvo-org took 2.854501485824585s
Availability | SPARQL endpoint availability check for LIBRIS took 0.2953667640686035s
Availability | VoID file availability check for LIBRIS took 0.0002620220184326172s
Extra | Recovery of all triples for LIBRIS took 6.324949026107788s
Performance | Total latancy measurement for LIBRIS took 0.704725980758667s
Amount of data | Number of triples check for LIBRIS took 28.143738269805908s
Interoperability | New terms check for LIBRIS took 15.751574277877808s
Versatility | Languages check for LIBRIS took 0.16256070137023926s
Interpretability | Number of blank nodes check for LIBRIS took 300.0900161266327s
Security | Check HTTPS for LIBRIS took 0.39421916007995605s
Interpretability | RDF structures check for LIBRIS took 0.2843208312988281s
Versatility | Serialization formats check for LIBRIS took 0.17348814010620117s
Availability | RDF dump link check for LIBRIS took 0.14188551902770996s
License | MR license check for LIBRIS took 0.2267320156097412s
License | HR license check for LIBRIS took 0.17026972770690918s
Amount of data | Number of property check for LIBRIS took 0.17425870895385742s
Understandability | Number of label check for LIBRIS took 0.25466251373291016s
Understandability | URI regex check for LIBRIS took 0.313584566116333s
Understandability | Vocabs check for LIBRIS took 0.14368176460266113s
Verifiability | Authors check for LIBRIS took 0.14856266975402832s
Verifiability | Publishers check for LIBRIS took 0.1594853401184082s
Performance | Throughput check for LIBRIS took 11.152059316635132s
Amount of data | Check the number of entities for LIBRIS took 3.218650817871094e-05s
Verifiability | Contribs. check for LIBRIS took 0.15418124198913574s
Interlinking | sameAs chians check for LIBRIS took 0.2242882251739502s
Interlinking | skos check for LIBRIS took 0.24540424346923828s
Interlinking | skos check for LIBRIS took 0.13903141021728516s
Timeliness | dataset update frequency check for LIBRIS took 0.14776396751403809s
Currency | Creation date check for LIBRIS took 0.34253716468811035s
Currency | Modification date check for LIBRIS took 0.5938923358917236s
Rep.Conc. | URIs length for LIBRIS took 80.42470645904541s
Interoperability | New vocabularies check for LIBRIS took 6.67572021484375e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.15693926811218262s
Accuracy | Check Functional Property for LIBRIS took 0.16428494453430176s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.17021703720092773s
Accuracy | Check Datatype consistency for LIBRIS took 0.26758527755737305s
Consistency | Disjoint class check for LIBRIS took 0.16371798515319824s
Consistency | Check Misplaced properties for LIBRIS took 62.00462102890015s
Consistency | Misplaced classes for LIBRIS took 1.0851640701293945s
Consistency | Check Ontology hijacking for LIBRIS took 3.2127654552459717s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.3437590599060059s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 63.101465940475464s
Conciseness | Check Extensional conciseness for LIBRIS took 0.27167844772338867s
Conciseness | Check Intensional conciseness for LIBRIS took 0.41034579277038574s
Security | Sign check for LIBRIS took 0.24138140678405762s
Availability | Check URIs Dereferenciability for LIBRIS took 14.369250774383545s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.45467543601989746s
Reputation | Calculation of the PageRank for LIBRIS took 0.019986867904663086s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006716251373291016s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 9.202957153320312e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.430511474609375e-06s
Believability | Calculation of trust value for LIBRIS took 6.9141387939453125e-06s
INFO | --- Analysis for libris took 1082.6243345737457s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.12341976165771484s
Availability | VoID file availability check for Public Library of Veroia took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.25780296325683594s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.033348083496094e-05s
Believability | Calculation of trust value for Public Library of Veroia took 6.67572021484375e-06s
INFO | --- Analysis for libver took 3.881906270980835s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 3.933906555175781e-05s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.25687503814697266s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.605552673339844e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 8.106231689453125e-06s
INFO | --- Analysis for lichfield-spending took 2.8103182315826416s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 7.62939453125e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.00032711029052734375s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.25513291358947754s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.170967102050781e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.1444091796875e-05s
INFO | --- Analysis for lime took 2.7967097759246826s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 4.029273986816406e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.26479077339172363s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.02002859115600586s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010371208190917969s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 6.4373016357421875e-06s
INFO | --- Analysis for lingvoj took 2.8416662216186523s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 5.030632019042969e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.27556371688842773s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.020188331604003906s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.724761962890625e-05s
Believability | Calculation of trust value for Linked Crunchbase took 8.344650268554688e-06s
INFO | --- Analysis for linked-crunchbase took 2.882472515106201s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 4.0531158447265625e-05s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.2453322410583496s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 7.152557373046875e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.4373016357421875e-06s
INFO | --- Analysis for linked-drugs took 2.766204833984375s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.26484084129333496s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.000751495361328125s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.250640869140625e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 7.867813110351562e-06s
INFO | --- Analysis for linked-edgar took 2.819167375564575s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.744529724121094e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.23679161071777344s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020752429962158203s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.465217590332031e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.3113021850585938e-05s
INFO | --- Analysis for linked-eurostat took 2.7326509952545166s
Availability | SPARQL endpoint availability check for linked hypernyms took 3.886222839355469e-05s
Availability | VoID file availability check for linked hypernyms took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.234053373336792s
Reputation | Calculation of the PageRank for linked hypernyms took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.152557373046875e-05s
Believability | Calculation of trust value for linked hypernyms took 9.5367431640625e-06s
INFO | --- Analysis for linked-hypernyms took 2.884647846221924s
Availability | SPARQL endpoint availability check for Linked Life Data took 3.933906555175781e-05s
Availability | VoID file availability check for Linked Life Data took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.2569127082824707s
Reputation | Calculation of the PageRank for Linked Life Data took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.029273986816406e-05s
Believability | Calculation of trust value for Linked Life Data took 1.239776611328125e-05s
INFO | --- Analysis for linked-life-data took 2.7972588539123535s
Availability | SPARQL endpoint availability check for Linked Logainm took 3.9577484130859375e-05s
Availability | VoID file availability check for Linked Logainm took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.2619314193725586s
Reputation | Calculation of the PageRank for Linked Logainm took 0.021142244338989258s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 7.963180541992188e-05s
Believability | Calculation of trust value for Linked Logainm took 8.106231689453125e-06s
INFO | --- Analysis for linked-logainm took 2.8778531551361084s
Availability | SPARQL endpoint availability check for Linked NUTS took 8.177757263183594e-05s
Availability | VoID file availability check for Linked NUTS took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.2509429454803467s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 5.245208740234375e-05s
Believability | Calculation of trust value for Linked NUTS took 7.62939453125e-06s
INFO | --- Analysis for linked-nuts took 2.847628355026245s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 3.886222839355469e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.2636427879333496s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.02067255973815918s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 3.170967102050781e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 1.1205673217773438e-05s
INFO | --- Analysis for linked-open-aalto-data-service took 2.7966198921203613s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 9.918212890625e-05s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.26309943199157715s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.020931243896484375s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.910064697265625e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-camera took 2.8627641201019287s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Open Commerce took 0.000244140625s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.27249646186828613s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.021033048629760742s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.1682510375976562e-05s
INFO | --- Analysis for linked-open-commerce took 2.8487002849578857s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.24021506309509277s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010323524475097656s
Believability | Calculation of trust value for Linked Open Data of Ecology took 8.58306884765625e-06s
INFO | --- Analysis for linked-open-data-of-ecology took 2.8213443756103516s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 4.1961669921875e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.2502570152282715s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020830392837524414s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 9.012222290039062e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.239776611328125e-05s
INFO | --- Analysis for linked-open-numbers took 2.749323606491089s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 8.7738037109375e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00030040740966796875s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.2588191032409668s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.020518064498901367s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 3.600120544433594e-05s
Believability | Calculation of trust value for Linked Open Piracy took 1.0013580322265625e-05s
INFO | --- Analysis for linked-open-piracy took 2.8758161067962646s
Availability | SPARQL endpoint availability check for Linked Open Senate (linkedopendata.it) took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Senate (linkedopendata.it) took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.2797422409057617s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020946264266967773s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.147125244140625e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-senate took 2.824622631072998s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.26046228408813477s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.792213439941406e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 7.3909759521484375e-06s
INFO | --- Analysis for linked-open-vocabularies-lov took 3.0652987957000732s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 3.9577484130859375e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.2518305778503418s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0006814002990722656s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 7.62939453125e-06s
INFO | --- Analysis for linked-periodicals took 2.8822247982025146s
Availability | SPARQL endpoint availability check for Linked Index took 3.933906555175781e-05s
Availability | VoID file availability check for Linked Index took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for Linked Index took 0.2672109603881836s
Reputation | Calculation of the PageRank for Linked Index took 0.02064967155456543s
Interlinking | Calculation of Degree of Connection for Linked Index took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Index took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.249282836914062e-05s
Believability | Calculation of trust value for Linked Index took 7.867813110351562e-06s
INFO | --- Analysis for linked-stockindex took 2.8542776107788086s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.26520299911499023s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.020523786544799805s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.743171691894531e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 7.3909759521484375e-06s
INFO | --- Analysis for linked-structured-product-labels took 2.881413698196411s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 7.748603820800781e-05s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.25527381896972656s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.021338462829589844s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.647804260253906e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 1.0728836059570312e-05s
INFO | --- Analysis for linked-taiwan-geo-names took 2.8073673248291016s
Availability | SPARQL endpoint availability check for Linked TCGA took 5.53131103515625e-05s
Availability | VoID file availability check for Linked TCGA took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.26569175720214844s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02034163475036621s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 8.416175842285156e-05s
Believability | Calculation of trust value for Linked TCGA took 1.2159347534179688e-05s
INFO | --- Analysis for linked-tcga took 2.8404905796051025s
Availability | SPARQL endpoint availability check for Linked User Feedback took 4.00543212890625e-05s
Availability | VoID file availability check for Linked User Feedback took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.27688026428222656s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.020350217819213867s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.4809112548828125e-05s
Believability | Calculation of trust value for Linked User Feedback took 7.3909759521484375e-06s
INFO | --- Analysis for linked-user-feedback took 2.9123072624206543s
Availability | SPARQL endpoint availability check for USPTO Patent data took 4.0531158447265625e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.2536427974700928s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.02036762237548828s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.557868957519531e-05s
Believability | Calculation of trust value for USPTO Patent data took 7.867813110351562e-06s
INFO | --- Analysis for linked-uspto-patent-data took 2.8371939659118652s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.0002760887145996094s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.2823503017425537s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.02106451988220215s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0009763240814208984s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 4.0531158447265625e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 7.3909759521484375e-06s
INFO | --- Analysis for linked-web-apis took 2.8832833766937256s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 4.0531158447265625e-05s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.00029587745666503906s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.23273682594299316s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.0517578125e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 8.106231689453125e-06s
INFO | --- Analysis for linkedarc took 2.8431203365325928s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.2443697452545166s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.020582914352416992s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.838539123535156e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 7.62939453125e-06s
INFO | --- Analysis for linkedcrowdsourceddata took 2.837261438369751s
Availability | SPARQL endpoint availability check for LinkedCT took 4.100799560546875e-05s
Availability | VoID file availability check for LinkedCT took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.25486135482788086s
Reputation | Calculation of the PageRank for LinkedCT took 0.020578622817993164s
Interlinking | Calculation of Degree of Connection for LinkedCT took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedCT took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 0.00010037422180175781s
Believability | Calculation of trust value for LinkedCT took 7.3909759521484375e-06s
INFO | --- Analysis for linkedct took 2.8800504207611084s
Availability | SPARQL endpoint availability check for LinkedGeoData took 4.00543212890625e-05s
Availability | VoID file availability check for LinkedGeoData took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.2759554386138916s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00011563301086425781s
Believability | Calculation of trust value for LinkedGeoData took 8.344650268554688e-06s
INFO | --- Analysis for linkedgeodata took 2.909512519836426s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 3.933906555175781e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.25745511054992676s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.218650817871094e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 8.344650268554688e-06s
INFO | --- Analysis for linkedgeodata-aerodromes took 2.8656115531921387s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0531136989593506s
Availability | VoID file availability check for LinkedLCCN took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.2544894218444824s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.020711660385131836s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010418891906738281s
Believability | Calculation of trust value for LinkedLCCN took 7.152557373046875e-06s
INFO | --- Analysis for linkedlccn took 3.848893165588379s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 4.601478576660156e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.2805960178375244s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.025135040283203125s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0012722015380859375s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 5.125999450683594e-05s
Believability | Calculation of trust value for LinkedMarkMail took 8.58306884765625e-06s
INFO | --- Analysis for linkedmarkmail took 2.904857873916626s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 1.2031044960021973s
Availability | VoID file availability check for Linked Movie DataBase took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.2792789936065674s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020633220672607422s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.00013256072998046875s
Believability | Calculation of trust value for Linked Movie DataBase took 7.3909759521484375e-06s
INFO | --- Analysis for linkedmdb took 4.336612701416016s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 4.1961669921875e-05s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.26320409774780273s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0207211971282959s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.557868957519531e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 7.62939453125e-06s
INFO | --- Analysis for linkedspending took 2.8401782512664795s
Availability | SPARQL endpoint availability check for LinkedStats took 4.0531158447265625e-05s
Availability | VoID file availability check for LinkedStats took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.2837851047515869s
Reputation | Calculation of the PageRank for LinkedStats took 0.020641803741455078s
Interlinking | Calculation of Degree of Connection for LinkedStats took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedStats took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 3.0517578125e-05s
Believability | Calculation of trust value for LinkedStats took 8.344650268554688e-06s
INFO | --- Analysis for linkedstats took 2.876005172729492s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 5.173683166503906e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.2747769355773926s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.02062201499938965s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.218650817871094e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 8.58306884765625e-06s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.920335531234741s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 4.1484832763671875e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.2664330005645752s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.0207216739654541s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 3.147125244140625e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 7.867813110351562e-06s
INFO | --- Analysis for linking-open-drug-data took 2.8473129272460938s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 4.0531158447265625e-05s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.00038361549377441406s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.27850341796875s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010585784912109375s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 7.62939453125e-06s
INFO | --- Analysis for linklion took 2.7668845653533936s
Availability | SPARQL endpoint availability check for Lion's Den took 4.00543212890625e-05s
Availability | VoID file availability check for Lion's Den took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.272904634475708s
Reputation | Calculation of the PageRank for Lion's Den took 0.02044844627380371s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.719329833984375e-05s
Believability | Calculation of trust value for Lion's Den took 2.1696090698242188e-05s
INFO | --- Analysis for lionsden took 2.8318285942077637s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 22.704521894454956s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.00031495094299316406s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.2748446464538574s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0007619857788085938s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 5.316734313964844e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.33514404296875e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 26.41916251182556s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 4.1484832763671875e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.2574329376220703s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.075599670410156e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 7.3909759521484375e-06s
INFO | --- Analysis for livtdm took 2.7932536602020264s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 8.225440979003906e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.2748572826385498s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.02070760726928711s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.3855438232421875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 1.1920928955078125e-05s
INFO | --- Analysis for livtdm2017 took 2.8734803199768066s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.0002789497375488281s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.2650432586669922s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 1.2159347534179688e-05s
INFO | --- Analysis for lobi took 2.8870463371276855s
Availability | SPARQL endpoint availability check for lobid-organisations took 3.9577484130859375e-05s
Availability | VoID file availability check for lobid-organisations took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.24325203895568848s
Reputation | Calculation of the PageRank for lobid-organisations took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 9.298324584960938e-05s
Believability | Calculation of trust value for lobid-organisations took 9.059906005859375e-06s
INFO | --- Analysis for lobid-organisations took 2.7384157180786133s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 4.982948303222656e-05s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.2713491916656494s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.02065134048461914s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 0.00010037422180175781s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 7.62939453125e-06s
INFO | --- Analysis for lobid-resources took 2.8852767944335938s
Availability | SPARQL endpoint availability check for Linked Open Colors took 4.00543212890625e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0002925395965576172s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.27492809295654297s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020969629287719727s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 7.200241088867188e-05s
Believability | Calculation of trust value for Linked Open Colors took 7.62939453125e-06s
INFO | --- Analysis for loc took 2.8165783882141113s
Availability | SPARQL endpoint availability check for Location Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Location Ontology took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.23778867721557617s
Reputation | Calculation of the PageRank for Location Ontology took 0.02082037925720215s
Interlinking | Calculation of Degree of Connection for Location Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Location Ontology took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 3.0279159545898438e-05s
Believability | Calculation of trust value for Location Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Location_Ontology took 2.8267152309417725s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.124641418457031e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.22957849502563477s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.02082061767578125s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.24249267578125e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 8.106231689453125e-06s
INFO | --- Analysis for locv took 2.719775915145874s
Availability | SPARQL endpoint availability check for LOD-a-lot took 0.0006225109100341797s
Availability | VoID file availability check for LOD-a-lot took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.2848386764526367s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0008482933044433594s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 3.409385681152344e-05s
Believability | Calculation of trust value for LOD-a-lot took 7.152557373046875e-06s
INFO | --- Analysis for lod-a-lot took 2.8578197956085205s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 4.029273986816406e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.2635984420776367s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.02044677734375s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0006768703460693359s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 7.3909759521484375e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 2.8218672275543213s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 4.029273986816406e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.27342867851257324s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.02044510841369629s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Open Data Web - a CKAN based linked open data repository in Taiwan took 2.7418136596679688e-05s
Believability | Calculation of trust value for Open Data Web - a CKAN based linked open data repository in Taiwan took 8.821487426757812e-06s
INFO | --- Analysis for lod-taiwan took 2.8402318954467773s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 4.076957702636719e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.26401758193969727s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.02077627182006836s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0008859634399414062s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 9.870529174804688e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.33514404296875e-05s
INFO | --- Analysis for lod2-project-wiki took 2.8734564781188965s
Availability | SPARQL endpoint availability check for LODAC BDLS took 4.100799560546875e-05s
Availability | VoID file availability check for LODAC BDLS took 0.000244140625s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.2561159133911133s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 6.914138793945312e-05s
Believability | Calculation of trust value for LODAC BDLS took 6.9141387939453125e-06s
INFO | --- Analysis for lodac-bdls took 2.7819721698760986s
Availability | SPARQL endpoint availability check for LODRussia Math took 3.933906555175781e-05s
Availability | VoID file availability check for LODRussia Math took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.2423722743988037s
Reputation | Calculation of the PageRank for LODRussia Math took 0.020855426788330078s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007786750793457031s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 3.409385681152344e-05s
Believability | Calculation of trust value for LODRussia Math took 8.106231689453125e-06s
INFO | --- Analysis for lodrussia-math took 2.8869009017944336s
Availability | SPARQL endpoint availability check for LODRussia Nano took 3.886222839355469e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.25096988677978516s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 3.0040740966796875e-05s
Believability | Calculation of trust value for LODRussia Nano took 7.152557373046875e-06s
INFO | --- Analysis for lodrussia-nano took 2.7790796756744385s
Availability | SPARQL endpoint availability check for LODStats took 5.125999450683594e-05s
Availability | VoID file availability check for LODStats took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for LODStats took 0.265425443649292s
Reputation | Calculation of the PageRank for LODStats took 0.021088361740112305s
Interlinking | Calculation of Degree of Connection for LODStats took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODStats took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.0279159545898438e-05s
Believability | Calculation of trust value for LODStats took 7.867813110351562e-06s
INFO | --- Analysis for lodstats took 2.7961483001708984s
Availability | SPARQL endpoint availability check for LODUM took 4.029273986816406e-05s
Availability | VoID file availability check for LODUM took 0.0003638267517089844s
Completeness | Calculation of interlinking completeness for LODUM took 0.26281213760375977s
Reputation | Calculation of the PageRank for LODUM took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for LODUM took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.0517578125e-05s
Believability | Calculation of trust value for LODUM took 7.3909759521484375e-06s
INFO | --- Analysis for lodum took 2.8677749633789062s
Availability | SPARQL endpoint availability check for lofd took 4.1484832763671875e-05s
Availability | VoID file availability check for lofd took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for lofd took 0.2411036491394043s
Reputation | Calculation of the PageRank for lofd took 0.021144628524780273s
Interlinking | Calculation of Degree of Connection for lofd took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for lofd took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for lofd took 2.9802322387695312e-05s
Believability | Calculation of trust value for lofd took 1.2159347534179688e-05s
INFO | --- Analysis for lofd took 2.8482537269592285s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 4.100799560546875e-05s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.24298763275146484s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.020405054092407227s
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.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 4.5299530029296875e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 7.62939453125e-06s
INFO | --- Analysis for loius took 2.826279401779175s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 5.173683166503906e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.2527034282684326s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.8848648071289062e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 7.152557373046875e-06s
INFO | --- Analysis for loius-linking-italian-university-statistics took 2.743543863296509s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 4.029273986816406e-05s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.24683642387390137s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 4.863739013671875e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 6.67572021484375e-06s
INFO | --- Analysis for london-gazette took 2.81532883644104s
Availability | SPARQL endpoint availability check for Weather Stations took 3.9577484130859375e-05s
Availability | VoID file availability check for Weather Stations took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.25217485427856445s
Reputation | Calculation of the PageRank for Weather Stations took 0.02041459083557129s
Interlinking | Calculation of Degree of Connection for Weather Stations took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007348060607910156s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 7.62939453125e-05s
Believability | Calculation of trust value for Weather Stations took 6.4373016357421875e-06s
INFO | --- Analysis for los_metar took 2.8360893726348877s
Availability | SPARQL endpoint availability check for Lotico took 4.029273986816406e-05s
Availability | VoID file availability check for Lotico took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Lotico took 0.25574254989624023s
Reputation | Calculation of the PageRank for Lotico took 0.020369768142700195s
Interlinking | Calculation of Degree of Connection for Lotico took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Lotico took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Lotico took 7.653236389160156e-05s
Believability | Calculation of trust value for Lotico took 7.152557373046875e-06s
INFO | --- Analysis for lotico took 2.8432390689849854s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 3.933906555175781e-05s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.25919151306152344s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.02057647705078125s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 3.0279159545898438e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 7.152557373046875e-06s
INFO | --- Analysis for lower-layer-super-output-areas took 2.829127550125122s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.291534423828125e-05s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.25671911239624023s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.020692110061645508s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0007467269897460938s
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.811981201171875e-05s
INFO | --- Analysis for LPIS_(Poland) took 2.945920944213867s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 5.4836273193359375e-05s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.24221181869506836s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.020659923553466797s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.4332275390625e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 6.4373016357421875e-06s
INFO | --- Analysis for LPIS_Czech_Republic took 2.878265380859375s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 3.9577484130859375e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.25486278533935547s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007772445678710938s
Interlinking | Calculation of Clustering coefficient for A collection of Authors for LREC2014 and related Workshops took 3.0279159545898438e-05s
Believability | Calculation of trust value for A collection of Authors for LREC2014 and related Workshops took 6.67572021484375e-06s
INFO | --- Analysis for lremap-auth took 2.8064489364624023s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 6.4849853515625e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.2684509754180908s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02115345001220703s
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.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 2.9325485229492188e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.0013580322265625e-05s
INFO | --- Analysis for lremap-conf took 2.843538999557495s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 4.2438507080078125e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.26357126235961914s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.020113229751586914s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 2.7418136596679688e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 7.3909759521484375e-06s
INFO | --- Analysis for lremap-ri took 2.8709235191345215s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 4.100799560546875e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.00032782554626464844s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.2779660224914551s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020941972732543945s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.2901763916015625e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 1.3113021850585938e-05s
INFO | --- Analysis for lremap-sub took 2.8167238235473633s
Availability | SPARQL endpoint availability check for LSQ took 4.076957702636719e-05s
Availability | VoID file availability check for LSQ took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for LSQ took 0.2671961784362793s
Reputation | Calculation of the PageRank for LSQ took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for LSQ took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.0517578125e-05s
Believability | Calculation of trust value for LSQ took 7.152557373046875e-06s
INFO | --- Analysis for lsq took 2.8253207206726074s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6831235885620117s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.24604487419128418s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.02069544792175293s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.482269287109375e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for LucaniPharsalia took 3.983565330505371s
Availability | SPARQL endpoint availability check for Linked rules took 4.172325134277344e-05s
Availability | VoID file availability check for Linked rules took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Linked rules took 0.25727391242980957s
Reputation | Calculation of the PageRank for Linked rules took 0.020365476608276367s
Interlinking | Calculation of Degree of Connection for Linked rules took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked rules took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linked rules took 3.0040740966796875e-05s
Believability | Calculation of trust value for Linked rules took 1.2159347534179688e-05s
INFO | --- Analysis for Luminaires_senlis took 2.8278110027313232s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.2438507080078125e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.2634446620941162s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 2.7179718017578125e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 6.4373016357421875e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 2.804532051086426s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 4.744529724121094e-05s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.2678403854370117s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020511150360107422s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0007486343383789062s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 3.170967102050781e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 7.3909759521484375e-06s
INFO | --- Analysis for makg took 2.8373935222625732s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 3.981590270996094e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.0006604194641113281s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.2653522491455078s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.020597219467163086s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 3.24249267578125e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 6.9141387939453125e-06s
INFO | --- Analysis for manchester-university-reading-lists took 2.8385772705078125s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 3.933906555175781e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.24581217765808105s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.3909759521484375e-06s
INFO | --- Analysis for manish took 2.802417039871216s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.506111145019531e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.2754948139190674s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02173638343811035s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0009012222290039062s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 3.361701965332031e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 6.9141387939453125e-06s
INFO | --- Analysis for mapa-referencia-bogota took 2.820824146270752s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 4.029273986816406e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.23492813110351562s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020575284957885742s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.86102294921875e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 7.3909759521484375e-06s
INFO | --- Analysis for mapa-referencia-bogota-dc took 2.7751142978668213s
Availability | SPARQL endpoint availability check for MARC Codes List took 5.245208740234375e-05s
Availability | VoID file availability check for MARC Codes List took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.2778472900390625s
Reputation | Calculation of the PageRank for MARC Codes List took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00011610984802246094s
Believability | Calculation of trust value for MARC Codes List took 7.62939453125e-06s
INFO | --- Analysis for marc-codes took 2.8730578422546387s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.315376281738281e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.2603936195373535s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020474672317504883s
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.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 3.600120544433594e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for masc took 2.8657021522521973s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 4.0531158447265625e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.0004990100860595703s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.2692606449127197s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.62396240234375e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 6.9141387939453125e-06s
INFO | --- Analysis for masc-bn-nif took 2.9000089168548584s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.5708754062652588s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.271806001663208s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020281314849853516s
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.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 2.9087066650390625e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 6.67572021484375e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 4.474416255950928s
Availability | SPARQL endpoint availability check for medline took 4.1484832763671875e-05s
Availability | VoID file availability check for medline took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for medline took 0.24781227111816406s
Reputation | Calculation of the PageRank for medline took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for medline took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for medline took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for medline took 3.337860107421875e-05s
Believability | Calculation of trust value for medline took 7.3909759521484375e-06s
INFO | --- Analysis for medline took 2.8339624404907227s
Availability | SPARQL endpoint availability check for mEducator: Linked Educational Resources took 4.029273986816406e-05s
Availability | VoID file availability check for mEducator: Linked Educational Resources took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.2541491985321045s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.604194641113281e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 7.152557373046875e-06s
INFO | --- Analysis for meducator took 2.913259983062744s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 4.029273986816406e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.25705504417419434s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.02057790756225586s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 2.765655517578125e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 7.62939453125e-06s
INFO | --- Analysis for mesh-finnish took 2.887566566467285s
Availability | SPARQL endpoint availability check for MeSH headings took 4.0531158447265625e-05s
Availability | VoID file availability check for MeSH headings took 0.0002346038818359375s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.359283447265625s
Reputation | Calculation of the PageRank for MeSH headings took 0.020519018173217773s
Interlinking | Calculation of Degree of Connection for MeSH headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MeSH headings took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 2.9325485229492188e-05s
Believability | Calculation of trust value for MeSH headings took 6.67572021484375e-06s
INFO | --- Analysis for mesh_headings took 3.051323652267456s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 5.2928924560546875e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.25934267044067383s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02051687240600586s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0008146762847900391s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 3.24249267578125e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 7.62939453125e-06s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 2.87325382232666s
Availability | SPARQL endpoint availability check for MeSH pairs took 3.933906555175781e-05s
Availability | VoID file availability check for MeSH pairs took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.2648956775665283s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020336151123046875s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.8848648071289062e-05s
Believability | Calculation of trust value for MeSH pairs took 7.152557373046875e-06s
INFO | --- Analysis for mesh_pairs took 2.895397186279297s
Availability | SPARQL endpoint availability check for MeSH titles took 3.910064697265625e-05s
Availability | VoID file availability check for MeSH titles took 0.0005483627319335938s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.28086161613464355s
Reputation | Calculation of the PageRank for MeSH titles took 0.020413875579833984s
Interlinking | Calculation of Degree of Connection for MeSH titles took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MeSH titles took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.6941299438476562e-05s
Believability | Calculation of trust value for MeSH titles took 1.049041748046875e-05s
INFO | --- Analysis for mesh_titles took 2.955402135848999s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 4.124641418457031e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.2640976905822754s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.020246267318725586s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům z psp.cz took 2.9802322387695312e-05s
Believability | Calculation of trust value for Metadata k zákonům z psp.cz took 6.9141387939453125e-06s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 2.8612101078033447s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 4.315376281738281e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.2950918674468994s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.020381689071655273s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 3.0517578125e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.1682510375976562e-05s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.8982021808624268s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 3.886222839355469e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.29416608810424805s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.0208282470703125s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 7.033348083496094e-05s
Believability | Calculation of trust value for MetaShare metadata model took 7.3909759521484375e-06s
INFO | --- Analysis for metashare took 2.8537256717681885s
Availability | SPARQL endpoint availability check for MExiCo took 4.0531158447265625e-05s
Availability | VoID file availability check for MExiCo took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for MExiCo took 0.2593955993652344s
Reputation | Calculation of the PageRank for MExiCo took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for MExiCo took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MExiCo took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for MExiCo took 4.38690185546875e-05s
Believability | Calculation of trust value for MExiCo took 7.152557373046875e-06s
INFO | --- Analysis for mexico took 2.8425886631011963s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for Coronavirus dataset took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.27745985984802246s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.020327091217041016s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 4.7206878662109375e-05s
Believability | Calculation of trust value for Coronavirus dataset took 1.0967254638671875e-05s
INFO | --- Analysis for micro-coronavirus took 2.833069324493408s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 5.245208740234375e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.24820947647094727s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.00010204315185546875s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 7.867813110351562e-06s
INFO | --- Analysis for miguiadeviajes-gnoss took 2.7771553993225098s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 4.9591064453125e-05s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.25397562980651855s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011277198791503906s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 6.747245788574219e-05s
INFO | --- Analysis for mismuseos-gnoss took 2.858792543411255s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.076957702636719e-05s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.25604677200317383s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.482269287109375e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 7.867813110351562e-06s
INFO | --- Analysis for mlsa took 2.896697521209717s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 4.315376281738281e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.2492055892944336s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.9802322387695312e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 9.298324584960938e-06s
INFO | --- Analysis for model took 2.793309211730957s
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.649162292480469e-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.0003943443298339844s
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.27807021141052246s
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.020491361618041992s
Interlinking | Calculation of Degree of Connection for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 2.9325485229492188e-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 7.867813110351562e-06s
INFO | --- Analysis for model1 took 2.916414260864258s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 4.0531158447265625e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.23952531814575195s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 2.6941299438476562e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 7.152557373046875e-06s
INFO | --- Analysis for mond took 2.833547592163086s
Availability | SPARQL endpoint availability check for MONDIS took 3.838539123535156e-05s
Availability | VoID file availability check for MONDIS took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for MONDIS took 0.2466268539428711s
Reputation | Calculation of the PageRank for MONDIS took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0009477138519287109s
Interlinking | Calculation of Clustering coefficient for MONDIS took 3.457069396972656e-05s
Believability | Calculation of trust value for MONDIS took 7.3909759521484375e-06s
INFO | --- Analysis for mondis took 2.8150365352630615s
Availability | SPARQL endpoint availability check for Monumentos took 4.0531158447265625e-05s
Availability | VoID file availability check for Monumentos took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for Monumentos took 0.25260138511657715s
Reputation | Calculation of the PageRank for Monumentos took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for Monumentos took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Monumentos took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.8371810913085938e-05s
Believability | Calculation of trust value for Monumentos took 7.152557373046875e-06s
INFO | --- Analysis for monumentos-zaragoza took 2.7795519828796387s
Availability | SPARQL endpoint availability check for MORElab took 3.9577484130859375e-05s
Availability | VoID file availability check for MORElab took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for MORElab took 0.27750515937805176s
Reputation | Calculation of the PageRank for MORElab took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for MORElab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for MORElab took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.368492126464844e-05s
Believability | Calculation of trust value for MORElab took 7.3909759521484375e-06s
INFO | --- Analysis for morelab took 2.8557815551757812s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 4.124641418457031e-05s
Availability | VoID file availability check for Mathematics Subject Classification took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.2604868412017822s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.020550966262817383s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.368492126464844e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 7.152557373046875e-06s
INFO | --- Analysis for msc took 2.812227487564087s
Availability | SPARQL endpoint availability check for Multext-East took 4.00543212890625e-05s
Availability | VoID file availability check for Multext-East took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Multext-East took 0.2554900646209717s
Reputation | Calculation of the PageRank for Multext-East took 0.020671844482421875s
Interlinking | Calculation of Degree of Connection for Multext-East took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Multext-East took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.457069396972656e-05s
Believability | Calculation of trust value for Multext-East took 8.106231689453125e-06s
INFO | --- Analysis for multext-east took 2.844099283218384s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.076957702636719e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0003325939178466797s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.2539830207824707s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 4.00543212890625e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 7.3909759521484375e-06s
INFO | --- Analysis for multilingualeulaw took 2.8743810653686523s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.1484832763671875e-05s
Availability | VoID file availability check for Multimedia Lab took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.24996232986450195s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.028171300888061523s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 2.574920654296875e-05s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0018765926361083984s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 5.316734313964844e-05s
Believability | Calculation of trust value for Multimedia Lab took 6.67572021484375e-06s
INFO | --- Analysis for multimedia-lab took 2.823876142501831s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 4.00543212890625e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.23963403701782227s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.02062058448791504s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 3.1948089599609375e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 8.821487426757812e-06s
INFO | --- Analysis for munich-offener-haushalt took 2.8107006549835205s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.734473705291748s
Availability | VoID file availability check for Muninn World War I took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.2489166259765625s
Reputation | Calculation of the PageRank for Muninn World War I took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 8.082389831542969e-05s
Believability | Calculation of trust value for Muninn World War I took 6.9141387939453125e-06s
INFO | --- Analysis for muninn-world-war-i took 6.347571134567261s
Availability | SPARQL endpoint availability check for Musei Italiani took 4.029273986816406e-05s
Availability | VoID file availability check for Musei Italiani took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.2588973045349121s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020854473114013672s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 3.170967102050781e-05s
Believability | Calculation of trust value for Musei Italiani took 1.2159347534179688e-05s
INFO | --- Analysis for musei-italiani took 2.865931510925293s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 5.745887756347656e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.2789590358734131s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.02064681053161621s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010657310485839844s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.344650268554688e-06s
INFO | --- Analysis for museosespania-gnoss took 2.9163923263549805s
Availability | SPARQL endpoint availability check for Italian Museums took 1.3678715229034424s
Availability | VoID file availability check for Italian Museums took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.26220154762268066s
Reputation | Calculation of the PageRank for Italian Museums took 0.02338719367980957s
Interlinking | Calculation of Degree of Connection for Italian Museums took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Italian Museums took 0.0011944770812988281s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 0.00010418891906738281s
Believability | Calculation of trust value for Italian Museums took 7.62939453125e-06s
INFO | --- Analysis for museums-in-italy took 4.306545972824097s
Availability | SPARQL endpoint availability check for MusicBrainz took 3.981590270996094e-05s
Availability | VoID file availability check for MusicBrainz took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.2669098377227783s
Reputation | Calculation of the PageRank for MusicBrainz took 0.02038097381591797s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 2.8848648071289062e-05s
Believability | Calculation of trust value for MusicBrainz took 7.3909759521484375e-06s
INFO | --- Analysis for musicbrainz_ took 2.8374619483947754s
Availability | SPARQL endpoint availability check for MusicNet Codex took 4.076957702636719e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0002913475036621094s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.27660036087036133s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 3.0994415283203125e-05s
Believability | Calculation of trust value for MusicNet Codex took 8.344650268554688e-06s
INFO | --- Analysis for musicnet_codex took 2.8003063201904297s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7229087352752686s
Availability | VoID file availability check for Muziekweb took 0.000308990478515625s
Extra | Recovery of all triples for Muziekweb took 1.002448320388794s
Performance | Total latancy measurement for Muziekweb took 1.5343048572540283s
Amount of data | Number of triples check for Muziekweb took 0.3106722831726074s
Interoperability | New terms check for Muziekweb took 1.7424378395080566s
Versatility | Languages check for Muziekweb took 0.3058509826660156s
Interpretability | Number of blank nodes check for Muziekweb took 0.29974889755249023s
Interpretability | RDF structures check for Muziekweb took 0.34693479537963867s
Versatility | Serialization formats check for Muziekweb took 0.31070542335510254s
Availability | RDF dump link check for Muziekweb took 0.3189096450805664s
License | MR license check for Muziekweb took 0.3268740177154541s
License | HR license check for Muziekweb took 0.3037586212158203s
Amount of data | Number of property check for Muziekweb took 0.34816527366638184s
Understandability | Number of label check for Muziekweb took 0.37914204597473145s
Understandability | URI regex check for Muziekweb took 0.6372735500335693s
Understandability | Vocabs check for Muziekweb took 0.2988467216491699s
Verifiability | Authors check for Muziekweb took 0.3015098571777344s
Verifiability | Publishers check for Muziekweb took 0.2870628833770752s
Performance | Throughput check for Muziekweb took 12.245500087738037s
Amount of data | Check the number of entities for Muziekweb took 7.843971252441406e-05s
Verifiability | Contribs. check for Muziekweb took 0.332369327545166s
Interlinking | sameAs chians check for Muziekweb took 0.3136861324310303s
Interlinking | skos check for Muziekweb took 0.3328547477722168s
Interlinking | skos check for Muziekweb took 0.3207108974456787s
Timeliness | dataset update frequency check for Muziekweb took 0.3179306983947754s
Currency | Creation date check for Muziekweb took 0.629448652267456s
Currency | Modification date check for Muziekweb took 0.6003084182739258s
Rep.Conc. | URIs length for Muziekweb took 1.0281329154968262s
Interoperability | New vocabularies check for Muziekweb took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.2938053607940674s
Accuracy | Check Functional Property for Muziekweb took 0.2892003059387207s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.2993035316467285s
Accuracy | Check Empty annotation labels for Muziekweb took 0.6375584602355957s
Accuracy | Check White space in annotation for Muziekweb took 0.02765488624572754s
Accuracy | Check Datatype consistency for Muziekweb took 0.028602123260498047s
Consistency | Disjoint class check for Muziekweb took 0.29814720153808594s
Consistency | Check Misplaced properties for Muziekweb took 0.6055402755737305s
Consistency | Check Ontology hijacking for Muziekweb took 1.9697775840759277s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.3879778385162354s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6833319664001465s
Conciseness | Check Extensional conciseness for Muziekweb took 0.03521156311035156s
Conciseness | Check Intensional conciseness for Muziekweb took 0.3093078136444092s
Security | Sign check for Muziekweb took 0.3172035217285156s
Availability | Check URIs Dereferenciability for Muziekweb took 1860.8957183361053s
Completeness | Calculation of interlinking completeness for Muziekweb took 1.5506746768951416s
Reputation | Calculation of the PageRank for Muziekweb took 0.02139878273010254s
Interlinking | Calculation of Degree of Connection for Muziekweb took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Muziekweb took 0.0008001327514648438s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 0.00018286705017089844s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.1920928955078125e-06s
Believability | Calculation of trust value for Muziekweb took 8.106231689453125e-06s
INFO | --- Analysis for muziekweb took 1920.6212794780731s
Availability | SPARQL endpoint availability check for myExperiment took 4.172325134277344e-05s
Availability | VoID file availability check for myExperiment took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for myExperiment took 0.2621138095855713s
Reputation | Calculation of the PageRank for myExperiment took 0.02075481414794922s
Interlinking | Calculation of Degree of Connection for myExperiment took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for myExperiment took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for myExperiment took 0.00010538101196289062s
Believability | Calculation of trust value for myExperiment took 7.152557373046875e-06s
INFO | --- Analysis for my-experiment took 3.247274160385132s
Availability | SPARQL endpoint availability check for My Family Lineage took 3.981590270996094e-05s
Availability | VoID file availability check for My Family Lineage took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.2793123722076416s
Reputation | Calculation of the PageRank for My Family Lineage took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.463859558105469e-05s
Believability | Calculation of trust value for My Family Lineage took 7.62939453125e-06s
INFO | --- Analysis for my-family-lineage took 2.9321253299713135s
Availability | SPARQL endpoint availability check for My ontology test took 4.57763671875e-05s
Availability | VoID file availability check for My ontology test took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for My ontology test took 0.2636563777923584s
Reputation | Calculation of the PageRank for My ontology test took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.0994415283203125e-05s
Believability | Calculation of trust value for My ontology test took 8.106231689453125e-06s
INFO | --- Analysis for myontologytest took 3.2801105976104736s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 4.0531158447265625e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.23851919174194336s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.02080392837524414s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 0.00010347366333007812s
Believability | Calculation of trust value for myopenlink dataspaces took 7.62939453125e-06s
INFO | --- Analysis for myopenlink-dataspaces took 2.867917537689209s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 0.00011610984802246094s
Availability | VoID file availability check for N-Lex as Linked Data took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.26708388328552246s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0006792545318603516s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.437301635742188e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 1.2159347534179688e-05s
INFO | --- Analysis for n-lex-as-linked-data took 2.8706352710723877s
Availability | SPARQL endpoint availability check for NAICS 2007 took 5.507469177246094e-05s
Availability | VoID file availability check for NAICS 2007 took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.257627010345459s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.020761489868164062s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.62396240234375e-05s
Believability | Calculation of trust value for NAICS 2007 took 7.152557373046875e-06s
INFO | --- Analysis for naics-2007 took 2.816533327102661s
Availability | SPARQL endpoint availability check for NAICS 2012 took 4.029273986816406e-05s
Availability | VoID file availability check for NAICS 2012 took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.24513888359069824s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.020533084869384766s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.6253204345703125e-05s
Believability | Calculation of trust value for NAICS 2012 took 7.152557373046875e-06s
INFO | --- Analysis for naics-2012 took 2.8049185276031494s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 5.507469177246094e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.28198695182800293s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for National Agricultural Library Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Agricultural Library Thesaurus took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 4.863739013671875e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for nalt took 2.8875691890716553s
Availability | SPARQL endpoint availability check for Usernames  took 4.220008850097656e-05s
Availability | VoID file availability check for Usernames  took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Usernames  took 0.27600789070129395s
Reputation | Calculation of the PageRank for Usernames  took 0.020827293395996094s
Interlinking | Calculation of Degree of Connection for Usernames  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Usernames  took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.170967102050781e-05s
Believability | Calculation of trust value for Usernames  took 7.62939453125e-06s
INFO | --- Analysis for Names took 2.8684146404266357s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 5.626678466796875e-05s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.27229762077331543s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.020579099655151367s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.650520324707031e-05s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 1.239776611328125e-05s
INFO | --- Analysis for national-diet-library-authorities took 2.876462459564209s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 4.267692565917969e-05s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.280658483505249s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 5.7697296142578125e-05s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 8.106231689453125e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 2.896627902984619s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.007065773010254s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.26680636405944824s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.021329402923583984s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.291534423828125e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 5.7220458984375e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 4.623739242553711s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 4.220008850097656e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.2650020122528076s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020745515823364258s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.176399230957031e-05s
Believability | Calculation of trust value for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 7.867813110351562e-06s
INFO | --- Analysis for Naturopathy took 2.843344211578369s
Availability | SPARQL endpoint availability check for Naturopathy took 4.076957702636719e-05s
Availability | VoID file availability check for Naturopathy took 0.000942230224609375s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.24373197555541992s
Reputation | Calculation of the PageRank for Naturopathy took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for Naturopathy took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 3.0994415283203125e-05s
Believability | Calculation of trust value for Naturopathy took 6.198883056640625e-06s
INFO | --- Analysis for naturopathy2 took 2.8174540996551514s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.24546194076538086s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02066969871520996s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.361701965332031e-05s
Believability | Calculation of trust value for NCI Thesaurus took 6.67572021484375e-06s
INFO | --- Analysis for nci-thesaurus took 2.794602870941162s
Availability | SPARQL endpoint availability check for COVID-19 Data took 4.1961669921875e-05s
Availability | VoID file availability check for COVID-19 Data took 0.0002846717834472656s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.26840710639953613s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 2.9325485229492188e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.867813110351562e-06s
INFO | --- Analysis for NCMI-COVID-19 took 2.7999329566955566s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 4.029273986816406e-05s
Availability | VoID file availability check for NCMI-COVID-19 took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.2530965805053711s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.2159347534179688e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 7.867813110351562e-06s
INFO | --- Analysis for NCMICOVID-19 took 2.921600580215454s
Availability | SPARQL endpoint availability check for NDF-RT took 4.315376281738281e-05s
Availability | VoID file availability check for NDF-RT took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.2546689510345459s
Reputation | Calculation of the PageRank for NDF-RT took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for NDF-RT took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NDF-RT took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.170967102050781e-05s
Believability | Calculation of trust value for NDF-RT took 7.867813110351562e-06s
INFO | --- Analysis for ndf-rt took 2.854100227355957s
Availability | SPARQL endpoint availability check for Near took 4.00543212890625e-05s
Availability | VoID file availability check for Near took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Near took 0.27051687240600586s
Reputation | Calculation of the PageRank for Near took 0.021752119064331055s
Interlinking | Calculation of Degree of Connection for Near took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Near took 0.0008451938629150391s
Interlinking | Calculation of Clustering coefficient for Near took 0.0001068115234375s
Believability | Calculation of trust value for Near took 7.62939453125e-06s
INFO | --- Analysis for near took 2.911259174346924s
Availability | SPARQL endpoint availability check for Neel took 5.507469177246094e-05s
Availability | VoID file availability check for Neel took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Neel took 0.25137948989868164s
Reputation | Calculation of the PageRank for Neel took 0.020302534103393555s
Interlinking | Calculation of Degree of Connection for Neel took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neel took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Neel took 3.075599670410156e-05s
Believability | Calculation of trust value for Neel took 7.867813110351562e-06s
INFO | --- Analysis for neel took 2.8162050247192383s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 4.267692565917969e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.2417762279510498s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020604848861694336s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.0040740966796875e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 8.344650268554688e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.7873575687408447s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.029273986816406e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.279325008392334s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.02047109603881836s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.123283386230469e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 7.62939453125e-06s
INFO | --- Analysis for neurolex-wiki took 2.8576691150665283s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.291534423828125e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.23520207405090332s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020729780197143555s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.696846008300781e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.3113021850585938e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 2.848557949066162s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 4.029273986816406e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.25457048416137695s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.02073836326599121s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.67572021484375e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 7.3909759521484375e-06s
INFO | --- Analysis for news-100-nif-ner-corpus took 2.854234218597412s
Availability | SPARQL endpoint availability check for Newsweek took 4.076957702636719e-05s
Availability | VoID file availability check for Newsweek took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Newsweek took 0.26516103744506836s
Reputation | Calculation of the PageRank for Newsweek took 0.02069401741027832s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Newsweek took 3.123283386230469e-05s
Believability | Calculation of trust value for Newsweek took 7.62939453125e-06s
INFO | --- Analysis for newsweek took 2.825979709625244s
Availability | SPARQL endpoint availability check for neXtProt took 4.1484832763671875e-05s
Availability | VoID file availability check for neXtProt took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for neXtProt took 0.2647824287414551s
Reputation | Calculation of the PageRank for neXtProt took 0.02060246467590332s
Interlinking | Calculation of Degree of Connection for neXtProt took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for neXtProt took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.7670135498046875e-05s
Believability | Calculation of trust value for neXtProt took 7.867813110351562e-06s
INFO | --- Analysis for nextprot took 2.7947423458099365s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.1484832763671875e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.25588107109069824s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.020773887634277344s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010156631469726562s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 7.152557373046875e-06s
INFO | --- Analysis for nextweb-gnoss took 2.823380947113037s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 4.029273986816406e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.2541992664337158s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 8.630752563476562e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 8.821487426757812e-06s
INFO | --- Analysis for nhs-jargon took 2.878664255142212s
Availability | SPARQL endpoint availability check for NIT Patna took 4.00543212890625e-05s
Availability | VoID file availability check for NIT Patna took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.25093984603881836s
Reputation | Calculation of the PageRank for NIT Patna took 0.020787715911865234s
Interlinking | Calculation of Degree of Connection for NIT Patna took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.937980651855469e-05s
Believability | Calculation of trust value for NIT Patna took 8.106231689453125e-06s
INFO | --- Analysis for NITP took 2.8144612312316895s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 5.125999450683594e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.2705819606781006s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.695487976074219e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 7.867813110351562e-06s
INFO | --- Analysis for nlm_2007_mesh took 2.8745779991149902s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.553794860839844e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.2570974826812744s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for National Library of Russia BibCore Dataset took 7.3909759521484375e-06s
INFO | --- Analysis for nlr-dataset-mod took 2.7794349193573s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 4.100799560546875e-05s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.27011609077453613s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020936012268066406s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 9.059906005859375e-06s
INFO | --- Analysis for NLW took 2.8522913455963135s
Availability | SPARQL endpoint availability check for Nobel Prizes took 4.315376281738281e-05s
Availability | VoID file availability check for Nobel Prizes took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.2655506134033203s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02044963836669922s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 8.96453857421875e-05s
Believability | Calculation of trust value for Nobel Prizes took 7.3909759521484375e-06s
INFO | --- Analysis for nobelprizes took 2.9074957370758057s
Availability | SPARQL endpoint availability check for NoiPA took 4.029273986816406e-05s
Availability | VoID file availability check for NoiPA took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for NoiPA took 0.26268601417541504s
Reputation | Calculation of the PageRank for NoiPA took 0.020740509033203125s
Interlinking | Calculation of Degree of Connection for NoiPA took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NoiPA took 0.0007734298706054688s
Interlinking | Calculation of Clustering coefficient for NoiPA took 3.1948089599609375e-05s
Believability | Calculation of trust value for NoiPA took 6.9141387939453125e-06s
INFO | --- Analysis for NoiPA took 2.905829906463623s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 5.282761335372925s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0002911090850830078s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.27365684509277344s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.020973682403564453s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.1552734375e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.1920928955078125e-05s
INFO | --- Analysis for nom took 10.580211639404297s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 4.792213439941406e-05s
Availability | VoID file availability check for Nomenclator Asturias took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.2490992546081543s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.020233154296875s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.867813110351562e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 7.3909759521484375e-06s
INFO | --- Analysis for nomenclator-asturias took 2.8151650428771973s
Availability | SPARQL endpoint availability check for nomisma took 4.124641418457031e-05s
Availability | VoID file availability check for nomisma took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for nomisma took 0.25101542472839355s
Reputation | Calculation of the PageRank for nomisma took 0.020596981048583984s
Interlinking | Calculation of Degree of Connection for nomisma took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for nomisma took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for nomisma took 3.0279159545898438e-05s
Believability | Calculation of trust value for nomisma took 8.344650268554688e-06s
INFO | --- Analysis for nomisma took 2.8300843238830566s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.3627920150756836s
Availability | VoID file availability check for Nomisma.org  took 0.00026917457580566406s
Extra | Recovery of all triples for Nomisma.org  took 283.2344193458557s
Performance | Total latancy measurement for Nomisma.org  took 1.3752069473266602s
Amount of data | Number of triples check for Nomisma.org  took 39.17914915084839s
Interoperability | New terms check for Nomisma.org  took 7.408772706985474s
Versatility | Languages check for Nomisma.org  took 94.19515776634216s
Interpretability | Number of blank nodes check for Nomisma.org  took 36.11375641822815s
Security | Check HTTPS for Nomisma.org  took 0.6481921672821045s
Interpretability | RDF structures check for Nomisma.org  took 0.2744112014770508s
Versatility | Serialization formats check for Nomisma.org  took 0.27350330352783203s
Availability | RDF dump link check for Nomisma.org  took 1090.3238670825958s
License | MR license check for Nomisma.org  took 0.30739378929138184s
License | HR license check for Nomisma.org  took 55.023030042648315s
Amount of data | Number of property check for Nomisma.org  took 0.29048609733581543s
Understandability | Number of label check for Nomisma.org  took 6.05157470703125s
Understandability | URI regex check for Nomisma.org  took 0.5515618324279785s
Understandability | Vocabs check for Nomisma.org  took 0.2812540531158447s
Verifiability | Authors check for Nomisma.org  took 0.29084157943725586s
Verifiability | Publishers check for Nomisma.org  took 0.29604005813598633s
Performance | Throughput check for Nomisma.org  took 11.080982208251953s
Amount of data | Check the number of entities for Nomisma.org  took 63.43913698196411s
Verifiability | Contribs. check for Nomisma.org  took 0.2985086441040039s
Interlinking | sameAs chians check for Nomisma.org  took 0.27437663078308105s
Interlinking | skos check for Nomisma.org  took 0.9689931869506836s
Interlinking | skos check for Nomisma.org  took 0.4474141597747803s
Timeliness | dataset update frequency check for Nomisma.org  took 0.27396583557128906s
Currency | Creation date check for Nomisma.org  took 0.5794920921325684s
Currency | Modification date check for Nomisma.org  took 0.2954113483428955s
Rep.Conc. | URIs length for Nomisma.org  took 124.53674817085266s
Interoperability | New vocabularies check for Nomisma.org  took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.2834014892578125s
Accuracy | Check Functional Property for Nomisma.org  took 0.27541232109069824s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.2870829105377197s
Accuracy | Check Empty annotation labels for Nomisma.org  took 73.78586196899414s
Accuracy | Check White space in annotation for Nomisma.org  took 2.6979293823242188s
Accuracy | Check Datatype consistency for Nomisma.org  took 5.327116012573242s
Consistency | Disjoint class check for Nomisma.org  took 0.26439642906188965s
Consistency | Check Misplaced properties for Nomisma.org  took 26.09727168083191s
Consistency | Check Ontology hijacking for Nomisma.org  took 79.5066249370575s
Consistency | Check Invalid usage of undefined classes for Nomisma.org  took 2.076418876647949s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 28.0948383808136s
Conciseness | Check Extensional conciseness for Nomisma.org  took 2.779475450515747s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.28895068168640137s
Security | Sign check for Nomisma.org  took 0.28089284896850586s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2043.4975962638855s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 1.0673038959503174s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.022779226303100586s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 0.00017452239990234375s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 8.821487426757812e-06s
Believability | Calculation of trust value for Nomisma.org  took 7.152557373046875e-06s
INFO | --- Analysis for nomisma_org took 7677.85707950592s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 4.076957702636719e-05s
Availability | VoID file availability check for Curriculum Vitae took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.2879757881164551s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.000820159912109375s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 4.076957702636719e-05s
Believability | Calculation of trust value for Curriculum Vitae took 8.106231689453125e-06s
INFO | --- Analysis for Nordine_Bittich took 4.653067350387573s
Availability | SPARQL endpoint availability check for NorPark took 3.981590270996094e-05s
Availability | VoID file availability check for NorPark took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for NorPark took 0.266834020614624s
Reputation | Calculation of the PageRank for NorPark took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for NorPark took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NorPark took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.291534423828125e-05s
Believability | Calculation of trust value for NorPark took 7.867813110351562e-06s
INFO | --- Analysis for norpark took 2.7969748973846436s
Availability | SPARQL endpoint availability check for Parking Dataset took 5.6743621826171875e-05s
Availability | VoID file availability check for Parking Dataset took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.262148380279541s
Reputation | Calculation of the PageRank for Parking Dataset took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.100799560546875e-05s
Believability | Calculation of trust value for Parking Dataset took 1.3589859008789062e-05s
INFO | --- Analysis for norpark2 took 2.8716254234313965s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 5.8650970458984375e-05s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.2691645622253418s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.020398378372192383s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0010151863098144531s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.457069396972656e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 7.867813110351562e-06s
INFO | --- Analysis for Norway_Fishery_ took 2.8501791954040527s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 4.172325134277344e-05s
Availability | VoID file availability check for Norwegian geo-divisions took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.26168394088745117s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020679235458374023s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.6253204345703125e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 8.106231689453125e-06s
INFO | --- Analysis for norwegian-geo-divisions took 2.778261184692383s
Availability | SPARQL endpoint availability check for NorwegianSoE took 4.0531158447265625e-05s
Availability | VoID file availability check for NorwegianSoE took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.27786898612976074s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 3.075599670410156e-05s
Believability | Calculation of trust value for NorwegianSoE took 1.2874603271484375e-05s
INFO | --- Analysis for norwegiansoe took 2.8631680011749268s
Availability | SPARQL endpoint availability check for NITP took 4.100799560546875e-05s
Availability | VoID file availability check for NITP took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for NITP took 0.2694065570831299s
Reputation | Calculation of the PageRank for NITP took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for NITP took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NITP took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for NITP took 6.818771362304688e-05s
Believability | Calculation of trust value for NITP took 7.867813110351562e-06s
INFO | --- Analysis for notIdentifier took 2.8207314014434814s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 4.076957702636719e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.24941539764404297s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02069377899169922s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.3855438232421875e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 7.62939453125e-06s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.8796656131744385s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 3.933906555175781e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.27455806732177734s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.7894973754882812e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 1.2159347534179688e-05s
INFO | --- Analysis for npg took 2.881486177444458s
Availability | SPARQL endpoint availability check for NPM took 4.029273986816406e-05s
Availability | VoID file availability check for NPM took 0.00030517578125s
Completeness | Calculation of interlinking completeness for NPM took 0.2604045867919922s
Reputation | Calculation of the PageRank for NPM took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for NPM took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NPM took 0.0008513927459716797s
Interlinking | Calculation of Clustering coefficient for NPM took 4.2438507080078125e-05s
Believability | Calculation of trust value for NPM took 8.58306884765625e-06s
INFO | --- Analysis for npm took 2.8887031078338623s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.04613757133483887s
Availability | VoID file availability check for NTNU special collections took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.2551124095916748s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02063155174255371s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.53131103515625e-05s
Believability | Calculation of trust value for NTNU special collections took 8.106231689453125e-06s
INFO | --- Analysis for ntnusc took 2.9089627265930176s
Availability | SPARQL endpoint availability check for links took 4.076957702636719e-05s
Availability | VoID file availability check for links took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for links took 0.24445033073425293s
Reputation | Calculation of the PageRank for links took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for links took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for links took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for links took 1.33514404296875e-05s
Believability | Calculation of trust value for links took 7.3909759521484375e-06s
INFO | --- Analysis for nugmyanmar took 2.85890793800354s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 8.416175842285156e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.262249231338501s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.584426879882812e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 7.3909759521484375e-06s
INFO | --- Analysis for nuts-geovocab took 2.8201863765716553s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 4.982948303222656e-05s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.26236796379089355s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 6.890296936035156e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 9.298324584960938e-06s
INFO | --- Analysis for nvd took 2.915530204772949s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 4.0531158447265625e-05s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.2682011127471924s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.772445678710938e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 7.867813110351562e-06s
INFO | --- Analysis for nvs took 2.779557943344116s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 4.887580871582031e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0003097057342529297s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.25067973136901855s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.020760774612426758s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001811981201171875s
Believability | Calculation of trust value for New York Times - Linked Open Data took 8.821487426757812e-06s
INFO | --- Analysis for nytimes-linked-open-data took 2.810314655303955s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 3.981590270996094e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.00039458274841308594s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.2432420253753662s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.020534038543701172s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 3.1948089599609375e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 8.344650268554688e-06s
INFO | --- Analysis for o-anc took 2.8563528060913086s
Availability | SPARQL endpoint availability check for OANetzwerk took 4.1484832763671875e-05s
Availability | VoID file availability check for OANetzwerk took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.28000783920288086s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020490646362304688s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.9325485229492188e-05s
Believability | Calculation of trust value for OANetzwerk took 8.106231689453125e-06s
INFO | --- Analysis for oanetzwerk took 2.8158693313598633s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 5.316734313964844e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.2511637210845947s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.021579504013061523s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 3.266334533691406e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 6.4373016357421875e-06s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 3.0727975368499756s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.27441906929016113s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 9.083747863769531e-05s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 7.3909759521484375e-06s
INFO | --- Analysis for ocd took 2.836534261703491s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 4.124641418457031e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0009071826934814453s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.2526364326477051s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.4332275390625e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 8.106231689453125e-06s
INFO | --- Analysis for oceandrilling-borehole took 2.8502395153045654s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 4.124641418457031e-05s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.26218652725219727s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.02049398422241211s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 8.320808410644531e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-codices took 2.876342296600342s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 4.076957702636719e-05s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.25655388832092285s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 8.58306884765625e-06s
INFO | --- Analysis for oceandrilling-dbseabed took 2.819192886352539s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 4.124641418457031e-05s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.2452850341796875s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.528594970703125e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-forams took 2.867621660232544s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 4.1961669921875e-05s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.24974846839904785s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.02084803581237793s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.600120544433594e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-janus took 2.8789706230163574s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 4.00543212890625e-05s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.26312732696533203s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.02054619789123535s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.457069396972656e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 7.152557373046875e-06s
INFO | --- Analysis for oceandrilling-janusamp took 2.7500030994415283s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 4.2438507080078125e-05s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.2700674533843994s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.020766496658325195s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.24249267578125e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 7.867813110351562e-06s
INFO | --- Analysis for oceandrilling-ldeo took 2.910954475402832s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.029273986816406e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.2659890651702881s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.020888090133666992s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0008654594421386719s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.532669067382812e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 8.58306884765625e-06s
INFO | --- Analysis for oclc-fast took 2.831374406814575s
Availability | SPARQL endpoint availability check for Open Data Communities took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Data Communities took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.2732212543487549s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020789384841918945s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Data Communities took 1.7881393432617188e-05s
INFO | --- Analysis for odc took 2.8757894039154053s
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.00026297569274902344s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.2693021297454834s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020818471908569336s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 3.337860107421875e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.52587890625e-05s
INFO | --- Analysis for odc-imd-environment-score took 2.8859524726867676s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.076957702636719e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.24985027313232422s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 3.170967102050781e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 1.2874603271484375e-05s
INFO | --- Analysis for odc-imd-rank-2007 took 2.7607626914978027s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 4.220008850097656e-05s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.2666759490966797s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.0204317569732666s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.981590270996094e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 7.3909759521484375e-06s
INFO | --- Analysis for odc-lsoa took 2.8707847595214844s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 3.981590270996094e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.24924516677856445s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.020765066146850586s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 3.0994415283203125e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 7.867813110351562e-06s
INFO | --- Analysis for odc-population-2005 took 2.846539258956909s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.00543212890625e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.2609736919403076s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020859956741333008s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 8.344650268554688e-06s
INFO | --- Analysis for ods took 2.91563081741333s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 4.100799560546875e-05s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0003235340118408203s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.2592935562133789s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.608268737792969e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for oecd-linked-data took 2.819756269454956s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.00543212890625e-05s
Availability | VoID file availability check for Offener Haushalt took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.26070451736450195s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 3.218650817871094e-05s
Believability | Calculation of trust value for Offener Haushalt took 1.3589859008789062e-05s
INFO | --- Analysis for offener-haushalt took 2.819153070449829s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 4.0531158447265625e-05s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.2828798294067383s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.02116537094116211s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 4.1961669921875e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 7.867813110351562e-06s
INFO | --- Analysis for ogolod took 2.826906204223633s
Availability | SPARQL endpoint availability check for OLAC Metadata took 4.00543212890625e-05s
Availability | VoID file availability check for OLAC Metadata took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.25070953369140625s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020848989486694336s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 4.076957702636719e-05s
Believability | Calculation of trust value for OLAC Metadata took 7.152557373046875e-06s
INFO | --- Analysis for olac took 2.839770555496216s
Availability | SPARQL endpoint availability check for OLiA took 4.315376281738281e-05s
Availability | VoID file availability check for OLiA took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for OLiA took 0.2511277198791504s
Reputation | Calculation of the PageRank for OLiA took 0.021809101104736328s
Interlinking | Calculation of Degree of Connection for OLiA took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for OLiA took 0.0008509159088134766s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00013184547424316406s
Believability | Calculation of trust value for OLiA took 7.3909759521484375e-06s
INFO | --- Analysis for olia took 2.830077648162842s
Availability | SPARQL endpoint availability check for OLiA Discourse took 3.838539123535156e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.2421703338623047s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 3.910064697265625e-05s
Believability | Calculation of trust value for OLiA Discourse took 9.059906005859375e-06s
INFO | --- Analysis for olia-discourse took 2.811305046081543s
Availability | SPARQL endpoint availability check for Open Land Use took 4.076957702636719e-05s
Availability | VoID file availability check for Open Land Use took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.2841331958770752s
Reputation | Calculation of the PageRank for Open Land Use took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Open Land Use took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 2.956390380859375e-05s
Believability | Calculation of trust value for Open Land Use took 6.67572021484375e-06s
INFO | --- Analysis for OLU took 2.799807548522949s
Availability | SPARQL endpoint availability check for OmegaWiki took 4.076957702636719e-05s
Availability | VoID file availability check for OmegaWiki took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.26364874839782715s
Reputation | Calculation of the PageRank for OmegaWiki took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.218650817871094e-05s
Believability | Calculation of trust value for OmegaWiki took 7.62939453125e-06s
INFO | --- Analysis for omegawiki took 2.857717990875244s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.2879633903503418s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0006892681121826172s
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 6.198883056640625e-06s
INFO | --- Analysis for omwn-als took 2.8956401348114014s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.23842310905456543s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-arb took 2.8608639240264893s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 5.435943603515625e-05s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.2771792411804199s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.02053093910217285s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-bul took 2.901705503463745s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 4.172325134277344e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.24587416648864746s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020582199096679688s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-cow took 2.8084073066711426s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.2704291343688965s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020854949951171875s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-cwn took 2.900256395339966s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.24256157875061035s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.020606040954589844s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-dan took 2.804823160171509s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.2663722038269043s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.2874603271484375e-05s
INFO | --- Analysis for omwn-ell took 2.9130380153656006s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.23882842063903809s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
INFO | --- Analysis for omwn-eng took 2.804940938949585s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.2446441650390625s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-fas took 2.812875509262085s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.25133681297302246s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.021556854248046875s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0009102821350097656s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.458427429199219e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 7.152557373046875e-06s
INFO | --- Analysis for omwn-fin took 2.835527181625366s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.26500391960144043s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.020448684692382812s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-fra took 2.8270273208618164s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 4.673004150390625e-05s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.26775527000427246s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.02030348777770996s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-heb took 2.8354692459106445s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.23657584190368652s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.02035379409790039s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-hrv took 2.8156497478485107s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 4.458427429199219e-05s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.2606472969055176s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020226240158081055s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.528594970703125e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-isl took 2.7689545154571533s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 4.124641418457031e-05s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.2665581703186035s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ita took 2.8232266902923584s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.2531862258911133s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-iwn took 2.859424114227295s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 4.673004150390625e-05s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.2656373977661133s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-jpn took 2.929084539413452s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.2407078742980957s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.020919322967529297s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0012123584747314453s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 5.054473876953125e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-mcr took 2.834136486053467s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 4.315376281738281e-05s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.00030684471130371094s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.2461392879486084s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-msa took 2.7965900897979736s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.26099395751953125s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020549297332763672s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-nld took 2.8313052654266357s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.2540757656097412s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.021090269088745117s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0009553432464599609s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 4.6253204345703125e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
INFO | --- Analysis for omwn-nor took 2.7798469066619873s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.2635939121246338s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.020678043365478516s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-pol took 2.9088597297668457s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 6.747245788574219e-05s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.2776808738708496s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02042531967163086s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.814697265625e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 6.9141387939453125e-06s
INFO | --- Analysis for omwn-por took 3.084277868270874s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.25135207176208496s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.020548582077026367s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-ron took 2.8752782344818115s
Availability | SPARQL endpoint availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Availability | VoID file availability check for Slovak WordNet (as part of Open Multilingual WordNet) took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.2689828872680664s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020502328872680664s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
INFO | --- Analysis for omwn-slk took 2.8977718353271484s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.076957702636719e-05s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.25209474563598633s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-slv took 2.832071304321289s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.25000905990600586s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-swe took 2.8614144325256348s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0002808570861816406s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.2394258975982666s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-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.790855407714844e-05s
Believability | Calculation of trust value for Thai WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
INFO | --- Analysis for omwn-tha took 2.78055477142334s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 4.220008850097656e-05s
Availability | VoID file availability check for OntoBeef Domain took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.2731800079345703s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020405054092407227s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.291534423828125e-05s
Believability | Calculation of trust value for OntoBeef Domain took 7.62939453125e-06s
INFO | --- Analysis for ontobeef-domain took 2.8691349029541016s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontos News Portal took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.27339601516723633s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007359981536865234s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 9.322166442871094e-05s
Believability | Calculation of trust value for Ontos News Portal took 7.867813110351562e-06s
INFO | --- Analysis for ontos-news-portal took 2.85866117477417s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 4.00543212890625e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.2703075408935547s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.020450115203857422s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 2.8371810913085938e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 7.152557373046875e-06s
INFO | --- Analysis for ookaboo-rdf-dump took 2.8720216751098633s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 4.100799560546875e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.24804472923278809s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.62396240234375e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 6.67572021484375e-06s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 2.7934763431549072s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.1961669921875e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.2488417625427246s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 7.867813110351562e-06s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 2.8815081119537354s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.076957702636719e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.2645761966705322s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.649162292480469e-05s
Believability | Calculation of trust value for Open Data Euskadi took 7.62939453125e-06s
INFO | --- Analysis for open-data-euskadi took 2.941789388656616s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 7.987022399902344e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.23965048789978027s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020348072052001953s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 0.00010228157043457031s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 8.58306884765625e-06s
INFO | --- Analysis for open-data-risp took 2.830047845840454s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for Open Data Thesaurus took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.27076220512390137s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020299673080444336s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.000682830810546875s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.62939453125e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 7.62939453125e-06s
INFO | --- Analysis for open-data-thesaurus took 2.7861900329589844s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.25205183029174805s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 8.344650268554688e-06s
INFO | --- Analysis for open-data-tor-vergata took 2.8737564086914062s
Availability | SPARQL endpoint availability check for Open Election Data Project took 4.100799560546875e-05s
Availability | VoID file availability check for Open Election Data Project took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.26448988914489746s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020383834838867188s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0006847381591796875s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 6.508827209472656e-05s
Believability | Calculation of trust value for Open Election Data Project took 7.152557373046875e-06s
INFO | --- Analysis for open-election-data-project took 2.8190901279449463s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 4.100799560546875e-05s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.2773885726928711s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.02013111114501953s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.392333984375e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 8.58306884765625e-06s
INFO | --- Analysis for open-energy-info-wiki took 2.780640125274658s
Availability | SPARQL endpoint availability check for Open Library took 4.220008850097656e-05s
Availability | VoID file availability check for Open Library took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Open Library took 0.27771544456481934s
Reputation | Calculation of the PageRank for Open Library took 0.020458221435546875s
Interlinking | Calculation of Degree of Connection for Open Library took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Open Library took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.890296936035156e-05s
Believability | Calculation of trust value for Open Library took 8.58306884765625e-06s
INFO | --- Analysis for open-library took 2.7802484035491943s
Availability | SPARQL endpoint availability check for Open Directory took 4.0531158447265625e-05s
Availability | VoID file availability check for Open Directory took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Open Directory took 0.2531740665435791s
Reputation | Calculation of the PageRank for Open Directory took 0.02020430564880371s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.0040740966796875e-05s
Believability | Calculation of trust value for Open Directory took 1.3589859008789062e-05s
INFO | --- Analysis for open_directory took 2.8890979290008545s
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.0002620220184326172s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.2715334892272949s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.02053523063659668s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Open_Land_Use took 2.828077554702759s
Availability | SPARQL endpoint availability check for flyatlas took 4.076957702636719e-05s
Availability | VoID file availability check for flyatlas took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for flyatlas took 0.27782440185546875s
Reputation | Calculation of the PageRank for flyatlas took 0.02054429054260254s
Interlinking | Calculation of Degree of Connection for flyatlas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for flyatlas took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.956390380859375e-05s
Believability | Calculation of trust value for flyatlas took 1.0967254638671875e-05s
INFO | --- Analysis for openbiomed-flyatlas took 2.8254220485687256s
Availability | SPARQL endpoint availability check for OpenCalais took 3.933906555175781e-05s
Availability | VoID file availability check for OpenCalais took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.2567179203033447s
Reputation | Calculation of the PageRank for OpenCalais took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010251998901367188s
Believability | Calculation of trust value for OpenCalais took 1.2159347534179688e-05s
INFO | --- Analysis for opencalais took 2.843331813812256s
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.00025653839111328125s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.24770736694335938s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020692825317382812s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.224082946777344e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 8.106231689453125e-06s
INFO | --- Analysis for opencorporates took 2.786271810531616s
Availability | SPARQL endpoint availability check for OpenCyc took 3.910064697265625e-05s
Availability | VoID file availability check for OpenCyc took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.2676546573638916s
Reputation | Calculation of the PageRank for OpenCyc took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for OpenCyc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.00010085105895996094s
Believability | Calculation of trust value for OpenCyc took 7.152557373046875e-06s
INFO | --- Analysis for opencyc took 2.887864828109741s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.26665425300598145s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020302295684814453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.218650817871094e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 2.8300914764404297s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 8.249282836914062e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.2683699131011963s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.020470142364501953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.528594970703125e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 2.892059087753296s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 5.269050598144531e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.27364659309387207s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.020308256149291992s
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.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.859351873397827s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 3.9577484130859375e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.2760941982269287s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.020349740982055664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.62396240234375e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-2008 took 2.8354368209838867s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 4.029273986816406e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.2658076286315918s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.020566225051879883s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.6716461181640625e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.2874603271484375e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 2.889918327331543s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0002875328063964844s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.24801397323608398s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020189285278320312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-projections-population took 2.8681910037994385s
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.0002791881561279297s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.27744626998901367s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 4.1961669921875e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.4781951904296875e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 2.8758561611175537s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.2533457279205322s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.854316234588623s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.24949264526367188s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.02024221420288086s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.552436828613281e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 2.8805880546569824s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 4.9591064453125e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.2466440200805664s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.020473957061767578s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 3.552436828613281e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-housing-market took 2.812300682067871s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.23690366744995117s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-imd-crime-rank-2010 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-imd-crime-rank-2010 took 2.7890632152557373s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 4.029273986816406e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.26612257957458496s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.02043628692626953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.743171691894531e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 2.779811143875122s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-income-rank-la-2010 took 3.981590270996094e-05s
Availability | VoID file availability check for opendatacommunities-imd-income-rank-la-2010 took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.23899340629577637s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.02021646499633789s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 2.861835479736328s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 3.933906555175781e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.26612138748168945s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.839599132537842s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.029273986816406e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0005362033843994141s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.253154993057251s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-score-2010 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-imd-score-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 2.748258113861084s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.25489211082458496s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 2.7823050022125244s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.27141451835632324s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.02031564712524414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 2.857900619506836s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.27275681495666504s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020484447479248047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-housing-starts took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-housing-starts took 2.7634408473968506s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 5.1021575927734375e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.26575469970703125s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02050185203552246s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 2.858659029006958s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.221366882324219e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.2712583541870117s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.020364761352539062s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 2.841369390487671s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.24321961402893066s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.02098536491394043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007922649383544922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.886222839355469e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 2.8778860569000244s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.24906325340270996s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.8814713954925537s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.2529103755950928s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.02032017707824707s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.83270525932312s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.2649405002593994s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.02051234245300293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.1961669921875e-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 2.770777463912964s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.981590270996094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.24419569969177246s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.020314455032348633s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 9.5367431640625e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.8821041584014893s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.27521371841430664s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.773192882537842s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 5.316734313964844e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.2727210521697998s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 2.886737585067749s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.27177953720092773s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020462989807128906s
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.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 2.8430111408233643s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.00032448768615722656s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.28873205184936523s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.02082085609436035s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.52587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0010089874267578125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.7220458984375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.3113021850585938e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 2.8732213973999023s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.28035759925842285s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020488739013671875s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.867069721221924s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.2502098083496094s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020708084106445312s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.8316540718078613s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.2509803771972656s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.020540952682495117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.821487426757812e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.8594088554382324s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.2379457950592041s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0006933212280273438s
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 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 2.8659260272979736s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.2438507080078125e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.24525070190429688s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020582199096679688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 2.826707124710083s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.553794860839844e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002994537353515625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.2748098373413086s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 8.58306884765625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 2.8850650787353516s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 4.0531158447265625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.2546205520629883s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.020791292190551758s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 6.937980651855469e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 2.8022336959838867s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.940696716308594e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.26241135597229004s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.315376281738281e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 2.8499152660369873s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.267692565917969e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.26949357986450195s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.363059997558594e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 2.878054141998291s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 7.2479248046875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.2422783374786377s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.024857759475708008s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.0503997802734375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0012853145599365234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.4849853515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.344650268554688e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 2.9208743572235107s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.1961669921875e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0003609657287597656s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.24724817276000977s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.021108627319335938s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.9591064453125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 2.8706159591674805s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.220008850097656e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.24878334999084473s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0008568763732910156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 4.9114227294921875e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 7.3909759521484375e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 2.8875293731689453s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.172325134277344e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.26486754417419434s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.020874977111816406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007681846618652344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 4.3392181396484375e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.106231689453125e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 2.8506641387939453s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 4.124641418457031e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.24757933616638184s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 7.867813110351562e-06s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 2.7488420009613037s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 4.100799560546875e-05s
Availability | VoID file availability check for Open Data of Ecuador took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.24923968315124512s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.797645568847656e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 7.3909759521484375e-06s
INFO | --- Analysis for opendataec took 2.837674379348755s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.076957702636719e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.24433684349060059s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.020770549774169922s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 2.8331291675567627s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 4.172325134277344e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.2391047477722168s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.021903038024902344s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0011436939239501953s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 8.106231689453125e-06s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.761054515838623s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 7.224082946777344e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.24488496780395508s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 4.1484832763671875e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 2.7982242107391357s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.029273986816406e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.0003445148468017578s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.24689054489135742s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.020590782165527344s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-education-rank took 2.7759413719177246s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.076957702636719e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.26395392417907715s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-employment-rank took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-employment-rank took 0.0007076263427734375s
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 6.67572021484375e-06s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 2.7952611446380615s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 4.410743713378906e-05s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.2700083255767822s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 7.152557373046875e-06s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.760521411895752s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 4.172325134277344e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.24291753768920898s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020475387573242188s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 9.059906005859375e-06s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.7552638053894043s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 4.7206878662109375e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.2684175968170166s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.020627260208129883s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 7.62939453125e-06s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 2.831284761428833s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 4.124641418457031e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.25581836700439453s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 8.821487426757812e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.757917881011963s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 4.100799560546875e-05s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.2638843059539795s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 7.62939453125e-06s
INFO | --- Analysis for openlink-lod-cache took 2.863199472427368s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 4.00543212890625e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.00027871131896972656s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.24953818321228027s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.0206451416015625s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.632110595703125e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 8.344650268554688e-06s
INFO | --- Analysis for openlinksw-dataspaces took 2.7742061614990234s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 4.1484832763671875e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.2662539482116699s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 5.1975250244140625e-05s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 0.00010895729064941406s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 1.3113021850585938e-05s
INFO | --- Analysis for openlylocal took 2.844216823577881s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenMobileNetwork took 0.0002841949462890625s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.25003504753112793s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.020527362823486328s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 8.20159912109375e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 7.152557373046875e-06s
INFO | --- Analysis for openmobilenetwork took 2.8237266540527344s
Availability | SPARQL endpoint availability check for OpenTox took 4.00543212890625e-05s
Availability | VoID file availability check for OpenTox took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for OpenTox took 0.27132606506347656s
Reputation | Calculation of the PageRank for OpenTox took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for OpenTox took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for OpenTox took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.123283386230469e-05s
Believability | Calculation of trust value for OpenTox took 7.867813110351562e-06s
INFO | --- Analysis for opentox took 2.869088649749756s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 4.1961669921875e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.26953983306884766s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 2.9802322387695312e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 7.152557373046875e-06s
INFO | --- Analysis for openuplabs took 2.7556684017181396s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 4.100799560546875e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.2586700916290283s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.02047872543334961s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.0517578125e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 7.62939453125e-06s
INFO | --- Analysis for opus took 2.7853851318359375s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 5.173683166503906e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.27801036834716797s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020999670028686523s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.5762786865234375e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 7.62939453125e-06s
INFO | --- Analysis for orcid took 2.9077749252319336s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.2760469913482666s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.02078557014465332s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.679794311523438e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 9.298324584960938e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 2.8341336250305176s
Availability | SPARQL endpoint availability check for oreilly took 4.3392181396484375e-05s
Availability | VoID file availability check for oreilly took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for oreilly took 0.27440762519836426s
Reputation | Calculation of the PageRank for oreilly took 0.020822763442993164s
Interlinking | Calculation of Degree of Connection for oreilly took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for oreilly took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for oreilly took 4.982948303222656e-05s
Believability | Calculation of trust value for oreilly took 8.58306884765625e-06s
INFO | --- Analysis for oreilly took 2.8188107013702393s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 4.220008850097656e-05s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.00027489662170410156s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.2611880302429199s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020685672760009766s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.5762786865234375e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 7.62939453125e-06s
INFO | --- Analysis for Organchem-Data took 2.870163917541504s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 4.1484832763671875e-05s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.2565348148345947s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.604194641113281e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.3113021850585938e-05s
INFO | --- Analysis for organic-edunet took 2.8472540378570557s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 4.124641418457031e-05s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.00025916099548339844s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.25376081466674805s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.2159347534179688e-05s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 7.62939453125e-06s
INFO | --- Analysis for orkg took 2.809242010116577s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 5.326811075210571s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.27214574813842773s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 8.296966552734375e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 9.059906005859375e-06s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 15.06715202331543s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 4.5299530029296875e-05s
Availability | VoID file availability check for OSM Semantic Network took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.2713658809661865s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.910064697265625e-05s
Believability | Calculation of trust value for OSM Semantic Network took 8.106231689453125e-06s
INFO | --- Analysis for osm-semantic-network took 2.942199468612671s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 4.220008850097656e-05s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.25020480155944824s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020478010177612305s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 8.106231689453125e-06s
INFO | --- Analysis for OTM took 2.8334641456604004s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 4.00543212890625e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.26042962074279785s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.8848648071289062e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 6.67572021484375e-06s
INFO | --- Analysis for ounl-dspace-in-rdf took 2.861815929412842s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.076957702636719e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.2640202045440674s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020914316177368164s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.2159347534179688e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 2.9069430828094482s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 4.363059997558594e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.27017807960510254s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.02099323272705078s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 2.807234764099121s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 4.1961669921875e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.00029087066650390625s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.24998712539672852s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020107746124267578s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-openmeters took 2.8357841968536377s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.2504606246948242s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020660877227783203s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 8.344650268554688e-06s
INFO | --- Analysis for ox-ac-uk-timeseries took 2.8692033290863037s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.2758462429046631s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02147388458251953s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 3.528594970703125e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-vacancies took 2.8534016609191895s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 4.2438507080078125e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00028204917907714844s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.2690441608428955s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.021532058715820312s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 3.075599670410156e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 7.152557373046875e-06s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 2.7963027954101562s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.124641418457031e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.26492881774902344s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020301342010498047s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 2.6941299438476562e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 7.62939453125e-06s
INFO | --- Analysis for oxpoints took 2.8455722332000732s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.4271111488342285s
Availability | VoID file availability check for Pali English Lexicon took 0.0006234645843505859s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.26401543617248535s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 3.0040740966796875e-05s
Believability | Calculation of trust value for Pali English Lexicon took 7.62939453125e-06s
INFO | --- Analysis for pali-english-lexicon took 5.506376266479492s
Availability | SPARQL endpoint availability check for PanLex took 4.00543212890625e-05s
Availability | VoID file availability check for PanLex took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for PanLex took 0.25394129753112793s
Reputation | Calculation of the PageRank for PanLex took 0.020658016204833984s
Interlinking | Calculation of Degree of Connection for PanLex took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PanLex took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.319450378417969e-05s
Believability | Calculation of trust value for PanLex took 7.867813110351562e-06s
INFO | --- Analysis for panlex took 2.7635228633880615s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 4.2438507080078125e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.2708444595336914s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020763397216796875s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.910064697265625e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 8.58306884765625e-06s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 2.787102460861206s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 4.482269287109375e-05s
Availability | VoID file availability check for patents.data.gov.uk took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.2544131278991699s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.020066022872924805s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.8160552978515625e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 7.62939453125e-06s
INFO | --- Analysis for patents-data-gov-uk took 2.793269634246826s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 4.100799560546875e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.2535123825073242s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.4332275390625e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.1682510375976562e-05s
INFO | --- Analysis for pdev-lemon took 2.883631944656372s
Availability | SPARQL endpoint availability check for pdevlemon took 4.1484832763671875e-05s
Availability | VoID file availability check for pdevlemon took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.2535703182220459s
Reputation | Calculation of the PageRank for pdevlemon took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for pdevlemon took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 2.7894973754882812e-05s
Believability | Calculation of trust value for pdevlemon took 6.9141387939453125e-06s
INFO | --- Analysis for pdevlemon took 2.760901689529419s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 4.172325134277344e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.27349400520324707s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.020766258239746094s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.772445678710938e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 7.62939453125e-06s
INFO | --- Analysis for periodo took 2.7796270847320557s
Availability | SPARQL endpoint availability check for Personal_Homepages took 4.029273986816406e-05s
Availability | VoID file availability check for Personal_Homepages took 0.0003056526184082031s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.26274657249450684s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.0003883838653564453s
Believability | Calculation of trust value for Personal_Homepages took 7.152557373046875e-06s
INFO | --- Analysis for personal-homepages took 2.797344923019409s
Availability | SPARQL endpoint availability check for Ontology of University People took 4.00543212890625e-05s
Availability | VoID file availability check for Ontology of University People took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.2658722400665283s
Reputation | Calculation of the PageRank for Ontology of University People took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.86102294921875e-05s
Believability | Calculation of trust value for Ontology of University People took 1.239776611328125e-05s
INFO | --- Analysis for PersonOnto took 2.8710808753967285s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.124641418457031e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.2791635990142822s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0203857421875s
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.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1682510375976562e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 6.198883056640625e-06s
INFO | --- Analysis for PFKHS took 2.841167688369751s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 4.220008850097656e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0005612373352050781s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.26550722122192383s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02014780044555664s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1444091796875e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 7.62939453125e-06s
INFO | --- Analysis for PFRPPH took 2.8774187564849854s
Availability | SPARQL endpoint availability check for PGxLOD took 6.365776062011719e-05s
Availability | VoID file availability check for PGxLOD took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.2753934860229492s
Reputation | Calculation of the PageRank for PGxLOD took 0.020642518997192383s
Interlinking | Calculation of Degree of Connection for PGxLOD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 3.790855407714844e-05s
Believability | Calculation of trust value for PGxLOD took 6.9141387939453125e-06s
INFO | --- Analysis for PGxLOD took 2.8197662830352783s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 4.029273986816406e-05s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.2500457763671875s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.337860107421875e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 6.4373016357421875e-06s
INFO | --- Analysis for phoible took 2.873420238494873s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 3.9577484130859375e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.257274866104126s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.02064347267150879s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0008871555328369141s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.218650817871094e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 6.4373016357421875e-06s
INFO | --- Analysis for PISM took 2.866774797439575s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 4.100799560546875e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0002734661102294922s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.256439208984375s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 9.703636169433594e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for planetdata-project-wiki took 2.821974992752075s
Availability | SPARQL endpoint availability check for digitized plant specimen took 5.4836273193359375e-05s
Availability | VoID file availability check for digitized plant specimen took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.25562047958374023s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.794929504394531e-05s
Believability | Calculation of trust value for digitized plant specimen took 6.9141387939453125e-06s
INFO | --- Analysis for plant-specimen took 2.8296427726745605s
Availability | SPARQL endpoint availability check for Pleiades took 5.626678466796875e-05s
Availability | VoID file availability check for Pleiades took 0.0002942085266113281s
Completeness | Calculation of interlinking completeness for Pleiades took 0.26227831840515137s
Reputation | Calculation of the PageRank for Pleiades took 0.020592927932739258s
Interlinking | Calculation of Degree of Connection for Pleiades took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Pleiades took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Pleiades took 8.726119995117188e-05s
Believability | Calculation of trust value for Pleiades took 6.9141387939453125e-06s
INFO | --- Analysis for pleiades took 2.8215556144714355s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 4.100799560546875e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.27014803886413574s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02028656005859375s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.8371810913085938e-05s
Believability | Calculation of trust value for podorozhnyk.com took 8.106231689453125e-06s
INFO | --- Analysis for podorozhnyk took 2.8635921478271484s
Availability | SPARQL endpoint availability check for Poképédia took 4.0531158447265625e-05s
Availability | VoID file availability check for Poképédia took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for Poképédia took 0.2919960021972656s
Reputation | Calculation of the PageRank for Poképédia took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for Poképédia took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Poképédia took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.794929504394531e-05s
Believability | Calculation of trust value for Poképédia took 7.3909759521484375e-06s
INFO | --- Analysis for pokepedia-fr took 2.9591102600097656s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.315376281738281e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0003044605255126953s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.2635352611541748s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020128488540649414s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.319450378417969e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 8.106231689453125e-06s
INFO | --- Analysis for polymath-virtual-library took 2.829105854034424s
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.00048160552978515625s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.24948906898498535s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02096080780029297s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007228851318359375s
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 7.3909759521484375e-06s
INFO | --- Analysis for portuguese_prisons_releases took 2.83126163482666s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 4.220008850097656e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.255068302154541s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 2.8371810913085938e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 2.816340684890747s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 4.291534423828125e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.2623410224914551s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Corn trading volume and wholesale prices took 2.956390380859375e-05s
Believability | Calculation of trust value for Corn trading volume and wholesale prices took 7.62939453125e-06s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 2.9183945655822754s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 4.100799560546875e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.2754998207092285s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020205974578857422s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.8133392333984375e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 2.8214404582977295s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 5.221366882324219e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.268993616104126s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0008916854858398438s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 3.266334533691406e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 2.848494052886963s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0004930496215820312s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.28148436546325684s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 3.0040740966796875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 8.344650268554688e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 2.8624107837677s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 4.649162292480469e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.2480912208557129s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of barley took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of barley took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 2.835700511932373s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.27057480812072754s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.021196842193603516s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 2.8146660327911377s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.27516841888427734s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.6464462280273438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 6.9141387939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 2.889928102493286s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 4.076957702636719e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.2459559440612793s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.02005624771118164s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.9325485229492188e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 2.851574182510376s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.0003361701965332031s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.2708864212036133s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.020331859588623047s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.7418136596679688e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 2.85357666015625s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 8.368492126464844e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0003058910369873047s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.23528432846069336s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020269155502319336s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 8.106231689453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 2.8070218563079834s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.2606699466705322s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020161151885986328s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.6464462280273438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 2.840237855911255s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 0.0001068115234375s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.25322818756103516s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.02046990394592285s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.6941299438476562e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 2.768313407897949s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.2392416000366211s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.02148890495300293s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0010364055633544922s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 3.743171691894531e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 7.62939453125e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 2.9211456775665283s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 4.100799560546875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.25702524185180664s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.020090579986572266s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of potato took 2.8371810913085938e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of potato took 8.821487426757812e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 2.8905017375946045s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 4.124641418457031e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.2681405544281006s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.02018284797668457s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.6464462280273438e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 1.1920928955078125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.900226354598999s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 4.1484832763671875e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.27335643768310547s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0009179115295410156s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.337860107421875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 2.8682405948638916s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 4.029273986816406e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.0003261566162109375s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.24448823928833008s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.02009296417236328s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.6941299438476562e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 7.3909759521484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 2.837308406829834s
Availability | SPARQL endpoint availability check for prefix.cc took 5.078315734863281e-05s
Availability | VoID file availability check for prefix.cc took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.2667877674102783s
Reputation | Calculation of the PageRank for prefix.cc took 0.020695209503173828s
Interlinking | Calculation of Degree of Connection for prefix.cc took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for prefix.cc took 0.0007851123809814453s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 4.124641418457031e-05s
Believability | Calculation of trust value for prefix.cc took 1.2636184692382812e-05s
INFO | --- Analysis for prefix-cc took 2.8347065448760986s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 4.029273986816406e-05s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.27477025985717773s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020705699920654297s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.863739013671875e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 8.106231689453125e-06s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 2.841813802719116s
Availability | SPARQL endpoint availability check for PreLex took 4.029273986816406e-05s
Availability | VoID file availability check for PreLex took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for PreLex took 0.27446627616882324s
Reputation | Calculation of the PageRank for PreLex took 0.02008819580078125s
Interlinking | Calculation of Degree of Connection for PreLex took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PreLex took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.818771362304688e-05s
Believability | Calculation of trust value for PreLex took 8.106231689453125e-06s
INFO | --- Analysis for prelex took 2.8735690116882324s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.154231309890747s
Availability | VoID file availability check for Prelinger Archives took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.23914074897766113s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.8133392333984375e-05s
Believability | Calculation of trust value for Prelinger Archives took 8.106231689453125e-06s
INFO | --- Analysis for prelinger_archives took 5.913540363311768s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 4.076957702636719e-05s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.24936389923095703s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020528078079223633s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0008230209350585938s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 6.67572021484375e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 7.3909759521484375e-06s
INFO | --- Analysis for premon took 2.8010964393615723s
Availability | SPARQL endpoint availability check for Previsible took 4.0531158447265625e-05s
Availability | VoID file availability check for Previsible took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Previsible took 0.2643420696258545s
Reputation | Calculation of the PageRank for Previsible took 0.02062678337097168s
Interlinking | Calculation of Degree of Connection for Previsible took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Previsible took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Previsible took 1.1682510375976562e-05s
Believability | Calculation of trust value for Previsible took 7.867813110351562e-06s
INFO | --- Analysis for Previsible took 2.8944246768951416s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 5.53131103515625e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.2471923828125s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.020788192749023438s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 5.650520324707031e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 6.9141387939453125e-06s
INFO | --- Analysis for princeton-library-findingaids took 2.8676834106445312s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 4.00543212890625e-05s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.25547051429748535s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020510196685791016s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.647804260253906e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for PrinParLat took 2.8640222549438477s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.49301671981811523s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.24296808242797852s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.020347118377685547s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.796287536621094e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 6.67572021484375e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 3.277815103530884s
Availability | SPARQL endpoint availability check for Prior Panel took 4.0531158447265625e-05s
Availability | VoID file availability check for Prior Panel took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.25106000900268555s
Reputation | Calculation of the PageRank for Prior Panel took 0.02035236358642578s
Interlinking | Calculation of Degree of Connection for Prior Panel took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 3.266334533691406e-05s
Believability | Calculation of trust value for Prior Panel took 6.9141387939453125e-06s
INFO | --- Analysis for Prior_Panel took 2.8295047283172607s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 4.076957702636719e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.2735309600830078s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 2.7894973754882812e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 7.152557373046875e-06s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 2.8387038707733154s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 4.100799560546875e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.2736191749572754s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 3.0517578125e-05s
Believability | Calculation of trust value for Procomún SPARQL took 7.152557373046875e-06s
INFO | --- Analysis for procomun-sparql took 2.901883602142334s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 4.076957702636719e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.2673783302307129s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.020515918731689453s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 2.9802322387695312e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 6.67572021484375e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 2.8919997215270996s
Availability | SPARQL endpoint availability check for ProductDB took 4.076957702636719e-05s
Availability | VoID file availability check for ProductDB took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for ProductDB took 0.2640986442565918s
Reputation | Calculation of the PageRank for ProductDB took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for ProductDB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for ProductDB took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for ProductDB took 0.00010919570922851562s
Believability | Calculation of trust value for ProductDB took 6.67572021484375e-06s
INFO | --- Analysis for productdb took 2.823594570159912s
Availability | SPARQL endpoint availability check for Product Types Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for Product Types Ontology took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.27638840675354004s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.02023768424987793s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 3.790855407714844e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.581710815429688e-05s
Believability | Calculation of trust value for Product Types Ontology took 6.67572021484375e-06s
INFO | --- Analysis for productontology took 2.8743412494659424s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 4.863739013671875e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.27495527267456055s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.020512819290161133s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 0.0001010894775390625s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 6.9141387939453125e-06s
INFO | --- Analysis for prospects-and-trends-gnoss took 2.878309965133667s
Availability | SPARQL endpoint availability check for provenanceweb took 8.416175842285156e-05s
Availability | VoID file availability check for provenanceweb took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.263355016708374s
Reputation | Calculation of the PageRank for provenanceweb took 0.02071213722229004s
Interlinking | Calculation of Degree of Connection for provenanceweb took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for provenanceweb took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 7.367134094238281e-05s
Believability | Calculation of trust value for provenanceweb took 6.9141387939453125e-06s
INFO | --- Analysis for provenanceweb took 2.833310842514038s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 4.172325134277344e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.28998374938964844s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020131826400756836s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 0.00010085105895996094s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 9.5367431640625e-06s
INFO | --- Analysis for proyectoapadrina took 2.8237526416778564s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 4.172325134277344e-05s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.2546663284301758s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.02053689956665039s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.218650817871094e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 7.3909759521484375e-06s
INFO | --- Analysis for pscs-catalogue took 2.8002750873565674s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 4.00543212890625e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.27575159072875977s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.020299196243286133s
Interlinking | Calculation of Degree of Connection for Polythematic Structured Subject Heading System took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Polythematic Structured Subject Heading System took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 6.890296936035156e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 7.152557373046875e-06s
INFO | --- Analysis for psh-subject-headings took 2.874720811843872s
Availability | SPARQL endpoint availability check for Depression took 4.5299530029296875e-05s
Availability | VoID file availability check for Depression took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Depression took 0.2510354518890381s
Reputation | Calculation of the PageRank for Depression took 0.020781993865966797s
Interlinking | Calculation of Degree of Connection for Depression took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Depression took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Depression took 2.8133392333984375e-05s
Believability | Calculation of trust value for Depression took 6.4373016357421875e-06s
INFO | --- Analysis for Psychology took 2.7971549034118652s
Availability | SPARQL endpoint availability check for PubChem RDF took 4.00543212890625e-05s
Availability | VoID file availability check for PubChem RDF took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.26896023750305176s
Reputation | Calculation of the PageRank for PubChem RDF took 0.02017807960510254s
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 3.814697265625e-05s
Believability | Calculation of trust value for PubChem RDF took 1.239776611328125e-05s
INFO | --- Analysis for PubChem_RDF took 2.8293347358703613s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 4.00543212890625e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.2684285640716553s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.020743608474731445s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.9325485229492188e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 7.3909759521484375e-06s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 2.8492252826690674s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 4.076957702636719e-05s
Availability | VoID file availability check for Public Spending in Greece took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.24911737442016602s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.867813110351562e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.1682510375976562e-05s
INFO | --- Analysis for public-spending-in-greece took 2.8914523124694824s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 4.00543212890625e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.2779712677001953s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.7418136596679688e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 7.62939453125e-06s
INFO | --- Analysis for publications-of-charles-university-in-prague took 2.872915506362915s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 4.029273986816406e-05s
Availability | VoID file availability check for Publications Office Authority tables took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.29544568061828613s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 3.361701965332031e-05s
Believability | Calculation of trust value for Publications Office Authority tables took 7.3909759521484375e-06s
INFO | --- Analysis for publications_office_authority_tables took 2.926614999771118s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 4.124641418457031e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.25660157203674316s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.020102262496948242s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 2.7894973754882812e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 6.9141387939453125e-06s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 2.8091869354248047s
Availability | SPARQL endpoint availability check for QBOAirbase took 4.076957702636719e-05s
Availability | VoID file availability check for QBOAirbase took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.2509591579437256s
Reputation | Calculation of the PageRank for QBOAirbase took 0.020640134811401367s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.653236389160156e-05s
Believability | Calculation of trust value for QBOAirbase took 6.9141387939453125e-06s
INFO | --- Analysis for qboairbase took 2.838827610015869s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.0531158447265625e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0003342628479003906s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.2669968605041504s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.02061748504638672s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007646083831787109s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 3.266334533691406e-05s
Believability | Calculation of trust value for qualitywebdata.org took 7.152557373046875e-06s
INFO | --- Analysis for qualitywebdata-org took 2.8177764415740967s
Availability | SPARQL endpoint availability check for Qualité de l'air took 4.3392181396484375e-05s
Availability | VoID file availability check for Qualité de l'air took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.24100208282470703s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.9087066650390625e-05s
Believability | Calculation of trust value for Qualité de l'air took 7.3909759521484375e-06s
INFO | --- Analysis for Qualité_de_l'air took 2.8809895515441895s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.1961669921875e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.24211406707763672s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.020767688751220703s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 2.956390380859375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 2.1696090698242188e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 2.808408498764038s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.6147737503051758s
Availability | VoID file availability check for Querolus in LiLa took 0.00035881996154785156s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.2904694080352783s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.838539123535156e-05s
Believability | Calculation of trust value for Querolus in LiLa took 7.62939453125e-06s
INFO | --- Analysis for Querolus took 3.898749828338623s
Availability | SPARQL endpoint availability check for Quotations Book took 4.00543212890625e-05s
Availability | VoID file availability check for Quotations Book took 0.0005211830139160156s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.25563526153564453s
Reputation | Calculation of the PageRank for Quotations Book took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Quotations Book took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 3.0517578125e-05s
Believability | Calculation of trust value for Quotations Book took 7.867813110351562e-06s
INFO | --- Analysis for quotations_book took 2.787357807159424s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00028514862060546875s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.2476515769958496s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.02049732208251953s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.361701965332031e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 6.67572021484375e-06s
INFO | --- Analysis for r4r took 2.7845754623413086s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.029273986816406e-05s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.260589599609375s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.02011728286743164s
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.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.482269287109375e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 6.9141387939453125e-06s
INFO | --- Analysis for racai-legalnero took 2.834113359451294s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 4.1484832763671875e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.23955559730529785s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020533323287963867s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 2.765655517578125e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 8.106231689453125e-06s
INFO | --- Analysis for racai-llod-corola-we took 2.838444232940674s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 7.390975952148438e-05s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.2558720111846924s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.02110767364501953s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 3.170967102050781e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.239776611328125e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 2.8567662239074707s
Availability | SPARQL endpoint availability check for RoLEX took 4.00543212890625e-05s
Availability | VoID file availability check for RoLEX took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for RoLEX took 0.2637817859649658s
Reputation | Calculation of the PageRank for RoLEX took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for RoLEX took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RoLEX took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for RoLEX took 2.86102294921875e-05s
Believability | Calculation of trust value for RoLEX took 3.266334533691406e-05s
INFO | --- Analysis for racai-llod-rolex took 2.8344733715057373s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.6253204345703125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00024819374084472656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.2533993721008301s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.86102294921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.62939453125e-06s
INFO | --- Analysis for racai-llod-romanian-treebank took 2.792170286178589s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 4.1961669921875e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.24205827713012695s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.02060842514038086s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.7894973754882812e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 2.817093849182129s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.744529724121094e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.26593995094299316s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0009670257568359375s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 3.5762786865234375e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 2.8569321632385254s
Availability | SPARQL endpoint availability check for Turtle-RDF Romanian Wordnet took 4.00543212890625e-05s
Availability | VoID file availability check for Turtle-RDF Romanian Wordnet took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.2672853469848633s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.8848648071289062e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.1920928955078125e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 2.8030846118927s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 4.076957702636719e-05s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.2604410648345947s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.8848648071289062e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 6.9141387939453125e-06s
INFO | --- Analysis for racai-llod-rtasc took 2.812718152999878s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 7.033348083496094e-05s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.28960537910461426s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 3.0040740966796875e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-simonero took 2.8691635131835938s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.22066116333007812s
Availability | VoID file availability check for Rådata nå! took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.2784087657928467s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02039813995361328s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 8.106231689453125e-05s
Believability | Calculation of trust value for Rådata nå! took 7.152557373046875e-06s
INFO | --- Analysis for radatana took 3.147547721862793s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 4.2438507080078125e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.27518534660339355s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.020689725875854492s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.62396240234375e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 7.152557373046875e-06s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 2.8674192428588867s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 4.100799560546875e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0003190040588378906s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.2707219123840332s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0009529590606689453s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.409385681152344e-05s
Believability | Calculation of trust value for Raphael Research Resource took 7.62939453125e-06s
INFO | --- Analysis for raphaelresearchresource took 2.847395420074463s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 6.580352783203125e-05s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.00032258033752441406s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.2776756286621094s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0009510517120361328s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.409385681152344e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 8.106231689453125e-06s
INFO | --- Analysis for ravensburg-local-shopping-graph took 2.7814199924468994s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 4.029273986816406e-05s
Availability | VoID file availability check for Polish LGU financial statements took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.24370431900024414s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.021089553833007812s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 2.9325485229492188e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 7.3909759521484375e-06s
INFO | --- Analysis for Rb_PL_LGU took 2.779357671737671s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.0002923011779785156s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2647669315338135s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.000827789306640625s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.1948089599609375e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 6.9141387939453125e-06s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 2.9179139137268066s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 4.172325134277344e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.26685214042663574s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.021805763244628906s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0010502338409423828s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 4.100799560546875e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 2.7686471939086914s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.0003075599670410156s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.23825836181640625s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020627737045288086s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.123283386230469e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 8.106231689453125e-06s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 2.777371644973755s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 8.511543273925781e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.27573060989379883s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020680904388427734s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 2.874443769454956s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 4.124641418457031e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.23710989952087402s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.02063751220703125s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.123283386230469e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 8.58306884765625e-06s
INFO | --- Analysis for rcahmw-periods-list took 2.806697368621826s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 4.0531158447265625e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.2900669574737549s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020643949508666992s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.487701416015625e-05s
Believability | Calculation of trust value for RDF Book Mashup took 8.344650268554688e-06s
INFO | --- Analysis for rdf-book-mashup took 2.886713743209839s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 4.1961669921875e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.24744558334350586s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.02699875831604004s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00011539459228515625s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 9.059906005859375e-06s
INFO | --- Analysis for rdfize-lastfm took 3.1433265209198s
Availability | SPARQL endpoint availability check for RDFLicense took 4.1484832763671875e-05s
Availability | VoID file availability check for RDFLicense took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.24910783767700195s
Reputation | Calculation of the PageRank for RDFLicense took 0.02050328254699707s
Interlinking | Calculation of Degree of Connection for RDFLicense took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for RDFLicense took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.0040740966796875e-05s
Believability | Calculation of trust value for RDFLicense took 7.867813110351562e-06s
INFO | --- Analysis for rdflicense took 2.8825647830963135s
Availability | SPARQL endpoint availability check for RDFohloh took 3.9577484130859375e-05s
Availability | VoID file availability check for RDFohloh took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.2751438617706299s
Reputation | Calculation of the PageRank for RDFohloh took 0.023303747177124023s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0012576580047607422s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 0.00011849403381347656s
Believability | Calculation of trust value for RDFohloh took 9.298324584960938e-06s
INFO | --- Analysis for rdfohloh took 2.821312665939331s
Availability | SPARQL endpoint availability check for Reactome RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for Reactome RDF took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.25983643531799316s
Reputation | Calculation of the PageRank for Reactome RDF took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.6716461181640625e-05s
Believability | Calculation of trust value for Reactome RDF took 8.344650268554688e-06s
INFO | --- Analysis for reactome-rdf took 2.8523108959198s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 3.981590270996094e-05s
Availability | VoID file availability check for Rechtspraak.nl took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.23629379272460938s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 0.00010395050048828125s
Believability | Calculation of trust value for Rechtspraak.nl took 6.9141387939453125e-06s
INFO | --- Analysis for rechtspraak took 2.825924873352051s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 5.125999450683594e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.2732565402984619s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.654594421386719e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 7.152557373046875e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 2.8623557090759277s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 4.00543212890625e-05s
Availability | VoID file availability check for reference.data.gov.uk took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.2540934085845947s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020613670349121094s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015282630920410156s
Believability | Calculation of trust value for reference.data.gov.uk took 1.1444091796875e-05s
INFO | --- Analysis for reference-data-gov-uk took 2.839040756225586s
Availability | SPARQL endpoint availability check for Regiony took 4.0531158447265625e-05s
Availability | VoID file availability check for Regiony took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Regiony took 0.2675137519836426s
Reputation | Calculation of the PageRank for Regiony took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for Regiony took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Regiony took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Regiony took 2.9325485229492188e-05s
Believability | Calculation of trust value for Regiony took 6.9141387939453125e-06s
INFO | --- Analysis for regiony took 2.877683162689209s
Availability | SPARQL endpoint availability check for RELD took 4.220008850097656e-05s
Availability | VoID file availability check for RELD took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for RELD took 0.26963138580322266s
Reputation | Calculation of the PageRank for RELD took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for RELD took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RELD took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for RELD took 3.0994415283203125e-05s
Believability | Calculation of trust value for RELD took 8.821487426757812e-06s
INFO | --- Analysis for RELD took 2.828052520751953s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 5.245208740234375e-05s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.27590513229370117s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02286386489868164s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0012576580047607422s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 5.1021575927734375e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 8.58306884765625e-06s
INFO | --- Analysis for reload took 2.836458683013916s
Availability | SPARQL endpoint availability check for Land use merced dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0002770423889160156s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.26641392707824707s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.02068924903869629s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.9087066650390625e-05s
Believability | Calculation of trust value for Land use merced dataset took 8.106231689453125e-06s
INFO | --- Analysis for remote_Sensing took 2.9413418769836426s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 4.029273986816406e-05s
Availability | VoID file availability check for Renewable Energy Generators took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.25710487365722656s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.3392181396484375e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 6.198883056640625e-06s
INFO | --- Analysis for renewable_energy_generators took 2.817233085632324s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 4.3392181396484375e-05s
Availability | VoID file availability check for research.data.gov.uk took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.24869108200073242s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.02120828628540039s
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.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 0.00010752677917480469s
Believability | Calculation of trust value for research.data.gov.uk took 6.9141387939453125e-06s
INFO | --- Analysis for research-data-gov-uk took 2.7990143299102783s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 4.076957702636719e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.2528071403503418s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.020359277725219727s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 2.9325485229492188e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 8.344650268554688e-06s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 2.7747793197631836s
Availability | SPARQL endpoint availability check for Restaurantes took 4.076957702636719e-05s
Availability | VoID file availability check for Restaurantes took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.24830937385559082s
Reputation | Calculation of the PageRank for Restaurantes took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for Restaurantes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Restaurantes took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 2.86102294921875e-05s
Believability | Calculation of trust value for Restaurantes took 7.867813110351562e-06s
INFO | --- Analysis for restaurantes-zaragoza took 2.8500161170959473s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 5.364418029785156e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.00027108192443847656s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.24463152885437012s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.389617919921875e-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 2.8532400131225586s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 4.1961669921875e-05s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.2372281551361084s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 2.9087066650390625e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 6.4373016357421875e-06s
INFO | --- Analysis for revistas_turismo took 2.8215701580047607s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 3.9577484130859375e-05s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.2636866569519043s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00011467933654785156s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.1444091796875e-05s
INFO | --- Analysis for revyu took 2.8382813930511475s
Availability | SPARQL endpoint availability check for sdafsadf took 3.886222839355469e-05s
Availability | VoID file availability check for sdafsadf took 0.0002856254577636719s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.2591385841369629s
Reputation | Calculation of the PageRank for sdafsadf took 0.0203702449798584s
Interlinking | Calculation of Degree of Connection for sdafsadf took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sdafsadf took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.9087066650390625e-05s
Believability | Calculation of trust value for sdafsadf took 1.1920928955078125e-05s
INFO | --- Analysis for rgsdfg took 2.8511881828308105s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.0531158447265625e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.000286102294921875s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.24591326713562012s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.020795106887817383s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007507801055908203s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.839897155761719e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 1.239776611328125e-05s
INFO | --- Analysis for riese took 2.815328598022461s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 3.886222839355469e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.2642061710357666s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.020566463470458984s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007855892181396484s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.147125244140625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 1.2874603271484375e-05s
INFO | --- Analysis for rijksmuseum took 2.815917491912842s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 30.42125105857849s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.23380446434020996s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.020380496978759766s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 4.076957702636719e-05s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 7.867813110351562e-06s
INFO | --- Analysis for rism took 63.245089054107666s
Availability | SPARQL endpoint availability check for RISM Authority data took 20.162547826766968s
Availability | VoID file availability check for RISM Authority data took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.2662496566772461s
Reputation | Calculation of the PageRank for RISM Authority data took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 4.38690185546875e-05s
Believability | Calculation of trust value for RISM Authority data took 1.0967254638671875e-05s
INFO | --- Analysis for rism-authorities took 53.082008838653564s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.482269287109375e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.24768662452697754s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.0206758975982666s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for engineering equipment ontology took 7.867813110351562e-06s
INFO | --- Analysis for rk took 2.8633437156677246s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.27519798278808594s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02059626579284668s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.00022220611572265625s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-acm took 2.8255679607391357s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.2904829978942871s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.020894289016723633s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001385211944580078s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-budapest took 2.910806179046631s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.25999879837036133s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.020249128341674805s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019240379333496094s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-citeseer took 2.8352255821228027s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.00030493736267089844s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.2573575973510742s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.020497560501098633s
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.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.000156402587890625s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-cordis took 2.8422083854675293s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 5.1021575927734375e-05s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.2663147449493408s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.02053213119506836s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00016307830810546875s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-courseware took 2.803572177886963s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 4.124641418457031e-05s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.24865984916687012s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020592689514160156s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.790855407714844e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-crime took 2.7949275970458984s
Availability | SPARQL endpoint availability check for crm took 4.124641418457031e-05s
Availability | VoID file availability check for crm took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for crm took 0.26248955726623535s
Reputation | Calculation of the PageRank for crm took 0.020610809326171875s
Interlinking | Calculation of Degree of Connection for crm took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for crm took 0.0007731914520263672s
Interlinking | Calculation of Clustering coefficient for crm took 3.0040740966796875e-05s
Believability | Calculation of trust value for crm took 1.7404556274414062e-05s
INFO | --- Analysis for rkb-explorer-crm took 2.804917573928833s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.2517523765563965s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02078104019165039s
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.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00012493133544921875s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-curriculum took 2.7885990142822266s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00027561187744140625s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.24902915954589844s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.0206906795501709s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.1021575927734375e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 3.4809112548828125e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 2.8320062160491943s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.26816725730895996s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.02124166488647461s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.000240325927734375s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-dblp took 2.905710458755493s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.2518479824066162s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02036738395690918s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007386207580566406s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.152557373046875e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-deepblue took 2.837268590927124s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.2578878402709961s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.083747863769531e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-deploy took 2.819542646408081s
Availability | SPARQL endpoint availability check for digitaleconomy took 4.029273986816406e-05s
Availability | VoID file availability check for digitaleconomy took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.26270627975463867s
Reputation | Calculation of the PageRank for digitaleconomy took 0.02176523208618164s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for digitaleconomy took 0.0009641647338867188s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 3.3855438232421875e-05s
Believability | Calculation of trust value for digitaleconomy took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 2.8645410537719727s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 4.315376281738281e-05s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.25493478775024414s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020802736282348633s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.0001494884490966797s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-dotac took 2.839395761489868s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 7.271766662597656e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.23513197898864746s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02060556411743164s
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.0007927417755126953s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.458427429199219e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-ecs took 2.803701877593994s
Availability | SPARQL endpoint availability check for enaktingpsi took 5.173683166503906e-05s
Availability | VoID file availability check for enaktingpsi took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.2582087516784668s
Reputation | Calculation of the PageRank for enaktingpsi took 0.02045440673828125s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.86102294921875e-05s
Believability | Calculation of trust value for enaktingpsi took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.8320884704589844s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 4.172325134277344e-05s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.2677602767944336s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.020445823669433594s
Interlinking | Calculation of Degree of Connection for ePrints3 Institutional Archive Collection (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017690658569335938s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-eprints took 2.9028584957122803s
Availability | SPARQL endpoint availability check for epsrc took 4.3392181396484375e-05s
Availability | VoID file availability check for epsrc took 0.00032401084899902344s
Completeness | Calculation of interlinking completeness for epsrc took 0.2890775203704834s
Reputation | Calculation of the PageRank for epsrc took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for epsrc took 6.008148193359375e-05s
Believability | Calculation of trust value for epsrc took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 2.8305609226226807s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.26583099365234375s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.020690202713012695s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.416175842285156e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-era took 2.843529462814331s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.25058794021606445s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 9.918212890625e-05s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-eurecom took 2.886321783065796s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 4.124641418457031e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.2534949779510498s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 2.6941299438476562e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-foreign took 2.8427186012268066s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 5.91278076171875e-05s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.2529754638671875s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.021105051040649414s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.96453857421875e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ft took 2.8211851119995117s
Availability | SPARQL endpoint availability check for fun took 4.1484832763671875e-05s
Availability | VoID file availability check for fun took 0.0002906322479248047s
Completeness | Calculation of interlinking completeness for fun took 0.24519944190979004s
Reputation | Calculation of the PageRank for fun took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for fun took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for fun took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for fun took 7.081031799316406e-05s
Believability | Calculation of trust value for fun took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-fun took 2.9295027256011963s
Availability | SPARQL endpoint availability check for gdlc took 4.029273986816406e-05s
Availability | VoID file availability check for gdlc took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for gdlc took 0.2603418827056885s
Reputation | Calculation of the PageRank for gdlc took 0.0203859806060791s
Interlinking | Calculation of Degree of Connection for gdlc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.389617919921875e-05s
Believability | Calculation of trust value for gdlc took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-gdlc took 2.744847297668457s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.0002944469451904297s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.2565031051635742s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020737886428833008s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0008060932159423828s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00012135505676269531s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ibm took 2.857999324798584s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 4.0531158447265625e-05s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.25751519203186035s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020861148834228516s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.00013303756713867188s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 6.67572021484375e-06s
INFO | --- Analysis for rkb-explorer-ieee took 2.849916934967041s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 4.3392181396484375e-05s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.2819802761077881s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.020772218704223633s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001373291015625s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-irit took 2.8550477027893066s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 3.9577484130859375e-05s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.26570916175842285s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.151199340820312e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.848517894744873s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 4.482269287109375e-05s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.25008177757263184s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.020363330841064453s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.319450378417969e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-jisc took 2.8069958686828613s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0003178119659423828s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.2687342166900635s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.020713329315185547s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0006923675537109375s
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 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-kaunas took 2.8043324947357178s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 5.14984130859375e-05s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.2715730667114258s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00015783309936523438s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-kisti took 2.9154436588287354s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 3.9577484130859375e-05s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.2680702209472656s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.000141143798828125s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-laas took 2.8557229042053223s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.2543344497680664s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.021017074584960938s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.461143493652344e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-lisbon took 2.8401010036468506s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 4.315376281738281e-05s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.00030112266540527344s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.25072526931762695s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.00112152099609375s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001800060272216797s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 2.801290512084961s
Availability | SPARQL endpoint availability check for notube took 4.0531158447265625e-05s
Availability | VoID file availability check for notube took 0.0003948211669921875s
Completeness | Calculation of interlinking completeness for notube took 0.2797372341156006s
Reputation | Calculation of the PageRank for notube took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for notube took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for notube took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for notube took 4.2438507080078125e-05s
Believability | Calculation of trust value for notube took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-notube took 2.8424293994903564s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.26016688346862793s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.020563602447509766s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00012993812561035156s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.880279302597046s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 6.604194641113281e-05s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.2737572193145752s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0001583099365234375s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-oai took 2.842663288116455s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0003116130828857422s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.25130534172058105s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 3.0279159545898438e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-opencyc took 2.8386006355285645s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0003802776336669922s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.27662110328674316s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.02102065086364746s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.510185241699219e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 5.4836273193359375e-06s
INFO | --- Analysis for rkb-explorer-os took 2.923752546310425s
Availability | SPARQL endpoint availability check for photos took 4.124641418457031e-05s
Availability | VoID file availability check for photos took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for photos took 0.2738947868347168s
Reputation | Calculation of the PageRank for photos took 0.02079319953918457s
Interlinking | Calculation of Degree of Connection for photos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for photos took 7.271766662597656e-05s
Believability | Calculation of trust value for photos took 8.344650268554688e-06s
INFO | --- Analysis for rkb-explorer-photos took 2.952878475189209s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 4.482269287109375e-05s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0003113746643066406s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.24566125869750977s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.0001380443572998047s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-pisa took 2.8200974464416504s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 4.267692565917969e-05s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.24065113067626953s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.02065300941467285s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00018787384033203125s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-rae2001 took 2.82366681098938s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00010061264038085938s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00028586387634277344s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.24224424362182617s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020827054977416992s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00014019012451171875s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 5.9604644775390625e-06s
INFO | --- Analysis for rkb-explorer-resex took 2.789513111114502s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.2652003765106201s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020784854888916016s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0008118152618408203s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.965896606445312e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-risks took 2.8379790782928467s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00031113624572753906s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.2548830509185791s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020499706268310547s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0001251697540283203s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-roma took 2.8432371616363525s
Availability | SPARQL endpoint availability check for roni took 4.363059997558594e-05s
Availability | VoID file availability check for roni took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for roni took 0.24991154670715332s
Reputation | Calculation of the PageRank for roni took 0.02059483528137207s
Interlinking | Calculation of Degree of Connection for roni took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for roni took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for roni took 3.0517578125e-05s
Believability | Calculation of trust value for roni took 6.198883056640625e-06s
INFO | --- Analysis for rkb-explorer-roni took 2.837293863296509s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 6.747245788574219e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.25015997886657715s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.020601749420166016s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0002129077911376953s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-southampton took 2.793381690979004s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.25627899169921875s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.0207059383392334s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Universität Ulm (RKBExplorer) took 0.00010752677917480469s
Believability | Calculation of trust value for Universität Ulm (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ulm took 2.7255654335021973s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.246781587600708s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.02068161964416504s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 0.00010132789611816406s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 7.3909759521484375e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 2.7469239234924316s
Availability | SPARQL endpoint availability check for webconf took 4.029273986816406e-05s
Availability | VoID file availability check for webconf took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for webconf took 0.2285444736480713s
Reputation | Calculation of the PageRank for webconf took 0.0206911563873291s
Interlinking | Calculation of Degree of Connection for webconf took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for webconf took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010132789611816406s
Believability | Calculation of trust value for webconf took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-webconf took 2.7557661533355713s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.22799062728881836s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 7.2479248046875e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-webscience took 2.742316246032715s
Availability | SPARQL endpoint availability check for ReSIST Project Wiki (RKBExplorer) took 5.4836273193359375e-05s
Availability | VoID file availability check for ReSIST Project Wiki (RKBExplorer) took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.2633376121520996s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020933866500854492s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.0002067089080810547s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-wiki took 2.9190914630889893s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 4.2438507080078125e-05s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.25240492820739746s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020755767822265625s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.822845458984375e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-wordnet took 2.829822540283203s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 4.458427429199219e-05s
Availability | VoID file availability check for RKB Explorer Data took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.2608988285064697s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.020632505416870117s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 2.9802322387695312e-05s
Believability | Calculation of trust value for RKB Explorer Data took 7.867813110351562e-06s
INFO | --- Analysis for rkb_explorer_data took 2.7849843502044678s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.26923179626464844s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.0006875991821289062s
Extra | Recovery of all triples for ROCEEH Out of Africa Database (ROAD) took 29.98436999320984s
Performance | Total latancy measurement for ROCEEH Out of Africa Database (ROAD) took 0.49086976051330566s
Amount of data | Number of triples check for ROCEEH Out of Africa Database (ROAD) took 1.7799856662750244s
Interoperability | New terms check for ROCEEH Out of Africa Database (ROAD) took 1.5875513553619385s
Versatility | Languages check for ROCEEH Out of Africa Database (ROAD) took 5.031066179275513s
Interpretability | Number of blank nodes check for ROCEEH Out of Africa Database (ROAD) took 1.3961381912231445s
Interpretability | RDF structures check for ROCEEH Out of Africa Database (ROAD) took 0.09479403495788574s
Versatility | Serialization formats check for ROCEEH Out of Africa Database (ROAD) took 0.09450221061706543s
Availability | RDF dump link check for ROCEEH Out of Africa Database (ROAD) took 0.08461284637451172s
License | MR license check for ROCEEH Out of Africa Database (ROAD) took 0.07806658744812012s
License | HR license check for ROCEEH Out of Africa Database (ROAD) took 0.0955350399017334s
Amount of data | Number of property check for ROCEEH Out of Africa Database (ROAD) took 0.07771778106689453s
Understandability | Number of label check for ROCEEH Out of Africa Database (ROAD) took 0.08728504180908203s
Understandability | URI regex check for ROCEEH Out of Africa Database (ROAD) took 0.1774299144744873s
Understandability | Vocabs check for ROCEEH Out of Africa Database (ROAD) took 0.09323930740356445s
Verifiability | Authors check for ROCEEH Out of Africa Database (ROAD) took 0.08660054206848145s
Verifiability | Publishers check for ROCEEH Out of Africa Database (ROAD) took 0.08785104751586914s
Performance | Throughput check for ROCEEH Out of Africa Database (ROAD) took 10.545748949050903s
Amount of data | Check the number of entities for ROCEEH Out of Africa Database (ROAD) took 0.00010657310485839844s
Verifiability | Contribs. check for ROCEEH Out of Africa Database (ROAD) took 0.08517861366271973s
Interlinking | sameAs chians check for ROCEEH Out of Africa Database (ROAD) took 0.09348344802856445s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.08589434623718262s
Interlinking | skos check for ROCEEH Out of Africa Database (ROAD) took 0.0929408073425293s
Timeliness | dataset update frequency check for ROCEEH Out of Africa Database (ROAD) took 0.07862067222595215s
Currency | Creation date check for ROCEEH Out of Africa Database (ROAD) took 0.21462512016296387s
Currency | Modification date check for ROCEEH Out of Africa Database (ROAD) took 0.17179512977600098s
Rep.Conc. | URIs length for ROCEEH Out of Africa Database (ROAD) took 19.447473287582397s
Interoperability | New vocabularies check for ROCEEH Out of Africa Database (ROAD) took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for ROCEEH Out of Africa Database (ROAD) took 0.0972142219543457s
Accuracy | Check Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.09291768074035645s
Accuracy | Check Inverse Functional Property for ROCEEH Out of Africa Database (ROAD) took 0.08423471450805664s
Accuracy | Check Datatype consistency for ROCEEH Out of Africa Database (ROAD) took 3.767833709716797s
Consistency | Disjoint class check for ROCEEH Out of Africa Database (ROAD) took 0.0882866382598877s
Consistency | Check Misplaced properties for ROCEEH Out of Africa Database (ROAD) took 3.001716375350952s
Consistency | Check Ontology hijacking for ROCEEH Out of Africa Database (ROAD) took 6.920867681503296s
Consistency | Check Invalid usage of undefined classes for ROCEEH Out of Africa Database (ROAD) took 1.4375064373016357s
Consistency | Check Invalid usage of undefined properties for ROCEEH Out of Africa Database (ROAD) took 4.351368188858032s
Conciseness | Check Extensional conciseness for ROCEEH Out of Africa Database (ROAD) took 3.01896333694458s
Security | Sign check for ROCEEH Out of Africa Database (ROAD) took 0.08608555793762207s
Availability | Check URIs Dereferenciability for ROCEEH Out of Africa Database (ROAD) took 494.0201361179352s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 1.3093514442443848s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.02133488655090332s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 8.440017700195312e-05s
Interoperability | Check the re-using of existing vocabs for ROCEEH Out of Africa Database (ROAD) took 2.384185791015625e-06s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 8.344650268554688e-06s
INFO | --- Analysis for roceeh-road took 611.9213080406189s
Availability | SPARQL endpoint availability check for The Rosetta Project took 4.1484832763671875e-05s
Availability | VoID file availability check for The Rosetta Project took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.2544209957122803s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02126622200012207s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 3.170967102050781e-05s
Believability | Calculation of trust value for The Rosetta Project took 1.2636184692382812e-05s
INFO | --- Analysis for rosetta-project took 2.825148582458496s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 4.363059997558594e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.24029231071472168s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.020627498626708984s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 3.147125244140625e-05s
Believability | Calculation of trust value for ontology terrorist attack took 6.9141387939453125e-06s
INFO | --- Analysis for ROSHANI took 2.782478094100952s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 4.0531158447265625e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.27516698837280273s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 3.457069396972656e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 8.106231689453125e-06s
INFO | --- Analysis for ROSHANI_SAHU took 2.8817551136016846s
Availability | SPARQL endpoint availability check for x took 4.100799560546875e-05s
Availability | VoID file availability check for x took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for x took 0.26056718826293945s
Reputation | Calculation of the PageRank for x took 0.02066516876220703s
Interlinking | Calculation of Degree of Connection for x took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for x took 0.0007898807525634766s
Interlinking | Calculation of Clustering coefficient for x took 3.62396240234375e-05s
Believability | Calculation of trust value for x took 6.9141387939453125e-06s
INFO | --- Analysis for Rozprawa,_artykuł took 2.870542049407959s
Availability | SPARQL endpoint availability check for Rpm Find took 4.029273986816406e-05s
Availability | VoID file availability check for Rpm Find took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.25993943214416504s
Reputation | Calculation of the PageRank for Rpm Find took 0.020537137985229492s
Interlinking | Calculation of Degree of Connection for Rpm Find took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Rpm Find took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 3.123283386230469e-05s
Believability | Calculation of trust value for Rpm Find took 6.9141387939453125e-06s
INFO | --- Analysis for rpm_find took 2.8363261222839355s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.029273986816406e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.25304150581359863s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.0204315185546875s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.723403930664062e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 8.106231689453125e-06s
INFO | --- Analysis for rss-500-nif-ner-corpus took 2.783318281173706s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 6.461143493652344e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.2773873805999756s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.020877361297607422s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0008089542388916016s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 8.368492126464844e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 8.58306884765625e-06s
INFO | --- Analysis for rubentaelman took 2.811321496963501s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 3.981590270996094e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.26563024520874023s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.020585060119628906s
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.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.273124694824219e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 8.344650268554688e-06s
INFO | --- Analysis for rubenverborgh took 2.7925667762756348s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 4.100799560546875e-05s
Availability | VoID file availability check for Russian Universities Specialities took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.24669909477233887s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.020390748977661133s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.337860107421875e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 6.67572021484375e-06s
INFO | --- Analysis for russian-universities-specialities took 2.893444776535034s
Availability | SPARQL endpoint availability check for RuThes Cloud took 4.100799560546875e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.2499394416809082s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 3.0517578125e-05s
Believability | Calculation of trust value for RuThes Cloud took 6.67572021484375e-06s
INFO | --- Analysis for ruthes took 2.7905211448669434s
Availability | SPARQL endpoint availability check for RxNorm took 4.100799560546875e-05s
Availability | VoID file availability check for RxNorm took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for RxNorm took 0.24238038063049316s
Reputation | Calculation of the PageRank for RxNorm took 0.020177602767944336s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.0994415283203125e-05s
Believability | Calculation of trust value for RxNorm took 1.2159347534179688e-05s
INFO | --- Analysis for rxnorm took 2.806081771850586s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 4.1484832763671875e-05s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.26093506813049316s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.02073812484741211s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007109642028808594s
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 7.152557373046875e-06s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 2.886892795562744s
Availability | SPARQL endpoint availability check for SALDO took 4.100799560546875e-05s
Availability | VoID file availability check for SALDO took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for SALDO took 0.25925159454345703s
Reputation | Calculation of the PageRank for SALDO took 0.020421266555786133s
Interlinking | Calculation of Degree of Connection for SALDO took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SALDO took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SALDO took 2.6941299438476562e-05s
Believability | Calculation of trust value for SALDO took 7.152557373046875e-06s
INFO | --- Analysis for saldo took 2.810760259628296s
Availability | SPARQL endpoint availability check for SALDO-RDF took 3.981590270996094e-05s
Availability | VoID file availability check for SALDO-RDF took 0.00028634071350097656s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.2601938247680664s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.504753112792969e-05s
Believability | Calculation of trust value for SALDO-RDF took 8.344650268554688e-06s
INFO | --- Analysis for saldo-rdf took 2.786407232284546s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 4.124641418457031e-05s
Availability | VoID file availability check for SALDOM-RDF took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.26367974281311035s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.020628929138183594s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.600120544433594e-05s
Believability | Calculation of trust value for SALDOM-RDF took 7.3909759521484375e-06s
INFO | --- Analysis for saldom-rdf took 2.8830981254577637s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.076957702636719e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.2533836364746094s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.020731687545776367s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00011348724365234375s
Believability | Calculation of trust value for Salzburgerland DE took 7.867813110351562e-06s
INFO | --- Analysis for salzburgerland-com-de took 2.8357341289520264s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 4.029273986816406e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.24846363067626953s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.02066326141357422s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010275840759277344s
Believability | Calculation of trust value for Salzburgerland EN took 7.3909759521484375e-06s
INFO | --- Analysis for salzburgerland-com-en took 2.8238892555236816s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 4.076957702636719e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.24239754676818848s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.02071380615234375s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010609626770019531s
Believability | Calculation of trust value for Salzburgerland IT took 6.67572021484375e-06s
INFO | --- Analysis for salzburgerland-com-it took 2.769423484802246s
Availability | SPARQL endpoint availability check for sameAs.org took 4.029273986816406e-05s
Availability | VoID file availability check for sameAs.org took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.24238920211791992s
Reputation | Calculation of the PageRank for sameAs.org took 0.020725488662719727s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 3.170967102050781e-05s
Believability | Calculation of trust value for sameAs.org took 6.67572021484375e-06s
INFO | --- Analysis for sameas-org took 2.8590304851531982s
Availability | SPARQL endpoint availability check for sandrart.net took 4.220008850097656e-05s
Availability | VoID file availability check for sandrart.net took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.26108765602111816s
Reputation | Calculation of the PageRank for sandrart.net took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.794929504394531e-05s
Believability | Calculation of trust value for sandrart.net took 6.9141387939453125e-06s
INFO | --- Analysis for sandrart-net took 2.840815305709839s
Availability | SPARQL endpoint availability check for Taxons  took 4.076957702636719e-05s
Availability | VoID file availability check for Taxons  took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for Taxons  took 0.26491761207580566s
Reputation | Calculation of the PageRank for Taxons  took 0.02073526382446289s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007700920104980469s
Interlinking | Calculation of Clustering coefficient for Taxons  took 7.605552673339844e-05s
Believability | Calculation of trust value for Taxons  took 7.3909759521484375e-06s
INFO | --- Analysis for sandre took 2.8012566566467285s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 3.9577484130859375e-05s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.2537961006164551s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.020697593688964844s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 3.266334533691406e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.3828277587890625e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 2.8803255558013916s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 7.414817810058594e-05s
Availability | VoID file availability check for Santillana Guide Dataset took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.2547943592071533s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.02046370506286621s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 3.1948089599609375e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for santillana_guide_dataset took 2.7172133922576904s
Availability | SPARQL endpoint availability check for SATAR test  took 4.458427429199219e-05s
Availability | VoID file availability check for SATAR test  took 0.0002758502960205078s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.2743651866912842s
Reputation | Calculation of the PageRank for SATAR test  took 0.02059340476989746s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 3.0517578125e-05s
Believability | Calculation of trust value for SATAR test  took 6.9141387939453125e-06s
INFO | --- Analysis for SATAR_test took 2.8100781440734863s
Availability | SPARQL endpoint availability check for SCBG Data took 4.00543212890625e-05s
Availability | VoID file availability check for SCBG Data took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.26338958740234375s
Reputation | Calculation of the PageRank for SCBG Data took 0.020511388778686523s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 7.963180541992188e-05s
Believability | Calculation of trust value for SCBG Data took 7.62939453125e-06s
INFO | --- Analysis for SCBG-Data took 2.827256917953491s
Availability | SPARQL endpoint availability check for schema.org took 4.029273986816406e-05s
Availability | VoID file availability check for schema.org took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for schema.org took 0.2412269115447998s
Reputation | Calculation of the PageRank for schema.org took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for schema.org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for schema.org took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.5762786865234375e-05s
Believability | Calculation of trust value for schema.org took 1.1920928955078125e-05s
INFO | --- Analysis for schema-org took 2.8878183364868164s
Availability | SPARQL endpoint availability check for Schemantra took 5.602836608886719e-05s
Availability | VoID file availability check for Schemantra took 0.0002300739288330078s
Completeness | Calculation of interlinking completeness for Schemantra took 0.2670924663543701s
Reputation | Calculation of the PageRank for Schemantra took 0.020581483840942383s
Interlinking | Calculation of Degree of Connection for Schemantra took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Schemantra took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Schemantra took 3.314018249511719e-05s
Believability | Calculation of trust value for Schemantra took 7.3909759521484375e-06s
INFO | --- Analysis for Schemantra took 2.8866569995880127s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 4.029273986816406e-05s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.25934839248657227s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020708560943603516s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.457069396972656e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.2159347534179688e-05s
INFO | --- Analysis for schemapedia took 2.8054373264312744s
Availability | SPARQL endpoint availability check for scholarlydata took 6.532669067382812e-05s
Availability | VoID file availability check for scholarlydata took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.25379109382629395s
Reputation | Calculation of the PageRank for scholarlydata took 0.02022552490234375s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.0279159545898438e-05s
Believability | Calculation of trust value for scholarlydata took 8.344650268554688e-06s
INFO | --- Analysis for scholarlydata took 2.813039541244507s
Availability | SPARQL endpoint availability check for Scholarometer took 4.1961669921875e-05s
Availability | VoID file availability check for Scholarometer took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.25002169609069824s
Reputation | Calculation of the PageRank for Scholarometer took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0006766319274902344s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.463859558105469e-05s
Believability | Calculation of trust value for Scholarometer took 7.3909759521484375e-06s
INFO | --- Analysis for scholarometer took 2.836700439453125s
Availability | SPARQL endpoint availability check for Science Commons took 5.435943603515625e-05s
Availability | VoID file availability check for Science Commons took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Science Commons took 0.27891063690185547s
Reputation | Calculation of the PageRank for Science Commons took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Science Commons took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Science Commons took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Science Commons took 3.147125244140625e-05s
Believability | Calculation of trust value for Science Commons took 7.867813110351562e-06s
INFO | --- Analysis for science_commons took 2.8578171730041504s
Availability | SPARQL endpoint availability check for ScienceWise took 4.506111145019531e-05s
Availability | VoID file availability check for ScienceWise took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.2607908248901367s
Reputation | Calculation of the PageRank for ScienceWise took 0.020670413970947266s
Interlinking | Calculation of Degree of Connection for ScienceWise took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ScienceWise took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 3.266334533691406e-05s
Believability | Calculation of trust value for ScienceWise took 7.3909759521484375e-06s
INFO | --- Analysis for sciencewise took 2.9061107635498047s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 4.00543212890625e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.2745370864868164s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.020411252975463867s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.9802322387695312e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.1205673217773438e-05s
INFO | --- Analysis for scoreboard took 2.8267629146575928s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 4.3392181396484375e-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.0002498626708984375s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.26624488830566406s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.020380735397338867s
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.0013580322265625e-05s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.9325485229492188e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.106231689453125e-06s
INFO | --- Analysis for SDDEC took 2.791471004486084s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 5.340576171875e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.253368616104126s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020443201065063477s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 3.123283386230469e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 7.3909759521484375e-06s
INFO | --- Analysis for SDG took 2.7820680141448975s
Availability | SPARQL endpoint availability check for sears.com took 3.9577484130859375e-05s
Availability | VoID file availability check for sears.com took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for sears.com took 0.23752808570861816s
Reputation | Calculation of the PageRank for sears.com took 0.020589113235473633s
Interlinking | Calculation of Degree of Connection for sears.com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for sears.com took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.914138793945312e-05s
Believability | Calculation of trust value for sears.com took 1.2874603271484375e-05s
INFO | --- Analysis for sears took 2.757646083831787s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 4.1484832763671875e-05s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.26634907722473145s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020749807357788086s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007221698760986328s
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.1920928955078125e-05s
INFO | --- Analysis for sec-rdfabout took 2.8954615592956543s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.0003523826599121094s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.2787666320800781s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.020778417587280273s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 8.726119995117188e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 3.170967102050781e-05s
INFO | --- Analysis for secold took 2.9548933506011963s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 4.029273986816406e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.237349271774292s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.7179718017578125e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 9.059906005859375e-06s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 2.8367369174957275s
Availability | SPARQL endpoint availability check for semanlink took 4.029273986816406e-05s
Availability | VoID file availability check for semanlink took 0.0002276897430419922s
Completeness | Calculation of interlinking completeness for semanlink took 0.2668116092681885s
Reputation | Calculation of the PageRank for semanlink took 0.02065110206604004s
Interlinking | Calculation of Degree of Connection for semanlink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for semanlink took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00014257431030273438s
Believability | Calculation of trust value for semanlink took 7.152557373046875e-06s
INFO | --- Analysis for semanlink took 2.882582187652588s
Availability | SPARQL endpoint availability check for Semantic Library took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Library took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.2610752582550049s
Reputation | Calculation of the PageRank for Semantic Library took 0.0207672119140625s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 3.147125244140625e-05s
Believability | Calculation of trust value for Semantic Library took 7.62939453125e-06s
INFO | --- Analysis for semantic-library took 2.8449196815490723s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 4.0531158447265625e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.271726131439209s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020629405975341797s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.123283386230469e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 7.152557373046875e-06s
INFO | --- Analysis for semantic-profiling-network took 2.826820135116577s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 4.124641418457031e-05s
Availability | VoID file availability check for Semantic Universe Data took 0.00022482872009277344s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.2631042003631592s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.2874603271484375e-05s
INFO | --- Analysis for semantic-universe took 2.853344440460205s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 3.933906555175781e-05s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.00035190582275390625s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.2527031898498535s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011730194091796875s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.33514404296875e-05s
INFO | --- Analysis for semantic-web-dog-food took 2.825646162033081s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 6.914138793945312e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.2346038818359375s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020715713500976562s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.482269287109375e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 1.2874603271484375e-05s
INFO | --- Analysis for semantic-web-grundlagen took 2.7601215839385986s
Availability | SPARQL endpoint availability check for semantic-web-journal took 5.53131103515625e-05s
Availability | VoID file availability check for semantic-web-journal took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.2641913890838623s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.02077341079711914s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.170967102050781e-05s
Believability | Calculation of trust value for semantic-web-journal took 1.2636184692382812e-05s
INFO | --- Analysis for semantic-web-journal took 2.876960277557373s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.172325134277344e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.2562553882598877s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 8.96453857421875e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 7.3909759521484375e-06s
INFO | --- Analysis for semantic-xbrl took 2.902806043624878s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.029273986816406e-05s
Availability | VoID file availability check for Semantic Bible took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.2541170120239258s
Reputation | Calculation of the PageRank for Semantic Bible took 0.020744800567626953s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 3.0040740966796875e-05s
Believability | Calculation of trust value for Semantic Bible took 1.3589859008789062e-05s
INFO | --- Analysis for semantic_bible took 2.9242420196533203s
Availability | SPARQL endpoint availability check for SemanticQuran took 5.793571472167969e-05s
Availability | VoID file availability check for SemanticQuran took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.24780845642089844s
Reputation | Calculation of the PageRank for SemanticQuran took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 6.866455078125e-05s
Believability | Calculation of trust value for SemanticQuran took 7.3909759521484375e-06s
INFO | --- Analysis for semanticquran took 2.8845324516296387s
Availability | SPARQL endpoint availability check for SemanticTweet took 4.0531158447265625e-05s
Availability | VoID file availability check for SemanticTweet took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.27257800102233887s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020531654357910156s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.459785461425781e-05s
Believability | Calculation of trust value for SemanticTweet took 7.62939453125e-06s
INFO | --- Analysis for semantictweet took 2.8260498046875s
Availability | SPARQL endpoint availability check for semanticweb.org took 4.029273986816406e-05s
Availability | VoID file availability check for semanticweb.org took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.24734067916870117s
Reputation | Calculation of the PageRank for semanticweb.org took 0.020606517791748047s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 4.1484832763671875e-05s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.939338684082031e-05s
Believability | Calculation of trust value for semanticweb.org took 6.9141387939453125e-06s
INFO | --- Analysis for semanticweb-org took 2.8528501987457275s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 3.838539123535156e-05s
Availability | VoID file availability check for Semantic CrunchBase took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.24631476402282715s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020485877990722656s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 6.67572021484375e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 6.9141387939453125e-06s
INFO | --- Analysis for semsol-crunchbase took 2.8363234996795654s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 7.081031799316406e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.24327516555786133s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020619869232177734s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 2.9325485229492188e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 8.821487426757812e-06s
INFO | --- Analysis for sensores-de-intellidomo took 2.817429304122925s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 4.100799560546875e-05s
Availability | VoID file availability check for SentimentWortschatz took 0.000244140625s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.2437121868133545s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.1961669921875e-05s
Believability | Calculation of trust value for SentimentWortschatz took 6.67572021484375e-06s
INFO | --- Analysis for sentiws took 2.844367742538452s
Availability | SPARQL endpoint availability check for seoul-bike-data took 4.029273986816406e-05s
Availability | VoID file availability check for seoul-bike-data took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.23948097229003906s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 3.0279159545898438e-05s
Believability | Calculation of trust value for seoul-bike-data took 7.867813110351562e-06s
INFO | --- Analysis for seoul-bike-data took 2.784799575805664s
Availability | SPARQL endpoint availability check for Serendipity took 4.673004150390625e-05s
Availability | VoID file availability check for Serendipity took 0.0003337860107421875s
Completeness | Calculation of interlinking completeness for Serendipity took 0.2825052738189697s
Reputation | Calculation of the PageRank for Serendipity took 0.023215532302856445s
Interlinking | Calculation of Degree of Connection for Serendipity took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Serendipity took 0.0012063980102539062s
Interlinking | Calculation of Clustering coefficient for Serendipity took 9.083747863769531e-05s
Believability | Calculation of trust value for Serendipity took 7.62939453125e-06s
INFO | --- Analysis for serendipity took 2.8865303993225098s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 4.220008850097656e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.25677967071533203s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.02072453498840332s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 3.1948089599609375e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 6.67572021484375e-06s
INFO | --- Analysis for Sherry_Wine took 2.8567302227020264s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.172325134277344e-05s
Availability | VoID file availability check for Sherry Wine took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.26571226119995117s
Reputation | Calculation of the PageRank for Sherry Wine took 0.020775556564331055s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 3.170967102050781e-05s
Believability | Calculation of trust value for Sherry Wine took 7.867813110351562e-06s
INFO | --- Analysis for Sherry_Wine_ took 2.856450319290161s
Availability | SPARQL endpoint availability check for Shoah victims? names took 4.363059997558594e-05s
Availability | VoID file availability check for Shoah victims? names took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.25523924827575684s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.021337509155273438s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0006806850433349609s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 4.00543212890625e-05s
Believability | Calculation of trust value for Shoah victims? names took 6.198883056640625e-06s
INFO | --- Analysis for shoah-victims-names took 2.798581123352051s
Availability | SPARQL endpoint availability check for Person took 4.076957702636719e-05s
Availability | VoID file availability check for Person took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for Person took 0.2627739906311035s
Reputation | Calculation of the PageRank for Person took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Person took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Person took 0.0006799697875976562s
Interlinking | Calculation of Clustering coefficient for Person took 3.0040740966796875e-05s
Believability | Calculation of trust value for Person took 1.1920928955078125e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.814227342605591s
Availability | SPARQL endpoint availability check for Jishnu Raghavan (1976-2016) took 4.0531158447265625e-05s
Availability | VoID file availability check for Jishnu Raghavan (1976-2016) took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.25451040267944336s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.02050161361694336s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007317066192626953s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 3.0517578125e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 7.867813110351562e-06s
INFO | --- Analysis for Shutterstock took 2.906867504119873s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.00543212890625e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00030422210693359375s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.2732088565826416s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.020778656005859375s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 3.790855407714844e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 1.3113021850585938e-05s
INFO | --- Analysis for simile_data_collection took 2.8263978958129883s
Availability | SPARQL endpoint availability check for SIMPLE took 4.076957702636719e-05s
Availability | VoID file availability check for SIMPLE took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.2369990348815918s
Reputation | Calculation of the PageRank for SIMPLE took 0.020493507385253906s
Interlinking | Calculation of Degree of Connection for SIMPLE took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 4.0531158447265625e-05s
Believability | Calculation of trust value for SIMPLE took 7.867813110351562e-06s
INFO | --- Analysis for simple took 2.803443431854248s
Availability | SPARQL endpoint availability check for SITC-V4 took 4.100799560546875e-05s
Availability | VoID file availability check for SITC-V4 took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.27384138107299805s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020513296127319336s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.552436828613281e-05s
Believability | Calculation of trust value for SITC-V4 took 8.58306884765625e-06s
INFO | --- Analysis for sitc-v4 took 2.778913736343384s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.0531158447265625e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.25069212913513184s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 4.220008850097656e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 7.3909759521484375e-06s
INFO | --- Analysis for sli_galnet_rdf took 2.856325626373291s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 4.100799560546875e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.27416205406188965s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.02039027214050293s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 3.24249267578125e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 1.1920928955078125e-05s
INFO | --- Analysis for slideshare2rdf took 2.884732723236084s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 4.506111145019531e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.26509761810302734s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.020659685134887695s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 3.147125244140625e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 7.867813110351562e-06s
INFO | --- Analysis for slidewiki-rdf-sparql took 2.9692065715789795s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 9.435863018035889s
Availability | VoID file availability check for Linked Stage Graph took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.2691690921783447s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.020414113998413086s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 5.1021575927734375e-05s
Believability | Calculation of trust value for Linked Stage Graph took 7.3909759521484375e-06s
INFO | --- Analysis for slod took 18.92363142967224s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 4.124641418457031e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2648775577545166s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020697832107543945s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 3.170967102050781e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 7.152557373046875e-06s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.8555188179016113s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 4.029273986816406e-05s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.2742471694946289s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 9.274482727050781e-05s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Smart_POI_dataset took 2.954345226287842s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 4.410743713378906e-05s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.2738955020904541s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.020611286163330078s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.8623809814453125e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 6.9141387939453125e-06s
INFO | --- Analysis for smartlink took 2.8852975368499756s
Availability | SPARQL endpoint availability check for SNIK took 4.029273986816406e-05s
Availability | VoID file availability check for SNIK took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for SNIK took 0.26180028915405273s
Reputation | Calculation of the PageRank for SNIK took 0.02052593231201172s
Interlinking | Calculation of Degree of Connection for SNIK took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.200241088867188e-05s
Believability | Calculation of trust value for SNIK took 9.059906005859375e-06s
INFO | --- Analysis for snik took 2.8333897590637207s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 4.029273986816406e-05s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.27338099479675293s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.020798921585083008s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.123283386230469e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 7.3909759521484375e-06s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 2.848581075668335s
Availability | SPARQL endpoint availability check for SocialLink took 4.1484832763671875e-05s
Availability | VoID file availability check for SocialLink took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for SocialLink took 0.23853588104248047s
Reputation | Calculation of the PageRank for SocialLink took 0.02129817008972168s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0009052753448486328s
Interlinking | Calculation of Clustering coefficient for SocialLink took 9.489059448242188e-05s
Believability | Calculation of trust value for SocialLink took 7.152557373046875e-06s
INFO | --- Analysis for SocialLink took 2.857208728790283s
Availability | SPARQL endpoint availability check for SocialLink took 4.0531158447265625e-05s
Availability | VoID file availability check for SocialLink took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for SocialLink took 0.26171326637268066s
Reputation | Calculation of the PageRank for SocialLink took 0.020602941513061523s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.147125244140625e-05s
Believability | Calculation of trust value for SocialLink took 8.344650268554688e-06s
INFO | --- Analysis for sociallink took 2.836413860321045s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 4.100799560546875e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.27393388748168945s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.02045750617980957s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.0994415283203125e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 7.3909759521484375e-06s
INFO | --- Analysis for SocialRoles took 2.845953941345215s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.2645106315612793s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020713090896606445s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 9.083747863769531e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for socialsemweb-thesaurus took 2.7528467178344727s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.601478576660156e-05s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.26343798637390137s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.147125244140625e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for Soil_maps took 2.859900951385498s
Availability | SPARQL endpoint availability check for terrorrist ontology took 4.124641418457031e-05s
Availability | VoID file availability check for terrorrist ontology took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.26571059226989746s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 2.8133392333984375e-05s
Believability | Calculation of trust value for terrorrist ontology took 7.152557373046875e-06s
INFO | --- Analysis for somya_omer took 2.9166555404663086s
Availability | SPARQL endpoint availability check for Sonclubcx took 5.078315734863281e-05s
Availability | VoID file availability check for Sonclubcx took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.24662113189697266s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020835161209106445s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.3113021850585938e-05s
Believability | Calculation of trust value for Sonclubcx took 7.152557373046875e-06s
INFO | --- Analysis for sonclubcx took 2.759556293487549s
Availability | SPARQL endpoint availability check for SORS took 4.9114227294921875e-05s
Availability | VoID file availability check for SORS took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for SORS took 0.24478721618652344s
Reputation | Calculation of the PageRank for SORS took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for SORS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SORS took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for SORS took 4.696846008300781e-05s
Believability | Calculation of trust value for SORS took 7.3909759521484375e-06s
INFO | --- Analysis for sors took 2.8118696212768555s
Availability | SPARQL endpoint availability check for Soudy České republiky took 5.245208740234375e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.26764535903930664s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.9087066650390625e-05s
Believability | Calculation of trust value for Soudy České republiky took 7.3909759521484375e-06s
INFO | --- Analysis for soudy--esk--republiky took 2.8462860584259033s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 4.220008850097656e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.00025844573974609375s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.27521276473999023s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.020642757415771484s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 9.72747802734375e-05s
Believability | Calculation of trust value for southampton-ac-uk took 7.867813110351562e-06s
INFO | --- Analysis for southampton-ac-uk took 2.888986587524414s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 6.842613220214844e-05s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.26465487480163574s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 3.0279159545898438e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 7.3909759521484375e-06s
INFO | --- Analysis for southampton-ac-uk-apps took 2.8454248905181885s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 4.172325134277344e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.24976515769958496s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.021499156951904297s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.751319885253906e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 7.152557373046875e-06s
INFO | --- Analysis for southampton-ecs-eprints took 2.849046468734741s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 4.1484832763671875e-05s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.24440646171569824s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.023445844650268555s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0013439655303955078s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 4.315376281738281e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 7.3909759521484375e-06s
INFO | --- Analysis for spanish-linguistic-datasets took 2.7874813079833984s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 4.1484832763671875e-05s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.24716973304748535s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.02069830894470215s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.649162292480469e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 7.62939453125e-06s
INFO | --- Analysis for sparql-endpoint-status took 2.8794612884521484s
Availability | SPARQL endpoint availability check for SPC publikovaná SÚKL took 4.100799560546875e-05s
Availability | VoID file availability check for SPC publikovaná SÚKL took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.2680838108062744s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.218650817871094e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 7.62939453125e-06s
INFO | --- Analysis for spc-publikovan--s-kl took 2.8411717414855957s
Availability | SPARQL endpoint availability check for SPQR took 4.0531158447265625e-05s
Availability | VoID file availability check for SPQR took 0.00025463104248046875s
Completeness | Calculation of interlinking completeness for SPQR took 0.2694211006164551s
Reputation | Calculation of the PageRank for SPQR took 0.020654678344726562s
Interlinking | Calculation of Degree of Connection for SPQR took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.218650817871094e-05s
Believability | Calculation of trust value for SPQR took 8.58306884765625e-06s
INFO | --- Analysis for spqr took 2.78775954246521s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 4.0531158447265625e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.2438662052154541s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.440017700195312e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 8.821487426757812e-06s
INFO | --- Analysis for springernaturescigraph took 2.9020063877105713s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 4.3392181396484375e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.24298906326293945s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Syntactic Reference Corpus of Medieval French (SRCMF) took 3.266334533691406e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 6.9141387939453125e-06s
INFO | --- Analysis for srcmf took 2.856708288192749s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 4.220008850097656e-05s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.0003409385681152344s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.2596101760864258s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.02059030532836914s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 4.601478576660156e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 6.9141387939453125e-06s
INFO | --- Analysis for ssf took 2.878964900970459s
Availability | SPARQL endpoint availability check for SSF took 4.1961669921875e-05s
Availability | VoID file availability check for SSF took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for SSF took 0.2572925090789795s
Reputation | Calculation of the PageRank for SSF took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for SSF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SSF took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for SSF took 2.9087066650390625e-05s
Believability | Calculation of trust value for SSF took 8.58306884765625e-06s
INFO | --- Analysis for ssf-lexicon took 2.8378729820251465s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 4.57763671875e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.26457643508911133s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for St. Andrews University Resource Lists took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for St. Andrews University Resource Lists took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.337860107421875e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 7.867813110351562e-06s
INFO | --- Analysis for st-andrews-resource-lists took 2.8348381519317627s
Availability | SPARQL endpoint availability check for STAC took 4.100799560546875e-05s
Availability | VoID file availability check for STAC took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for STAC took 0.2732973098754883s
Reputation | Calculation of the PageRank for STAC took 0.02055954933166504s
Interlinking | Calculation of Degree of Connection for STAC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for STAC took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for STAC took 3.0040740966796875e-05s
Believability | Calculation of trust value for STAC took 7.62939453125e-06s
INFO | --- Analysis for stac took 2.900991201400757s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 4.649162292480469e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.2797873020172119s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020607471466064453s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 3.7670135498046875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 7.3909759521484375e-06s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 2.8796029090881348s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 4.1484832763671875e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.25554466247558594s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.337860107421875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 7.62939453125e-06s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 2.8313233852386475s
Availability | SPARQL endpoint availability check for Stammbuch took 4.029273986816406e-05s
Availability | VoID file availability check for Stammbuch took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.27587199211120605s
Reputation | Calculation of the PageRank for Stammbuch took 0.020480632781982422s
Interlinking | Calculation of Degree of Connection for Stammbuch took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Stammbuch took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.9325485229492188e-05s
Believability | Calculation of trust value for Stammbuch took 7.62939453125e-06s
INFO | --- Analysis for Stammbuch took 2.8698275089263916s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 4.076957702636719e-05s
Availability | VoID file availability check for statistics.data.gov.uk took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.2626669406890869s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020626306533813477s
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.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010156631469726562s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.1682510375976562e-05s
INFO | --- Analysis for statistics-data-gov-uk took 3.03136944770813s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 4.172325134277344e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.2579493522644043s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.02060103416442871s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.9802322387695312e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 7.62939453125e-06s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 2.8280951976776123s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.00024700164794921875s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.27190542221069336s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.02082204818725586s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00012803077697753906s
Believability | Calculation of trust value for statusnet-1w6-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-1w6-org took 2.804454803466797s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.24670720100402832s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.020685434341430664s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-20100-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-20100-org took 3.040198564529419s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 7.104873657226562e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.24686384201049805s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.751091957092285s
Availability | SPARQL endpoint availability check for statusnet-atari-frosch-de took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-atari-frosch-de took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.27548694610595703s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020730018615722656s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0006952285766601562s
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 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 2.8447656631469727s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.00027632713317871094s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.27298998832702637s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020566940307617188s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 9.131431579589844e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-belfalas-org took 2.875192165374756s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 4.649162292480469e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.26977086067199707s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.02068328857421875s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.0001068115234375s
Believability | Calculation of trust value for statusnet-bka-li took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-bka-li took 2.9047162532806396s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.2650623321533203s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.020319461822509766s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.6716461181640625e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-bonifaz-ec took 2.8330636024475098s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.24646759033203125s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.553794860839844e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-ced117-net took 2.7423601150512695s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.0003032684326171875s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.26315855979919434s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.9114227294921875e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-chickenkiller-com took 2.8409693241119385s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.2520449161529541s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.020178794860839844s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00010919570922851562s
Believability | Calculation of trust value for statusnet-chromic-org took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-chromic-org took 2.885714292526245s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.2746312618255615s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020612001419067383s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.796287536621094e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-cooleysekula-net took 2.775585651397705s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.26555514335632324s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.020292997360229492s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-coreyavis-com took 2.8124582767486572s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.2419586181640625s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020193815231323242s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-datenfahrt-org took 2.8589863777160645s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 8.273124694824219e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.27185940742492676s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.02033543586730957s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 9.965896606445312e-05s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 2.8348746299743652s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.0002453327178955078s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.2503378391265869s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 6.246566772460938e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.7754642963409424s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.261502742767334s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.020557880401611328s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 5.0067901611328125e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-doomicile-de took 2.8412115573883057s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 4.9114227294921875e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.24942326545715332s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020354270935058594s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-dtdns-net took 2.882202386856079s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.2858741283416748s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020452260971069336s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.3855438232421875e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-equestriarp-net took 2.8073854446411133s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.23771405220031738s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.02052164077758789s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0007367134094238281s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 7.009506225585938e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-exdc-net took 2.7880446910858154s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.00023174285888671875s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.26102304458618164s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.020708560943603516s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.322166442871094e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-fcac-com took 2.7658426761627197s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.2397325038909912s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-fcestrada-com took 2.821712017059326s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.2647547721862793s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.021422147750854492s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0009052753448486328s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.0002155303955078125s
Believability | Calculation of trust value for statusnet-fragdev-com took 9.298324584960938e-06s
INFO | --- Analysis for statusnet-fragdev-com took 2.867319107055664s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.24716663360595703s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.02088189125061035s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.43865966796875e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-freelish-us took 2.8537564277648926s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.2469768524169922s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.020516395568847656s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-gegeweb-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-gegeweb-org took 2.7863128185272217s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.2619514465332031s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.020282268524169922s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.67572021484375e-05s
Believability | Calculation of trust value for statusnet-glou-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-glou-org took 2.854757308959961s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 6.318092346191406e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.27422571182250977s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.00012373924255371094s
Believability | Calculation of trust value for statusnet-gomertronic-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-gomertronic-com took 2.8650567531585693s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.28908324241638184s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.02082681655883789s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010228157043457031s
Believability | Calculation of trust value for statusnet-hackerposse-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-hackerposse-com took 2.9301986694335938s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.2531614303588867s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.02144026756286621s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.839897155761719e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-hii-co-il took 2.8410513401031494s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 8.0108642578125e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.0002543926239013672s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.25267505645751953s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020565271377563477s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007677078247070312s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 9.226799011230469e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 2.8069589138031006s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.0002689361572265625s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.24564456939697266s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.0213167667388916s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.000888824462890625s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 7.200241088867188e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 8.821487426757812e-06s
INFO | --- Analysis for statusnet-imirhil-fr took 2.819272518157959s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.00028252601623535156s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.2646443843841553s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.02121138572692871s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0010840892791748047s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 4.6253204345703125e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-integralblue-com took 2.838754892349243s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.2733759880065918s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 7.62939453125e-06s
INFO | --- Analysis for statusnet-johndrinkwater-name took 2.78987979888916s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.0002899169921875s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.26044607162475586s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020394563674926758s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.0001125335693359375s
Believability | Calculation of trust value for statusnet-jonkman-ca took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-jonkman-ca took 2.86810040473938s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.27619409561157227s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020566701889038086s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.489059448242188e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 2.8970391750335693s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.253481388092041s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.020224332809448242s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.601478576660156e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 2.8427395820617676s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.2790977954864502s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02041769027709961s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.981590270996094e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-kenzoid-com took 2.843053102493286s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 4.482269287109375e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.25051236152648926s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 8.58306884765625e-06s
INFO | --- Analysis for statusnet-keuser-fr took 2.8324134349823s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 5.412101745605469e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0005376338958740234s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.2440173625946045s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.02025890350341797s
Interlinking | Calculation of Degree of Connection for statusnet-ldn-fai-net took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for statusnet-ldn-fai-net took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 4.57763671875e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 2.848478078842163s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.25075769424438477s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.02028942108154297s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 5.793571472167969e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-lebsanft-org took 2.8578360080718994s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.2664022445678711s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020299911499023438s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 8.893013000488281e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.7905659675598145s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.2746315002441406s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011229515075683594s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.9283337593078613s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.2615787982940674s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ludost-net took 2.8312339782714844s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.26025390625s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020456314086914062s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 0.00010347366333007812s
Believability | Calculation of trust value for statusnet-lydiastench-com took 7.62939453125e-06s
INFO | --- Analysis for statusnet-lydiastench-com took 2.8967652320861816s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.00027823448181152344s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.2481701374053955s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02064824104309082s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-m-kuttner-com took 2.771652936935425s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 5.793571472167969e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.2536349296569824s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.0202944278717041s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014781951904296875s
Believability | Calculation of trust value for statusnet-macno-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-macno-org took 2.7466983795166016s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.00026154518127441406s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.26482510566711426s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.103515625e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 2.7423689365386963s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.0002892017364501953s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.25832700729370117s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.020840167999267578s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0008065700531005859s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 8.678436279296875e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-maymay-net took 2.8752777576446533s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0002605915069580078s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.26578712463378906s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.00015544891357421875s
Believability | Calculation of trust value for statusnet-morphtown-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-morphtown-de took 2.863525867462158s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.27314257621765137s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.465217590332031e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-mrblog-nl took 2.780494451522827s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0002636909484863281s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.22785353660583496s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.364418029785156e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-mulestable-net took 2.7388949394226074s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.256716251373291s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.020598411560058594s
Interlinking | Calculation of Degree of Connection for statusnet-my-status-tk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-my-status-tk took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.173683166503906e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-my-status-tk took 2.7705748081207275s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.2751927375793457s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00010514259338378906s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 6.67572021484375e-06s
INFO | --- Analysis for statusnet-opensim-chat-eu took 2.82598614692688s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.24470996856689453s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020296335220336914s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.53131103515625e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.8951525688171387s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.25603294372558594s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.02047276496887207s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 5.936622619628906e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-otbm-fr took 2.812886953353882s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.24343180656433105s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 8.320808410644531e-05s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.853968381881714s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.000263214111328125s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.2649714946746826s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.6253204345703125e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-panda-id-au took 2.8622891902923584s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.2603902816772461s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.393692016601562e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-piana-eu took 2.835149049758911s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.0002639293670654297s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.24993467330932617s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.02140665054321289s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0007917881011962891s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 2.814249038696289s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0002791881561279297s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.25519299507141113s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.020862579345703125s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.00022983551025390625s
Believability | Calculation of trust value for statusnet-postblue-info took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-postblue-info took 2.7656185626983643s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.24054551124572754s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02021312713623047s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.341934204101562e-05s
Believability | Calculation of trust value for statusnet-progval-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-progval-net took 2.8419365882873535s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.24857354164123535s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020403146743774414s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00010943412780761719s
Believability | Calculation of trust value for statusnet-qdnx-org took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-qdnx-org took 2.8443703651428223s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.00031685829162597656s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.2647285461425781s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020422935485839844s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.008148193359375e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-qth-fr took 2.909034490585327s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.000247955322265625s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.2757444381713867s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.00021409988403320312s
Believability | Calculation of trust value for statusnet-quitter-se took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-quitter-se took 2.9022634029388428s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0002589225769042969s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.26591920852661133s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.02116847038269043s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.000102996826171875s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.3589859008789062e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 2.875410318374634s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.982948303222656e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.26604533195495605s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020287036895751953s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.316734313964844e-05s
Believability | Calculation of trust value for statusnet-recit-org took 6.198883056640625e-06s
INFO | --- Analysis for statusnet-recit-org took 2.8116726875305176s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0002617835998535156s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.26392412185668945s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00014901161193847656s
Believability | Calculation of trust value for statusnet-russwurm-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-russwurm-org took 2.807457208633423s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.24881243705749512s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.02067089080810547s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.416175842285156e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-samnoble-org took 2.9140403270721436s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.2581362724304199s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-schiessle-org took 2.864673137664795s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.23811864852905273s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.751319885253906e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-scoffoni-net took 2.813558340072632s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 7.152557373046875e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.25393223762512207s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.02077960968017578s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.198883056640625e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-sebseb01-net took 2.8062729835510254s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.24392938613891602s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.02144312858581543s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 8.273124694824219e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-shnoulle-net took 2.849853038787842s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.2642698287963867s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.020212650299072266s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021028518676757812s
Believability | Calculation of trust value for statusnet-skilledtests-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-skilledtests-com took 2.9028525352478027s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.00026607513427734375s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.24462461471557617s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010204315185546875s
Believability | Calculation of trust value for statusnet-somsants-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-somsants-net took 2.855038642883301s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0005347728729248047s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.269317626953125s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.0201723575592041s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00014972686767578125s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-soucy-cc took 2.870661497116089s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.2720203399658203s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-spip-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-spip-org took 2.9123318195343018s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.363059997558594e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0005691051483154297s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.24323272705078125s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.437301635742188e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-spraci-org took 2.7973897457122803s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.2889137268066406s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-ssweeny-net took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-ssweeny-net took 2.8574106693267822s
Availability | SPARQL endpoint availability check for statusnet-status-net took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-status-net took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.26603198051452637s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020511865615844727s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.00022125244140625s
Believability | Calculation of trust value for statusnet-status-net took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-status-net took 2.822028160095215s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.00026488304138183594s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.2589840888977051s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.626678466796875e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 7.3909759521484375e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 2.8055999279022217s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.26721835136413574s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.02095937728881836s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.369850158691406e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 2.8596882820129395s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.0006864070892333984s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.259366512298584s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.02103900909423828s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0009436607360839844s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001456737518310547s
Believability | Calculation of trust value for statusnet-thelovebug-org took 8.344650268554688e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 2.869213342666626s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.24910926818847656s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.021486520767211914s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.390975952148438e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-thornton2-com took 2.864133358001709s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.2556266784667969s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020368099212646484s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010538101196289062s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-timttmy-co-uk took 2.779747724533081s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 0.00011444091796875s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.25517964363098145s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.020470380783081055s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 4.2438507080078125e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-tl1n-com took 2.7696268558502197s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.00025773048400878906s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.27459049224853516s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020966291427612305s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0007665157318115234s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 7.033348083496094e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 7.62939453125e-06s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 2.8923635482788086s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.26537585258483887s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020233869552612305s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.0007236003875732422s
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 6.9141387939453125e-06s
INFO | --- Analysis for statusnet-uni-siegen-de took 2.9028940200805664s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.00048828125s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.26125097274780273s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 2.8133392333984375e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 7.867813110351562e-06s
INFO | --- Analysis for steak took 2.809011220932007s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 5.698204040527344e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.00028824806213378906s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.2598106861114502s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.650520324707031e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.2159347534179688e-05s
INFO | --- Analysis for stitch-rameau took 2.873668670654297s
Availability | SPARQL endpoint availability check for Stone Tech Square took 8.58306884765625e-05s
Availability | VoID file availability check for Stone Tech Square took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.2529585361480713s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.020418643951416016s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.2874603271484375e-05s
Believability | Calculation of trust value for Stone Tech Square took 7.152557373046875e-06s
INFO | --- Analysis for stone-tech-square-data took 2.8642754554748535s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 4.172325134277344e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.2422943115234375s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.020810365676879883s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0006787776947021484s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 2.9325485229492188e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 7.3909759521484375e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 3.370521306991577s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 4.124641418457031e-05s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.2623157501220703s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.020471572875976562s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.00011348724365234375s
Believability | Calculation of trust value for STW Thesaurus for Economics took 6.4373016357421875e-06s
INFO | --- Analysis for stw-thesaurus-for-economics took 2.8601715564727783s
Availability | SPARQL endpoint availability check for SudershanTech took 5.936622619628906e-05s
Availability | VoID file availability check for SudershanTech took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.2610323429107666s
Reputation | Calculation of the PageRank for SudershanTech took 0.020479917526245117s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.600120544433594e-05s
Believability | Calculation of trust value for SudershanTech took 6.67572021484375e-06s
INFO | --- Analysis for SudershanTech took 2.8002583980560303s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 4.1961669921875e-05s
Availability | VoID file availability check for Sudoc bibliographic data took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.25345587730407715s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.0203402042388916s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.6253204345703125e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 8.344650268554688e-06s
INFO | --- Analysis for sudocfr took 2.8616726398468018s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 4.1961669921875e-05s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.0002663135528564453s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.2653501033782959s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.772445678710938e-05s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 1.1205673217773438e-05s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 3.108901023864746s
Availability | SPARQL endpoint availability check for Surge Radio took 4.267692565917969e-05s
Availability | VoID file availability check for Surge Radio took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.24826812744140625s
Reputation | Calculation of the PageRank for Surge Radio took 0.02012467384338379s
Interlinking | Calculation of Degree of Connection for Surge Radio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Surge Radio took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.20159912109375e-05s
Believability | Calculation of trust value for Surge Radio took 1.0967254638671875e-05s
INFO | --- Analysis for surge-radio took 2.8273351192474365s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 5.14984130859375e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.2814772129058838s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.8371810913085938e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 6.4373016357421875e-06s
INFO | --- Analysis for SWAT took 2.9447858333587646s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 4.220008850097656e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.25600576400756836s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.020389080047607422s
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.000701904296875s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.343292236328125e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 6.67572021484375e-06s
INFO | --- Analysis for swedish-open-cultural-heritage took 2.8528358936309814s
Availability | SPARQL endpoint availability check for SweFN-RDF took 3.9577484130859375e-05s
Availability | VoID file availability check for SweFN-RDF took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.2784261703491211s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020232439041137695s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.409385681152344e-05s
Believability | Calculation of trust value for SweFN-RDF took 6.9141387939453125e-06s
INFO | --- Analysis for swefn-rdf took 2.957376480102539s
Availability | SPARQL endpoint availability check for SwetoDblp took 4.0531158447265625e-05s
Availability | VoID file availability check for SwetoDblp took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.26061224937438965s
Reputation | Calculation of the PageRank for SwetoDblp took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for SwetoDblp took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 4.1484832763671875e-05s
Believability | Calculation of trust value for SwetoDblp took 6.9141387939453125e-06s
INFO | --- Analysis for sweto-dblp took 2.807042360305786s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 4.2438507080078125e-05s
Availability | VoID file availability check for Swift Vocabulary took 0.0003197193145751953s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.28917813301086426s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.02077770233154297s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 7.43865966796875e-05s
Believability | Calculation of trust value for Swift Vocabulary took 9.059906005859375e-06s
INFO | --- Analysis for Swift took 2.850618600845337s
Availability | SPARQL endpoint availability check for SymbolicData took 5.14984130859375e-05s
Availability | VoID file availability check for SymbolicData took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.24665403366088867s
Reputation | Calculation of the PageRank for SymbolicData took 0.02024555206298828s
Interlinking | Calculation of Degree of Connection for SymbolicData took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SymbolicData took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 2.956390380859375e-05s
Believability | Calculation of trust value for SymbolicData took 6.67572021484375e-06s
INFO | --- Analysis for symbolicdata took 2.7970869541168213s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 5.412101745605469e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0002803802490234375s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.25224971771240234s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020180940628051758s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 2.86102294921875e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 7.152557373046875e-06s
INFO | --- Analysis for symptoms-in-chinese took 2.9089295864105225s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.4673655033111572s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.0002963542938232422s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.4925570487976074s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.8901069164276123s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 50.31447792053223s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 17.88747239112854s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.19078779220581055s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 35.51866555213928s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.10968899726867676s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 1.273139238357544s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 1.1162168979644775s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.16897916793823242s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.9052901268005371s
License | HR license check for National Digital Data Archive of Hungary (partial) took 54.74976921081543s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5846178531646729s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 42.04711365699768s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.3517284393310547s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.20301175117492676s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.16902446746826172s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 1.3336546421051025s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.90791654586792s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.128715515136719e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.5639324188232422s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.7276699542999268s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.474924087524414s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.4220757484436035s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.4280269145965576s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.2477598190307617s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.7808470726013184s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 73.11031031608582s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 9.5367431640625e-07s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.18066906929016113s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.25424671173095703s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.0027191638946533203s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.002987384796142578s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.2574648857116699s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.67451596260071s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.26331377029418945s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.5954980850219727s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.3253867626190186s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 45.27579355239868s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.0022728443145751953s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.49118638038635254s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.22368097305297852s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 16.820958852767944s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.8165867328643799s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02071666717529297s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 9.012222290039062e-05s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 8.58306884765625e-06s
INFO | --- Analysis for sztaki-lod took 584.1599950790405s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.100799560546875e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.24819397926330566s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.02095174789428711s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007812976837158203s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.412101745605469e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 5.1975250244140625e-05s
INFO | --- Analysis for t4gm-info took 3.734187126159668s
Availability | SPARQL endpoint availability check for tags2con delicious took 4.100799560546875e-05s
Availability | VoID file availability check for tags2con delicious took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.2550010681152344s
Reputation | Calculation of the PageRank for tags2con delicious took 0.02037668228149414s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 3.9577484130859375e-05s
Believability | Calculation of trust value for tags2con delicious took 7.62939453125e-06s
INFO | --- Analysis for tags2con-delicious took 3.273491621017456s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 4.029273986816406e-05s
Availability | VoID file availability check for Taiwan geographic names took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.2660982608795166s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 4.696846008300781e-05s
Believability | Calculation of trust value for Taiwan geographic names took 7.3909759521484375e-06s
INFO | --- Analysis for taiwan-geographic-names took 3.328691005706787s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.3392181396484375e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0007650852203369141s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.24692058563232422s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02058863639831543s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 9.393692016601562e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 6.9141387939453125e-06s
INFO | --- Analysis for talis-openlibrary took 4.324495315551758s
Availability | SPARQL endpoint availability check for TalkBank took 4.029273986816406e-05s
Availability | VoID file availability check for TalkBank took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for TalkBank took 0.25756263732910156s
Reputation | Calculation of the PageRank for TalkBank took 0.021317481994628906s
Interlinking | Calculation of Degree of Connection for TalkBank took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for TalkBank took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.86102294921875e-05s
Believability | Calculation of trust value for TalkBank took 7.152557373046875e-06s
INFO | --- Analysis for talkbank took 2.8270962238311768s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 4.291534423828125e-05s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.000293731689453125s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.2521815299987793s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.000118255615234375s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for taxonconcept took 2.864248752593994s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 4.076957702636719e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.00033020973205566406s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.24792718887329102s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.0201568603515625s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 7.367134094238281e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.3113021850585938e-05s
INFO | --- Analysis for taxonconcept-assets took 2.935359239578247s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 5.364418029785156e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.27316784858703613s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.0205380916595459s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 4.9591064453125e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 8.106231689453125e-06s
INFO | --- Analysis for taxonconcept-occurences took 2.8108770847320557s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 4.3392181396484375e-05s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.0002772808074951172s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.2784595489501953s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.020431041717529297s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.9114227294921875e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 7.152557373046875e-06s
INFO | --- Analysis for taxref-ld took 2.875453472137451s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 4.2438507080078125e-05s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.00029540061950683594s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.23730826377868652s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.02048492431640625s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 3.0517578125e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 6.9141387939453125e-06s
INFO | --- Analysis for tcga took 2.8139147758483887s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 3.933906555175781e-05s
Availability | VoID file availability check for TCGA Roadmap took 0.00026106834411621094s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.24390745162963867s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.021349430084228516s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007565021514892578s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 7.557868957519531e-05s
Believability | Calculation of trust value for TCGA Roadmap took 7.152557373046875e-06s
INFO | --- Analysis for tcga-roadmap took 2.799816608428955s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 4.076957702636719e-05s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.0002963542938232422s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.2684214115142822s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.020543813705444336s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.72747802734375e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 7.62939453125e-06s
INFO | --- Analysis for tcmgenedit_dataset took 2.89943790435791s
Availability | SPARQL endpoint availability check for TDS took 4.00543212890625e-05s
Availability | VoID file availability check for TDS took 0.00030517578125s
Completeness | Calculation of interlinking completeness for TDS took 0.25394487380981445s
Reputation | Calculation of the PageRank for TDS took 0.020681381225585938s
Interlinking | Calculation of Degree of Connection for TDS took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TDS took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for TDS took 3.981590270996094e-05s
Believability | Calculation of trust value for TDS took 7.3909759521484375e-06s
INFO | --- Analysis for tds took 2.8327221870422363s
Availability | SPARQL endpoint availability check for TED Talks took 4.029273986816406e-05s
Availability | VoID file availability check for TED Talks took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for TED Talks took 0.26123952865600586s
Reputation | Calculation of the PageRank for TED Talks took 0.020557403564453125s
Interlinking | Calculation of Degree of Connection for TED Talks took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TED Talks took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for TED Talks took 3.0994415283203125e-05s
Believability | Calculation of trust value for TED Talks took 7.867813110351562e-06s
INFO | --- Analysis for ted-talks took 2.8548147678375244s
Availability | SPARQL endpoint availability check for TEKORD took 3.981590270996094e-05s
Availability | VoID file availability check for TEKORD took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for TEKORD took 0.2742271423339844s
Reputation | Calculation of the PageRank for TEKORD took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for TEKORD took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for TEKORD took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.410743713378906e-05s
Believability | Calculation of trust value for TEKORD took 7.3909759521484375e-06s
INFO | --- Analysis for tekord took 2.8588144779205322s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for Telegraphis Linked Data took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.2496492862701416s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.020392179489135742s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0006833076477050781s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.00010704994201660156s
Believability | Calculation of trust value for Telegraphis Linked Data took 7.867813110351562e-06s
INFO | --- Analysis for telegraphis took 2.9103095531463623s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 4.172325134277344e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.00023317337036132812s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.25705575942993164s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.022179603576660156s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0010848045349121094s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 8.559226989746094e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 8.344650268554688e-06s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 2.8594489097595215s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 4.100799560546875e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.0002887248992919922s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.24558639526367188s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.02043890953063965s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for TERENCE Reading Comprehension Dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for TERENCE Reading Comprehension Dataset took 1.049041748046875e-05s
INFO | --- Analysis for terence-reading-comprehension-dataset took 2.824634552001953s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 4.124641418457031e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0003151893615722656s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.2772963047027588s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.02058696746826172s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 2.9087066650390625e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for terminesp took 2.8896830081939697s
Availability | SPARQL endpoint availability check for Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Ontology took 0.00038909912109375s
Completeness | Calculation of interlinking completeness for Ontology took 0.24620819091796875s
Reputation | Calculation of the PageRank for Ontology took 0.020725250244140625s
Interlinking | Calculation of Degree of Connection for Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Terrorist_attack took 2.8511734008789062s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 4.029273986816406e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.25465822219848633s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.02053999900817871s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 3.170967102050781e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 7.867813110351562e-06s
INFO | --- Analysis for Terrorist_Attack_1 took 2.8298850059509277s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.2438507080078125e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.00026798248291015625s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.24880576133728027s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 2.9087066650390625e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 8.106231689453125e-06s
INFO | --- Analysis for tesauro-materias-bupm took 2.8426239490509033s
Availability | SPARQL endpoint availability check for Teseo took 4.267692565917969e-05s
Availability | VoID file availability check for Teseo took 0.00031256675720214844s
Completeness | Calculation of interlinking completeness for Teseo took 0.25518202781677246s
Reputation | Calculation of the PageRank for Teseo took 0.02091670036315918s
Interlinking | Calculation of Degree of Connection for Teseo took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Teseo took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Teseo took 3.409385681152344e-05s
Believability | Calculation of trust value for Teseo took 1.3828277587890625e-05s
INFO | --- Analysis for teseo took 2.767514944076538s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 4.0531158447265625e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0002601146697998047s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.2365736961364746s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020619630813598633s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 2.9325485229492188e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 1.2159347534179688e-05s
INFO | --- Analysis for Tesla_Deaths took 2.7560689449310303s
Availability | SPARQL endpoint availability check for test took 4.0531158447265625e-05s
Availability | VoID file availability check for test took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for test took 0.2630331516265869s
Reputation | Calculation of the PageRank for test took 0.020335912704467773s
Interlinking | Calculation of Degree of Connection for test took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for test took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for test took 2.9325485229492188e-05s
Believability | Calculation of trust value for test took 7.152557373046875e-06s
INFO | --- Analysis for test took 2.8478572368621826s
Availability | SPARQL endpoint availability check for Test took 6.890296936035156e-05s
Availability | VoID file availability check for Test took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Test took 0.24082446098327637s
Reputation | Calculation of the PageRank for Test took 0.020731449127197266s
Interlinking | Calculation of Degree of Connection for Test took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Test took 3.0994415283203125e-05s
Believability | Calculation of trust value for Test took 7.867813110351562e-06s
INFO | --- Analysis for Test took 2.8006789684295654s
Availability | SPARQL endpoint availability check for test-svu took 4.076957702636719e-05s
Availability | VoID file availability check for test-svu took 0.00023818016052246094s
Completeness | Calculation of interlinking completeness for test-svu took 0.2526423931121826s
Reputation | Calculation of the PageRank for test-svu took 0.020649433135986328s
Interlinking | Calculation of Degree of Connection for test-svu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.0994415283203125e-05s
Believability | Calculation of trust value for test-svu took 7.867813110351562e-06s
INFO | --- Analysis for test-svu took 2.8798792362213135s
Availability | SPARQL endpoint availability check for Test took 4.0531158447265625e-05s
Availability | VoID file availability check for Test took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Test took 0.24398183822631836s
Reputation | Calculation of the PageRank for Test took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Test took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Test took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Test took 2.956390380859375e-05s
Believability | Calculation of trust value for Test took 1.2636184692382812e-05s
INFO | --- Analysis for Test_ took 2.8224592208862305s
Availability | SPARQL endpoint availability check for xxxxx took 4.100799560546875e-05s
Availability | VoID file availability check for xxxxx took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for xxxxx took 0.25925111770629883s
Reputation | Calculation of the PageRank for xxxxx took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for xxxxx took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for xxxxx took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.2438507080078125e-05s
Believability | Calculation of trust value for xxxxx took 1.2636184692382812e-05s
INFO | --- Analysis for testee took 2.9455952644348145s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.172325134277344e-05s
Availability | VoID file availability check for Texai Lexicon took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.2357184886932373s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.020237207412719727s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.0040740966796875e-05s
Believability | Calculation of trust value for Texai Lexicon took 8.58306884765625e-06s
INFO | --- Analysis for texai_lexicon took 2.800828218460083s
Availability | SPARQL endpoint availability check for tharawat magazine took 4.124641418457031e-05s
Availability | VoID file availability check for tharawat magazine took 0.0002505779266357422s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.27240753173828125s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02072930335998535s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010275840759277344s
Believability | Calculation of trust value for tharawat magazine took 7.867813110351562e-06s
INFO | --- Analysis for tharawat-magazine-com took 2.870265007019043s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.124641418457031e-05s
Availability | VoID file availability check for The CIARD RING took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.24069523811340332s
Reputation | Calculation of the PageRank for The CIARD RING took 0.02068948745727539s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0279159545898438e-05s
Believability | Calculation of trust value for The CIARD RING took 7.867813110351562e-06s
INFO | --- Analysis for the-ciard-ring took 2.85840106010437s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 4.1484832763671875e-05s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.26528143882751465s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.020383119583129883s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 2.86102294921875e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 7.152557373046875e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.9176065921783447s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 0.7926666736602783s
Availability | VoID file availability check for The European Library Open Dataset took 0.0002551078796386719s
Extra | Recovery of all triples for The European Library Open Dataset took 1.098951816558838s
Performance | Total latancy measurement for The European Library Open Dataset took 1.3858740329742432s
Amount of data | Number of triples check for The European Library Open Dataset took 30.18023157119751s
Versatility | Languages check for The European Library Open Dataset took 0.2646157741546631s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 30.234760522842407s
Interpretability | RDF structures check for The European Library Open Dataset took 0.22152400016784668s
Versatility | Serialization formats check for The European Library Open Dataset took 0.2665398120880127s
Availability | RDF dump link check for The European Library Open Dataset took 0.22783994674682617s
License | MR license check for The European Library Open Dataset took 0.3290541172027588s
License | HR license check for The European Library Open Dataset took 0.22452855110168457s
Amount of data | Number of property check for The European Library Open Dataset took 0.23076510429382324s
Understandability | Number of label check for The European Library Open Dataset took 0.7762219905853271s
Understandability | URI regex check for The European Library Open Dataset took 0.4527604579925537s
Understandability | Vocabs check for The European Library Open Dataset took 0.2935678958892822s
Verifiability | Authors check for The European Library Open Dataset took 0.254932165145874s
Verifiability | Publishers check for The European Library Open Dataset took 0.24903082847595215s
Performance | Throughput check for The European Library Open Dataset took 11.607425689697266s
Amount of data | Check the number of entities for The European Library Open Dataset took 8.511543273925781e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 0.23261237144470215s
Interlinking | sameAs chians check for The European Library Open Dataset took 0.3059854507446289s
Interlinking | skos check for The European Library Open Dataset took 0.30861711502075195s
Interlinking | skos check for The European Library Open Dataset took 0.22519707679748535s
Timeliness | dataset update frequency check for The European Library Open Dataset took 0.266467809677124s
Currency | Creation date check for The European Library Open Dataset took 0.5315325260162354s
Currency | Modification date check for The European Library Open Dataset took 0.5139815807342529s
Rep.Conc. | URIs length for The European Library Open Dataset took 60.47905874252319s
Interoperability | New vocabularies check for The European Library Open Dataset took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for The European Library Open Dataset took 0.28128790855407715s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 0.43534255027770996s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02762007713317871s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02747797966003418s
Consistency | Disjoint class check for The European Library Open Dataset took 0.2886660099029541s
Consistency | Check Misplaced properties for The European Library Open Dataset took 30.472275495529175s
Consistency | Misplaced classes for The European Library Open Dataset took 0.5846600532531738s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 1.8043525218963623s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3105945587158203s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 31.69051432609558s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.034415483474731445s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 1.402388334274292s
Security | Sign check for The European Library Open Dataset took 0.3840031623840332s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 15.122003078460693s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.5843923091888428s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 7.867813110351562e-06s
INFO | --- Analysis for the-european-library-open-dataset took 395.97398471832275s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 4.458427429199219e-05s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0003910064697265625s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.36365842819213867s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 9.34600830078125e-05s
Believability | Calculation of trust value for The Eurostat Linked Data took 7.152557373046875e-06s
INFO | --- Analysis for the-eurostat-linked-data took 5.7586400508880615s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.0531158447265625e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.30394840240478516s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020371675491333008s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 3.600120544433594e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 7.3909759521484375e-06s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 3.1195201873779297s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 5.0067901611328125e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.2567594051361084s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020407915115356445s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 6.937980651855469e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 7.62939453125e-06s
INFO | --- Analysis for the-living-lod-cloud took 2.974257707595825s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 5.316734313964844e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.2499532699584961s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.020178794860839844s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.8371810913085938e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 8.106231689453125e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 2.9318671226501465s
Availability | SPARQL endpoint availability check for The View From took 0.17684197425842285s
Availability | VoID file availability check for The View From took 0.00023674964904785156s
Completeness | Calculation of interlinking completeness for The View From took 0.2713947296142578s
Reputation | Calculation of the PageRank for The View From took 0.020272254943847656s
Interlinking | Calculation of Degree of Connection for The View From took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The View From took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for The View From took 7.843971252441406e-05s
Believability | Calculation of trust value for The View From took 6.4373016357421875e-06s
INFO | --- Analysis for the-view-from took 3.3142924308776855s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 4.1484832763671875e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.2437729835510254s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02035212516784668s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.9802322387695312e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 7.152557373046875e-06s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 2.920447587966919s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 4.076957702636719e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.26836585998535156s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.02031230926513672s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.7894973754882812e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.2874603271484375e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 2.935641288757324s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.0531158447265625e-05s
Availability | VoID file availability check for The Content Wrangler took 0.0002613067626953125s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.2820596694946289s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.02016735076904297s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.00010561943054199219s
Believability | Calculation of trust value for The Content Wrangler took 6.4373016357421875e-06s
INFO | --- Analysis for thecontentwrangler-com took 2.956514835357666s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.267692565917969e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.00032830238342285156s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.25574493408203125s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02078986167907715s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 2.956390380859375e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 6.9141387939453125e-06s
INFO | --- Analysis for thesaurus-bncf took 2.967463493347168s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 4.076957702636719e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.0003159046173095703s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.2787785530090332s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 3.218650817871094e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 7.62939453125e-06s
INFO | --- Analysis for thesaurus-datenwissen took 2.8574159145355225s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 4.276881217956543s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00028228759765625s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.276047945022583s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0009195804595947266s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 8.344650268554688e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 1.2636184692382812e-05s
INFO | --- Analysis for thesaurus-w took 8.762213230133057s
Availability | SPARQL endpoint availability check for theses.fr took 3.981590270996094e-05s
Availability | VoID file availability check for theses.fr took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for theses.fr took 0.2376995086669922s
Reputation | Calculation of the PageRank for theses.fr took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for theses.fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.696846008300781e-05s
Believability | Calculation of trust value for theses.fr took 7.62939453125e-06s
INFO | --- Analysis for thesesfr took 2.972712516784668s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.076957702636719e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.2645745277404785s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020312070846557617s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.0994415283203125e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 6.9141387939453125e-06s
INFO | --- Analysis for Thinkphile took 2.903247117996216s
Availability | SPARQL endpoint availability check for ThIST took 4.601478576660156e-05s
Availability | VoID file availability check for ThIST took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for ThIST took 0.254180908203125s
Reputation | Calculation of the PageRank for ThIST took 0.020298004150390625s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for ThIST took 7.557868957519531e-05s
Believability | Calculation of trust value for ThIST took 6.4373016357421875e-06s
INFO | --- Analysis for thist took 3.0129027366638184s
Availability | SPARQL endpoint availability check for TIP took 39.00993466377258s
Availability | VoID file availability check for TIP took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for TIP took 0.24448323249816895s
Reputation | Calculation of the PageRank for TIP took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for TIP took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for TIP took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for TIP took 0.00010585784912109375s
Believability | Calculation of trust value for TIP took 7.3909759521484375e-06s
INFO | --- Analysis for tip took 80.25647139549255s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 4.124641418457031e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.27770328521728516s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.0204007625579834s
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.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 2.7418136596679688e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 7.3909759521484375e-06s
INFO | --- Analysis for TOPMODEL took 5.192720890045166s
Availability | SPARQL endpoint availability check for Tourpedia took 4.744529724121094e-05s
Availability | VoID file availability check for Tourpedia took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.26421523094177246s
Reputation | Calculation of the PageRank for Tourpedia took 0.020624876022338867s
Interlinking | Calculation of Degree of Connection for Tourpedia took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Tourpedia took 0.0009963512420654297s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.4332275390625e-05s
Believability | Calculation of trust value for Tourpedia took 9.298324584960938e-06s
INFO | --- Analysis for tourpedia took 3.2681081295013428s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 4.0531158447265625e-05s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.2674076557159424s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.02040886878967285s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.0009987354278564453s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 4.3392181396484375e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 7.152557373046875e-06s
INFO | --- Analysis for TP-data took 3.48978590965271s
Availability | SPARQL endpoint availability check for Trackloaded Linked Open Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Trackloaded Linked Open Data took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Trackloaded Linked Open Data took 0.3290252685546875s
Reputation | Calculation of the PageRank for Trackloaded Linked Open Data took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for Trackloaded Linked Open Data took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Trackloaded Linked Open Data took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Trackloaded Linked Open Data took 1.1682510375976562e-05s
Believability | Calculation of trust value for Trackloaded Linked Open Data took 6.67572021484375e-06s
INFO | --- Analysis for trackloaded took 3.6783604621887207s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.3108365535736084s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.020476818084716797s
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.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 3.9577484130859375e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 6.67572021484375e-06s
INFO | --- Analysis for traditional-korean-medicine took 3.3064732551574707s
Availability | SPARQL endpoint availability check for Traffic Scotland took 3.981590270996094e-05s
Availability | VoID file availability check for Traffic Scotland took 0.0002503395080566406s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.2903296947479248s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.02012157440185547s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0006844997406005859s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.218650817871094e-05s
Believability | Calculation of trust value for Traffic Scotland took 7.152557373046875e-06s
INFO | --- Analysis for traffic-scotland took 3.292459011077881s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 4.029273986816406e-05s
Availability | VoID file availability check for Transparency International Linked Data took 0.0002696514129638672s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.27680087089538574s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020459413528442383s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 0.00010728836059570312s
Believability | Calculation of trust value for Transparency International Linked Data took 7.3909759521484375e-06s
INFO | --- Analysis for transparency-linked-data took 3.5004076957702637s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 4.1484832763671875e-05s
Availability | VoID file availability check for transport.data.gov.uk took 0.00027370452880859375s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.29477953910827637s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020578861236572266s
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.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.96453857421875e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 7.3909759521484375e-06s
INFO | --- Analysis for transport-data-gov-uk took 3.489975929260254s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.1484832763671875e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.26151371002197266s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.02087855339050293s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0007543563842773438s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 3.218650817871094e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 7.867813110351562e-06s
INFO | --- Analysis for transport-openuplabs took 3.097123861312866s
Availability | SPARQL endpoint availability check for Trelios took 4.029273986816406e-05s
Availability | VoID file availability check for Trelios took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Trelios took 0.29297447204589844s
Reputation | Calculation of the PageRank for Trelios took 0.02030324935913086s
Interlinking | Calculation of Degree of Connection for Trelios took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1682510375976562e-05s
Believability | Calculation of trust value for Trelios took 7.62939453125e-06s
INFO | --- Analysis for Trelios took 3.7526774406433105s
Availability | SPARQL endpoint availability check for Twarql took 4.124641418457031e-05s
Availability | VoID file availability check for Twarql took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for Twarql took 0.37840747833251953s
Reputation | Calculation of the PageRank for Twarql took 0.02069878578186035s
Interlinking | Calculation of Degree of Connection for Twarql took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Twarql took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.771087646484375e-05s
Believability | Calculation of trust value for Twarql took 7.867813110351562e-06s
INFO | --- Analysis for twarql took 6.089299440383911s
Availability | SPARQL endpoint availability check for TWC Data-gov took 6.4849853515625e-05s
Availability | VoID file availability check for TWC Data-gov took 0.0002446174621582031s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.7403132915496826s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.020725727081298828s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 2.9087066650390625e-05s
Believability | Calculation of trust value for TWC Data-gov took 7.867813110351562e-06s
INFO | --- Analysis for twc-data-gov took 5.642260313034058s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 4.124641418457031e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.4442758560180664s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020621776580810547s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0006783008575439453s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 2.86102294921875e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 6.9141387939453125e-06s
INFO | --- Analysis for twc-demos took 4.8914830684661865s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 4.887580871582031e-05s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.3000316619873047s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.020513534545898438s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 2.9087066650390625e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.1920928955078125e-05s
INFO | --- Analysis for twc-healthdata took 4.107070446014404s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 5.14984130859375e-05s
Availability | VoID file availability check for Instance Hub (all) took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.9987070560455322s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02044200897216797s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 6.437301635742188e-05s
Believability | Calculation of trust value for Instance Hub (all) took 7.867813110351562e-06s
INFO | --- Analysis for twc-hub took 5.45531153678894s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 4.172325134277344e-05s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 1.3414673805236816s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020739316940307617s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00011229515075683594s
Believability | Calculation of trust value for IEEE VIS Source Data took 8.58306884765625e-06s
INFO | --- Analysis for twc-ieeevis took 5.875242471694946s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 4.839897155761719e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.00029468536376953125s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.6545438766479492s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.020647048950195312s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0008249282836914062s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 9.512901306152344e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 8.344650268554688e-06s
INFO | --- Analysis for twc-logd took 6.0217554569244385s
Availability | SPARQL endpoint availability check for twc-opendap took 5.3882598876953125e-05s
Availability | VoID file availability check for twc-opendap took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.48700833320617676s
Reputation | Calculation of the PageRank for twc-opendap took 0.02035069465637207s
Interlinking | Calculation of Degree of Connection for twc-opendap took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for twc-opendap took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 7.104873657226562e-05s
Believability | Calculation of trust value for twc-opendap took 7.152557373046875e-06s
INFO | --- Analysis for twc-opendap took 4.504732608795166s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 4.076957702636719e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0002751350402832031s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.296811580657959s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.020625829696655273s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 2.9325485229492188e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 7.62939453125e-06s
INFO | --- Analysis for tweetskb took 6.113025188446045s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.076957702636719e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.2999389171600342s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.02078866958618164s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.528594970703125e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 7.62939453125e-06s
INFO | --- Analysis for twitter-lids took 4.319482088088989s
Availability | SPARQL endpoint availability check for typepad took 4.172325134277344e-05s
Availability | VoID file availability check for typepad took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for typepad took 0.5232570171356201s
Reputation | Calculation of the PageRank for typepad took 0.020383358001708984s
Interlinking | Calculation of Degree of Connection for typepad took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for typepad took 4.7206878662109375e-05s
Believability | Calculation of trust value for typepad took 8.344650268554688e-06s
INFO | --- Analysis for typepad took 5.41272497177124s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 1.2823476791381836s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.3066887855529785s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020250797271728516s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.363059997558594e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 8.344650268554688e-06s
INFO | --- Analysis for ub-mannheim-linked-data took 7.902242422103882s
Availability | SPARQL endpoint availability check for Uberblic.org took 4.220008850097656e-05s
Availability | VoID file availability check for Uberblic.org took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.29428625106811523s
Reputation | Calculation of the PageRank for Uberblic.org took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Uberblic.org took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010347366333007812s
Believability | Calculation of trust value for Uberblic.org took 7.152557373046875e-06s
INFO | --- Analysis for uberblic took 4.67545747756958s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.8396847248077393s
Availability | VoID file availability check for UDante in LiLa took 0.00029397010803222656s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.4346888065338135s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020847558975219727s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0006825923919677734s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for UDante in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for UDante took 6.654755115509033s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 5.650520324707031e-05s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0002720355987548828s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.3031196594238281s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.02047896385192871s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0006775856018066406s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 2.9087066650390625e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 8.344650268554688e-06s
INFO | --- Analysis for ufo took 4.14647650718689s
Availability | SPARQL endpoint availability check for Uganda Disasters took 6.580352783203125e-05s
Availability | VoID file availability check for Uganda Disasters took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.370391845703125s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.020759105682373047s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.673004150390625e-05s
Believability | Calculation of trust value for Uganda Disasters took 8.58306884765625e-06s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 3.7293310165405273s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 5.054473876953125e-05s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.00028014183044433594s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.38967299461364746s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02072620391845703s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.0009751319885253906s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 0.00011706352233886719s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 7.62939453125e-06s
INFO | --- Analysis for uis-linked-data took 3.945429563522339s
Availability | SPARQL endpoint availability check for UK Legislation took 5.245208740234375e-05s
Availability | VoID file availability check for UK Legislation took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.3610548973083496s
Reputation | Calculation of the PageRank for UK Legislation took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for UK Legislation took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UK Legislation took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.7738037109375e-05s
Believability | Calculation of trust value for UK Legislation took 7.867813110351562e-06s
INFO | --- Analysis for uk-legislation-api took 4.159201145172119s
Availability | SPARQL endpoint availability check for UK Postcodes took 4.2438507080078125e-05s
Availability | VoID file availability check for UK Postcodes took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.3537595272064209s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02075815200805664s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.7697296142578125e-05s
Believability | Calculation of trust value for UK Postcodes took 7.867813110351562e-06s
INFO | --- Analysis for uk-postcodes took 3.8659169673919678s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.1961669921875e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.38994312286376953s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020681142807006836s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0010728836059570312s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0001537799835205078s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 7.867813110351562e-06s
INFO | --- Analysis for umbel took 3.580364942550659s
Availability | SPARQL endpoint availability check for UMTHES took 4.124641418457031e-05s
Availability | VoID file availability check for UMTHES took 0.00027680397033691406s
Completeness | Calculation of interlinking completeness for UMTHES took 0.32359743118286133s
Reputation | Calculation of the PageRank for UMTHES took 0.020577669143676758s
Interlinking | Calculation of Degree of Connection for UMTHES took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UMTHES took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.172325134277344e-05s
Believability | Calculation of trust value for UMTHES took 8.106231689453125e-06s
INFO | --- Analysis for umthes took 3.542320966720581s
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.00029754638671875s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.33974480628967285s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.2901763916015625e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 6.67572021484375e-06s
INFO | --- Analysis for un-hazardous-numbers took 3.5040173530578613s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.1961669921875e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.3911428451538086s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020654916763305664s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.170967102050781e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.3909759521484375e-06s
INFO | --- Analysis for unesco-thesaurus took 3.9153361320495605s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.3184778690338135s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.02048778533935547s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for unescothes took 4.540703296661377s
Availability | SPARQL endpoint availability check for UniProt took 4.100799560546875e-05s
Availability | VoID file availability check for UniProt took 0.00031876564025878906s
Completeness | Calculation of interlinking completeness for UniProt took 0.33800840377807617s
Reputation | Calculation of the PageRank for UniProt took 0.020401716232299805s
Interlinking | Calculation of Degree of Connection for UniProt took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for UniProt took 3.9577484130859375e-05s
Believability | Calculation of trust value for UniProt took 7.3909759521484375e-06s
INFO | --- Analysis for UniProt took 4.034689426422119s
Availability | SPARQL endpoint availability check for UniProt took 8.559226989746094e-05s
Availability | VoID file availability check for UniProt took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for UniProt took 0.4832127094268799s
Reputation | Calculation of the PageRank for UniProt took 0.020473480224609375s
Interlinking | Calculation of Degree of Connection for UniProt took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for UniProt took 5.125999450683594e-05s
Believability | Calculation of trust value for UniProt took 8.344650268554688e-06s
INFO | --- Analysis for uniprot took 4.939760208129883s
Availability | SPARQL endpoint availability check for UniProt citations took 4.1961669921875e-05s
Availability | VoID file availability check for UniProt citations took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.43316102027893066s
Reputation | Calculation of the PageRank for UniProt citations took 0.020639896392822266s
Interlinking | Calculation of Degree of Connection for UniProt citations took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for UniProt citations took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.170967102050781e-05s
Believability | Calculation of trust value for UniProt citations took 7.62939453125e-06s
INFO | --- Analysis for uniprot-citations took 6.663872718811035s
Availability | SPARQL endpoint availability check for UniProt databases took 4.291534423828125e-05s
Availability | VoID file availability check for UniProt databases took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.3642690181732178s
Reputation | Calculation of the PageRank for UniProt databases took 0.02071976661682129s
Interlinking | Calculation of Degree of Connection for UniProt databases took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProt databases took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.2901763916015625e-05s
Believability | Calculation of trust value for UniProt databases took 7.867813110351562e-06s
INFO | --- Analysis for uniprot-databases took 4.109177350997925s
Availability | SPARQL endpoint availability check for uniprot-metadata took 7.772445678710938e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.44872212409973145s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.020651578903198242s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.270408630371094e-05s
Believability | Calculation of trust value for uniprot-metadata took 7.867813110351562e-06s
INFO | --- Analysis for uniprot-metadata took 4.0756964683532715s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 4.172325134277344e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.31926393508911133s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 3.1948089599609375e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 7.152557373046875e-06s
INFO | --- Analysis for uniprot-taxonomy took 3.8308801651000977s
Availability | SPARQL endpoint availability check for UniProt UniParc took 4.029273986816406e-05s
Availability | VoID file availability check for UniProt UniParc took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.3151237964630127s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020714759826660156s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.0517578125e-05s
Believability | Calculation of trust value for UniProt UniParc took 7.867813110351562e-06s
INFO | --- Analysis for uniprot-uniparc took 3.5044162273406982s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.029273986816406e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0002524852752685547s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.30444812774658203s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 2.956390380859375e-05s
Believability | Calculation of trust value for UniProt UniPathway took 7.3909759521484375e-06s
INFO | --- Analysis for uniprot-unipathway took 3.467416763305664s
Availability | SPARQL endpoint availability check for UniProtKB took 4.00543212890625e-05s
Availability | VoID file availability check for UniProtKB took 0.0002849102020263672s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.30471181869506836s
Reputation | Calculation of the PageRank for UniProtKB took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for UniProtKB took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UniProtKB took 0.0006825923919677734s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 5.5789947509765625e-05s
Believability | Calculation of trust value for UniProtKB took 7.3909759521484375e-06s
INFO | --- Analysis for uniprotkb took 3.256411075592041s
Availability | SPARQL endpoint availability check for UniProt UniRef took 3.9577484130859375e-05s
Availability | VoID file availability check for UniProt UniRef took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.2801787853240967s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 2.9802322387695312e-05s
Believability | Calculation of trust value for UniProt UniRef took 7.62939453125e-06s
INFO | --- Analysis for uniref took 3.1347272396087646s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 8.678436279296875e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.26399779319763184s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.02053356170654297s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 2.9325485229492188e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 7.62939453125e-06s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 3.0275704860687256s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 4.1484832763671875e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00026226043701171875s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.28009939193725586s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.02073979377746582s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.552436828613281e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 8.344650268554688e-06s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 3.1828229427337646s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 3.933906555175781e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.2893249988555908s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.02080559730529785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 3.0872762203216553s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.2868940830230713s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.020668983459472656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007791519165039062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.696846008300781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 2.9844536781311035s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.2663407325744629s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.0205538272857666s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 3.019265651702881s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 0.00010418891906738281s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.2710251808166504s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020551681518554688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-basque took 2.945592164993286s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.00033926963806152344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.27977919578552246s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.02070021629333496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.00078582763671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Bulgarian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Bulgarian took 3.361701965332031e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 3.068286657333374s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.0002880096435546875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.2560739517211914s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.020384550094604492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 3.033658266067505s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 5.054473876953125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.28875064849853516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 3.0625593662261963s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 8.845329284667969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.2981421947479248s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.02041935920715332s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 3.0564510822296143s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 4.863739013671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0002396106719970703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.28357744216918945s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020594120025634766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.38690185546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 2.918393135070801s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.26628971099853516s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020720243453979492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.7881393432617188e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 3.0386271476745605s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.27628445625305176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.020634174346923828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 2.9961891174316406s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0002644062042236328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.30052900314331055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.02045416831970215s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 2.9874267578125s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.2793748378753662s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.020262956619262695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-danish took 2.9288856983184814s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 4.029273986816406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.27419066429138184s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020495891571044922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 2.848686695098877s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 4.315376281738281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.00029850006103515625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.24555039405822754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 2.7779598236083984s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.2581052780151367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.020706653594970703s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.267692565917969e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-english took 2.8303627967834473s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 4.506111145019531e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.000240325927734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.27280092239379883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 2.8487086296081543s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.2642347812652588s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020636558532714844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 2.8603053092956543s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.2539088726043701s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.0206298828125s
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.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 2.902635335922241s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.25878047943115234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 2.840158700942993s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.2557530403137207s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 2.897199869155884s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.2510201930999756s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-french took 2.9018051624298096s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.00023031234741210938s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.25159692764282227s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02051091194152832s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician took 2.8494622707366943s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician-TreeGal took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician-TreeGal took 0.0005373954772949219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.24907588958740234s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 6.580352783203125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 2.8998448848724365s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 5.1975250244140625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0002818107604980469s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.2662343978881836s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.021004199981689453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank German took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank German took 0.0008983612060546875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-german took 3.0759012699127197s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.00028061866760253906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.35857081413269043s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.02052474021911621s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 3.564116954803467s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 7.462501525878906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.2526884078979492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.020830631256103516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-greek took 2.8521811962127686s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.000335693359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.2767448425292969s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.814697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 2.988586187362671s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.4301309585571289s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.020578384399414062s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 3.790855407714844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 4.336496114730835s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 4.8160552978515625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.00026702880859375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.2706904411315918s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0006871223449707031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 3.246692657470703s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.029273986816406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.00023245811462402344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.27687811851501465s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020377397537231445s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 1.1920928955078125e-05s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 2.9911439418792725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.029273986816406e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.26217007637023926s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.02056574821472168s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Irish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Irish took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Irish took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Irish took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-irish took 3.023775339126587s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0002295970916748047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.2712066173553467s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-italian took 2.9375405311584473s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.27057313919067383s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0006854534149169922s
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 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 2.924689292907715s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0003764629364013672s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.26482343673706055s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.02041792869567871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese-KTC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese-KTC took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 2.8615007400512695s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.2581489086151123s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020624637603759766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.3392181396484375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 2.801198720932007s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 4.9114227294921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.2567572593688965s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020399093627929688s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin took 2.9100441932678223s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0003266334533691406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.25141477584838867s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.028389453887939453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0013647079467773438s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 6.103515625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 6.9141387939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 2.853188991546631s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.2689976692199707s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.020444393157958984s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 2.8983747959136963s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.2590453624725342s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020677566528320312s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.0006897449493408203s
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 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 2.8145041465759277s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.2649712562561035s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.020749330520629883s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 2.899200916290283s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.00038552284240722656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.26169252395629883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 1.6927719116210938e-05s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 2.830547332763672s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.2662079334259033s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.020390033721923828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007061958312988281s
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 2.8722617626190186s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.2653379440307617s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-polish took 2.9584896564483643s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 9.012222290039062e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.00033736228942871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.2659108638763428s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.020394086837768555s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 3.7670135498046875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 2.875584840774536s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0003402233123779297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.2561211585998535s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020733356475830078s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 2.8531758785247803s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0002646446228027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.2490241527557373s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.020648717880249023s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-BR took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-br took 2.942873477935791s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.0002682209014892578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.24112176895141602s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020827531814575195s
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.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 7.152557373046875e-06s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 2.871006727218628s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.0002465248107910156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.2583348751068115s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.02058243751525879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian took 2.9254438877105713s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.2458028793334961s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020476102828979492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 8.344650268554688e-06s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 3.0066330432891846s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.2513558864593506s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.020241737365722656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 3.099053144454956s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.2665073871612549s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.024042844772338867s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.0010898113250732422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.5299530029296875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 2.9442291259765625s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 4.076957702636719e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.24755859375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.020125150680541992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 9.059906005859375e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 2.859813928604126s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.00024771690368652344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.2718181610107422s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.02044534683227539s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 3.838539123535156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 2.9258522987365723s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0006213188171386719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.2646939754486084s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 2.8882596492767334s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 6.508827209472656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.24937963485717773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.02029109001159668s
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.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 6.4373016357421875e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 2.892319440841675s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.2858731746673584s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 4.57763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 2.9228031635284424s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.553794860839844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.00023484230041503906s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.25942254066467285s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.020979642868041992s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.887580871582031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 2.8823585510253906s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.23483014106750488s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020832538604736328s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 2.813755512237549s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.24417805671691895s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020483970642089844s
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.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 2.8146393299102783s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.38690185546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0002918243408203125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.25179505348205566s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020908594131469727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 2.826740026473999s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.24375414848327637s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.02063894271850586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 4.744529724121094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 2.859307050704956s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 4.4345855712890625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.24783754348754883s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.020603418350219727s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 7.3909759521484375e-06s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 2.8873133659362793s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 5.412101745605469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.00022172927856445312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.27736759185791016s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.02076554298400879s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 2.866279125213623s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 5.435943603515625e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0002815723419189453s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.25252294540405273s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.02075672149658203s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 7.367134094238281e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 7.3909759521484375e-06s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 2.8789162635803223s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 4.076957702636719e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.2605907917022705s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.02076864242553711s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0007481575012207031s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.0994415283203125e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 8.344650268554688e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 2.9068424701690674s
Availability | SPARQL endpoint availability check for University of Bristol took 8.630752563476562e-05s
Availability | VoID file availability check for University of Bristol took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.24933671951293945s
Reputation | Calculation of the PageRank for University of Bristol took 0.020666122436523438s
Interlinking | Calculation of Degree of Connection for University of Bristol took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007441043853759766s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.170967102050781e-05s
Believability | Calculation of trust value for University of Bristol took 1.1920928955078125e-05s
INFO | --- Analysis for university-of-bristol took 2.8836145401000977s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 7.271766662597656e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0002722740173339844s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.28479504585266113s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020883560180664062s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.030632019042969e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.1682510375976562e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 2.867008924484253s
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.00041604042053222656s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.24388456344604492s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020802021026611328s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 4.291534423828125e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 6.67572021484375e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.8407998085021973s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 4.1961669921875e-05s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.2565486431121826s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02092456817626953s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 7.200241088867188e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.2636184692382812e-05s
INFO | --- Analysis for unodc took 2.839282751083374s
Availability | SPARQL endpoint availability check for Super Ontology took 5.4836273193359375e-05s
Availability | VoID file availability check for Super Ontology took 0.00028395652770996094s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.2710261344909668s
Reputation | Calculation of the PageRank for Super Ontology took 0.020435333251953125s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 8.368492126464844e-05s
Believability | Calculation of trust value for Super Ontology took 7.62939453125e-06s
INFO | --- Analysis for upper-ontology took 2.9293293952941895s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.2520270347595215s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.0207979679107666s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.409385681152344e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.239776611328125e-05s
INFO | --- Analysis for Upper_Ontology took 2.8299176692962646s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 4.100799560546875e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.00032830238342285156s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.24911856651306152s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 7.62939453125e-06s
INFO | --- Analysis for Urban_Atlas_ took 2.883274793624878s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 4.38690185546875e-05s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.0002970695495605469s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.2690732479095459s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.020844459533691406s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.1948089599609375e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 6.67572021484375e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 2.8911895751953125s
Availability | SPARQL endpoint availability check for URIBurner took 4.6253204345703125e-05s
Availability | VoID file availability check for URIBurner took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for URIBurner took 0.26082491874694824s
Reputation | Calculation of the PageRank for URIBurner took 0.02092885971069336s
Interlinking | Calculation of Degree of Connection for URIBurner took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for URIBurner took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.179115295410156e-05s
Believability | Calculation of trust value for URIBurner took 8.106231689453125e-06s
INFO | --- Analysis for uriburner took 2.9387691020965576s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 4.2438507080078125e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.28406381607055664s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020280838012695312s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007398128509521484s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.266334533691406e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.1920928955078125e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.89654803276062s
Availability | SPARQL endpoint availability check for Legija Stranaca took 4.267692565917969e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0002949237823486328s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.26580214500427246s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.02106308937072754s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.1948089599609375e-05s
Believability | Calculation of trust value for Legija Stranaca took 7.3909759521484375e-06s
INFO | --- Analysis for Uros_Legija_Susa took 2.8904123306274414s
Availability | SPARQL endpoint availability check for Legija took 4.553794860839844e-05s
Availability | VoID file availability check for Legija took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Legija took 0.28084611892700195s
Reputation | Calculation of the PageRank for Legija took 0.020526647567749023s
Interlinking | Calculation of Degree of Connection for Legija took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Legija took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Legija took 3.147125244140625e-05s
Believability | Calculation of trust value for Legija took 1.2636184692382812e-05s
INFO | --- Analysis for Uros_Susa took 2.848996639251709s
Availability | SPARQL endpoint availability check for US Political Violence took 4.1961669921875e-05s
Availability | VoID file availability check for US Political Violence took 0.0002353191375732422s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.2391669750213623s
Reputation | Calculation of the PageRank for US Political Violence took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for US Political Violence took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.266334533691406e-05s
Believability | Calculation of trust value for US Political Violence took 1.2636184692382812e-05s
INFO | --- Analysis for us-political-violence took 2.8890135288238525s
Availability | SPARQL endpoint availability check for USAGE review corpus took 4.124641418457031e-05s
Availability | VoID file availability check for USAGE review corpus took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.26184678077697754s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 3.170967102050781e-05s
Believability | Calculation of trust value for USAGE review corpus took 7.62939453125e-06s
INFO | --- Analysis for usage-review-corpus took 2.792450428009033s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 4.172325134277344e-05s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.23485541343688965s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.02056884765625s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.581710815429688e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 7.3909759521484375e-06s
INFO | --- Analysis for utpl-lod took 2.899139165878296s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 4.220008850097656e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.2580699920654297s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.02032470703125s
Interlinking | Calculation of Degree of Connection for Výkazy zisku a ztrát obcí ČR took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Výkazy zisku a ztrát obcí ČR took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 2.86102294921875e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 1.1682510375976562e-05s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.8198158740997314s
Availability | SPARQL endpoint availability check for terrorist attack took 7.104873657226562e-05s
Availability | VoID file availability check for terrorist attack took 0.0006039142608642578s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.25475049018859863s
Reputation | Calculation of the PageRank for terrorist attack took 0.02040719985961914s
Interlinking | Calculation of Degree of Connection for terrorist attack took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for terrorist attack took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 3.0517578125e-05s
Believability | Calculation of trust value for terrorist attack took 1.3589859008789062e-05s
INFO | --- Analysis for varsha took 2.896134853363037s
Availability | SPARQL endpoint availability check for VA took 4.124641418457031e-05s
Availability | VoID file availability check for VA took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for VA took 0.2695317268371582s
Reputation | Calculation of the PageRank for VA took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for VA took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VA took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for VA took 3.0517578125e-05s
Believability | Calculation of trust value for VA took 7.62939453125e-06s
INFO | --- Analysis for Vehicule_Autonome took 2.847053050994873s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 4.267692565917969e-05s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.00026035308837890625s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.24483132362365723s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.022041797637939453s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 4.601478576660156e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 2.927851915359497s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 4.076957702636719e-05s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.2621421813964844s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.02052617073059082s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 8.463859558105469e-05s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 6.9141387939453125e-06s
INFO | --- Analysis for verrijktkoninkrijk took 2.88773250579834s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 0.00010418891906738281s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.0002586841583251953s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.26166725158691406s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.02061009407043457s
Interlinking | Calculation of Degree of Connection for VIAF: The Virtual International Authority File took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIAF: The Virtual International Authority File took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.00017213821411132812s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.1444091796875e-05s
INFO | --- Analysis for viaf took 2.8637173175811768s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.1484832763671875e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00023889541625976562s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.2619600296020508s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 1.2159347534179688e-05s
INFO | --- Analysis for vias-publicas-zaragoza took 2.84755539894104s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.076957702636719e-05s
Availability | VoID file availability check for Vihar Exports took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.26296019554138184s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 2.9325485229492188e-05s
Believability | Calculation of trust value for Vihar Exports took 7.3909759521484375e-06s
INFO | --- Analysis for Vihar_Exports took 2.8690927028656006s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 4.220008850097656e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.00027942657470703125s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.25452589988708496s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.02054429054260254s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 2.86102294921875e-05s
Believability | Calculation of trust value for vimeo.videoobject took 7.62939453125e-06s
INFO | --- Analysis for vimeo_videoobject took 2.9198238849639893s
Availability | SPARQL endpoint availability check for VIVO took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for VIVO took 0.2543354034423828s
Reputation | Calculation of the PageRank for VIVO took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for VIVO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO took 0.0007901191711425781s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.343292236328125e-05s
Believability | Calculation of trust value for VIVO took 7.152557373046875e-06s
INFO | --- Analysis for vivo took 2.8385257720947266s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.172325134277344e-05s
Availability | VoID file availability check for VIVO Cornell took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.24741601943969727s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.020334720611572266s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 7.748603820800781e-05s
Believability | Calculation of trust value for VIVO Cornell took 6.67572021484375e-06s
INFO | --- Analysis for vivo-cornell-university took 2.840726375579834s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 4.00543212890625e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0002510547637939453s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.2482624053955078s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020658254623413086s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 2.7894973754882812e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 6.4373016357421875e-06s
INFO | --- Analysis for vivo-cu-boulder took 2.779567003250122s
Availability | SPARQL endpoint availability check for VIVO Indiana took 4.076957702636719e-05s
Availability | VoID file availability check for VIVO Indiana took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.24892044067382812s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 7.724761962890625e-05s
Believability | Calculation of trust value for VIVO Indiana took 6.67572021484375e-06s
INFO | --- Analysis for vivo-indiana-university took 2.8395943641662598s
Availability | SPARQL endpoint availability check for VIVO Ponce took 4.029273986816406e-05s
Availability | VoID file availability check for VIVO Ponce took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.26059603691101074s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.266334533691406e-05s
Believability | Calculation of trust value for VIVO Ponce took 7.867813110351562e-06s
INFO | --- Analysis for vivo-ponce took 2.830811023712158s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 5.364418029785156e-05s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0003066062927246094s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.2548067569732666s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.021636486053466797s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 1.52587890625e-05s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0010540485382080078s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 4.744529724121094e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 7.867813110351562e-06s
INFO | --- Analysis for vivo-scripps-research-institute took 2.878909111022949s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 4.291534423828125e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.000278472900390625s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.2646303176879883s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.02084827423095703s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 9.942054748535156e-05s
Believability | Calculation of trust value for VIVO University of Florida took 8.106231689453125e-06s
INFO | --- Analysis for vivo-university-of-florida took 2.8254361152648926s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 4.124641418457031e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0002868175506591797s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.24985289573669434s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.021795272827148438s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.9577484130859375e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 7.867813110351562e-06s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.888026237487793s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 4.267692565917969e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.00027441978454589844s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.25609469413757324s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.814697265625e-05s
Believability | Calculation of trust value for VIVO WUSTL took 8.344650268554688e-06s
INFO | --- Analysis for vivo-wustl took 2.8746440410614014s
Availability | SPARQL endpoint availability check for vivo2doi took 4.100799560546875e-05s
Availability | VoID file availability check for vivo2doi took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.27467823028564453s
Reputation | Calculation of the PageRank for vivo2doi took 0.020796537399291992s
Interlinking | Calculation of Degree of Connection for vivo2doi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.38690185546875e-05s
Believability | Calculation of trust value for vivo2doi took 1.3113021850585938e-05s
INFO | --- Analysis for vivo2doi took 2.876189947128296s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 6.246566772460938e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.269500732421875s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.02076125144958496s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 8.034706115722656e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.2874603271484375e-05s
INFO | --- Analysis for vu-wordnet took 2.8104074001312256s
Availability | SPARQL endpoint availability check for vulnerapedia took 4.1484832763671875e-05s
Availability | VoID file availability check for vulnerapedia took 0.00028443336486816406s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.278947114944458s
Reputation | Calculation of the PageRank for vulnerapedia took 0.020956993103027344s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0008208751678466797s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 7.605552673339844e-05s
Believability | Calculation of trust value for vulnerapedia took 7.62939453125e-06s
INFO | --- Analysis for vulnerapedia took 2.784255266189575s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 7.796287536621094e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.25370144844055176s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.021018505096435547s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007436275482177734s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.3113021850585938e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 8.344650268554688e-06s
INFO | --- Analysis for VVASIAK took 2.892482042312622s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 4.2438507080078125e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.26987409591674805s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020586729049682617s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0006797313690185547s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.218650817871094e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 8.344650268554688e-06s
INFO | --- Analysis for Vyvasta took 2.8750052452087402s
Availability | SPARQL endpoint availability check for W3C took 4.172325134277344e-05s
Availability | VoID file availability check for W3C took 0.0002968311309814453s
Completeness | Calculation of interlinking completeness for W3C took 0.2782480716705322s
Reputation | Calculation of the PageRank for W3C took 0.02031421661376953s
Interlinking | Calculation of Degree of Connection for W3C took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for W3C took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for W3C took 0.00013947486877441406s
Believability | Calculation of trust value for W3C took 8.821487426757812e-06s
INFO | --- Analysis for w3c took 2.888843059539795s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.172325134277344e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.00030159950256347656s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.25516438484191895s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.020354509353637695s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 2.9802322387695312e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 7.152557373046875e-06s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.8465230464935303s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 4.1961669921875e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.2672126293182373s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.020555973052978516s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00011277198791503906s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 6.9141387939453125e-06s
INFO | --- Analysis for w3c-wordnet took 2.882030963897705s
Availability | SPARQL endpoint availability check for WarSampo took 0.3317148685455322s
Availability | VoID file availability check for WarSampo took 0.0005128383636474609s
Extra | Recovery of all triples for WarSampo took 27.188050746917725s
Performance | Total latancy measurement for WarSampo took 0.8415288925170898s
Amount of data | Number of triples check for WarSampo took 19.902167081832886s
Interoperability | New terms check for WarSampo took 3.7271268367767334s
Versatility | Languages check for WarSampo took 52.74472498893738s
Interpretability | Number of blank nodes check for WarSampo took 17.827111959457397s
Security | Check HTTPS for WarSampo took 0.43174290657043457s
Interpretability | RDF structures check for WarSampo took 0.18136858940124512s
Versatility | Serialization formats check for WarSampo took 0.1998457908630371s
Availability | RDF dump link check for WarSampo took 1.0454857349395752s
License | MR license check for WarSampo took 0.1680140495300293s
License | HR license check for WarSampo took 47.52210235595703s
Amount of data | Number of property check for WarSampo took 0.2029891014099121s
Understandability | Number of label check for WarSampo took 8.918001174926758s
Understandability | URI regex check for WarSampo took 0.3434736728668213s
Understandability | Vocabs check for WarSampo took 0.17205071449279785s
Verifiability | Authors check for WarSampo took 0.1720438003540039s
Verifiability | Publishers check for WarSampo took 0.16124844551086426s
Performance | Throughput check for WarSampo took 10.878220319747925s
Amount of data | Check the number of entities for WarSampo took 15.960704803466797s
Verifiability | Contribs. check for WarSampo took 0.17510461807250977s
Interlinking | sameAs chians check for WarSampo took 0.1849379539489746s
Interlinking | skos check for WarSampo took 0.1995997428894043s
Interlinking | skos check for WarSampo took 0.1687183380126953s
Timeliness | dataset update frequency check for WarSampo took 0.16696929931640625s
Currency | Creation date check for WarSampo took 0.3471996784210205s
Currency | Modification date check for WarSampo took 0.37281155586242676s
Rep.Conc. | URIs length for WarSampo took 51.19910287857056s
Interoperability | New vocabularies check for WarSampo took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.17158937454223633s
Accuracy | Check Functional Property for WarSampo took 0.16453075408935547s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17105698585510254s
Accuracy | Check Empty annotation labels for WarSampo took 11.348804235458374s
Accuracy | Check White space in annotation for WarSampo took 2.1824324131011963s
Accuracy | Check Datatype consistency for WarSampo took 5.270736932754517s
Consistency | Disjoint class check for WarSampo took 0.1798093318939209s
Consistency | Check Misplaced properties for WarSampo took 19.70747208595276s
Consistency | Check Ontology hijacking for WarSampo took 21.002800703048706s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.4390959739685059s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.728069543838501s
Conciseness | Check Extensional conciseness for WarSampo took 2.8179235458374023s
Conciseness | Check Intensional conciseness for WarSampo took 0.2382807731628418s
Security | Sign check for WarSampo took 0.1679987907409668s
Availability | Check URIs Dereferenciability for WarSampo took 2.7021260261535645s
Completeness | Calculation of interlinking completeness for WarSampo took 0.8502655029296875s
Reputation | Calculation of the PageRank for WarSampo took 0.020742177963256836s
Interlinking | Calculation of Degree of Connection for WarSampo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WarSampo took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for WarSampo took 8.106231689453125e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 1.6689300537109375e-06s
Believability | Calculation of trust value for WarSampo took 7.3909759521484375e-06s
INFO | --- Analysis for warsampo took 997.075617313385s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 0.18615055084228516s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0002593994140625s
Extra | Recovery of all triples for WASABI RDF Knowledge Graph took 2.6588523387908936s
Performance | Total latancy measurement for WASABI RDF Knowledge Graph took 0.3873112201690674s
Amount of data | Number of triples check for WASABI RDF Knowledge Graph took 73.7117612361908s
Interoperability | New terms check for WASABI RDF Knowledge Graph took 2.4027040004730225s
Versatility | Languages check for WASABI RDF Knowledge Graph took 300.0682818889618s
Interpretability | Number of blank nodes check for WASABI RDF Knowledge Graph took 83.53561878204346s
Interpretability | RDF structures check for WASABI RDF Knowledge Graph took 0.1405026912689209s
Versatility | Serialization formats check for WASABI RDF Knowledge Graph took 0.1492147445678711s
Availability | RDF dump link check for WASABI RDF Knowledge Graph took 3.3109986782073975s
License | MR license check for WASABI RDF Knowledge Graph took 0.17385554313659668s
License | HR license check for WASABI RDF Knowledge Graph took 300.079962015152s
Amount of data | Number of property check for WASABI RDF Knowledge Graph took 0.11924362182617188s
Understandability | Number of label check for WASABI RDF Knowledge Graph took 3.3164472579956055s
Understandability | URI regex check for WASABI RDF Knowledge Graph took 0.34966063499450684s
Understandability | Vocabs check for WASABI RDF Knowledge Graph took 0.0798027515411377s
Verifiability | Authors check for WASABI RDF Knowledge Graph took 0.08216524124145508s
Verifiability | Publishers check for WASABI RDF Knowledge Graph took 0.08679533004760742s
Performance | Throughput check for WASABI RDF Knowledge Graph took 10.423919677734375s
Amount of data | Check the number of entities for WASABI RDF Knowledge Graph took 0.11599493026733398s
Verifiability | Contribs. check for WASABI RDF Knowledge Graph took 0.20522546768188477s
Interlinking | sameAs chians check for WASABI RDF Knowledge Graph took 0.08144736289978027s
Interlinking | skos check for WASABI RDF Knowledge Graph took 0.07786917686462402s
Interlinking | skos check for WASABI RDF Knowledge Graph took 0.07841706275939941s
Timeliness | dataset update frequency check for WASABI RDF Knowledge Graph took 0.353041410446167s
Currency | Creation date check for WASABI RDF Knowledge Graph took 0.15462303161621094s
Currency | Modification date check for WASABI RDF Knowledge Graph took 0.14122867584228516s
Rep.Conc. | URIs length for WASABI RDF Knowledge Graph took 91.73745560646057s
Interoperability | New vocabularies check for WASABI RDF Knowledge Graph took 43.118160247802734s
Consistency | Deprecated classes/propertiers check for WASABI RDF Knowledge Graph took 0.08095026016235352s
Accuracy | Check Functional Property for WASABI RDF Knowledge Graph took 0.216933012008667s
Accuracy | Check Inverse Functional Property for WASABI RDF Knowledge Graph took 0.24286699295043945s
Accuracy | Check Empty annotation labels for WASABI RDF Knowledge Graph took 0.9678797721862793s
Accuracy | Check White space in annotation for WASABI RDF Knowledge Graph took 0.08539605140686035s
Accuracy | Check Datatype consistency for WASABI RDF Knowledge Graph took 0.0804891586303711s
Consistency | Disjoint class check for WASABI RDF Knowledge Graph took 0.06758284568786621s
Consistency | Check Misplaced properties for WASABI RDF Knowledge Graph took 52.886478662490845s
Consistency | Misplaced classes for WASABI RDF Knowledge Graph took 1.394526481628418s
Consistency | Check Ontology hijacking for WASABI RDF Knowledge Graph took 2.500410318374634s
Consistency | Check Invalid usage of undefined classes for WASABI RDF Knowledge Graph took 1.715296983718872s
Consistency | Check Invalid usage of undefined properties for WASABI RDF Knowledge Graph took 33.77462077140808s
Conciseness | Check Extensional conciseness for WASABI RDF Knowledge Graph took 0.0866994857788086s
Conciseness | Check Intensional conciseness for WASABI RDF Knowledge Graph took 1.3161182403564453s
Security | Sign check for WASABI RDF Knowledge Graph took 0.41141557693481445s
Availability | Check URIs Dereferenciability for WASABI RDF Knowledge Graph took 16.947463512420654s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.9060502052307129s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.024103403091430664s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 2.2172927856445312e-05s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 8.726119995117188e-05s
Interoperability | Check the re-using of existing vocabs for WASABI RDF Knowledge Graph took 45.949281215667725s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 8.58306884765625e-06s
INFO | --- Analysis for wasabi took 11873.960288763046s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 4.029273986816406e-05s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.2476356029510498s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.020538330078125s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 2.7894973754882812e-05s
Believability | Calculation of trust value for FAO water areas classification as linked data @PSNC took 1.1444091796875e-05s
INFO | --- Analysis for Water_Areas_Classification took 5.229197978973389s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 4.00543212890625e-05s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.27872395515441895s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 2.9087066650390625e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.1682510375976562e-05s
INFO | --- Analysis for Water_Buffer took 3.7151052951812744s
Availability | SPARQL endpoint availability check for WebIsALOD took 3.981590270996094e-05s
Availability | VoID file availability check for WebIsALOD took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.2521646022796631s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02205657958984375s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0014314651489257812s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 0.0001049041748046875s
Believability | Calculation of trust value for WebIsALOD took 8.344650268554688e-06s
INFO | --- Analysis for webisalod took 2.7773585319519043s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 6.031990051269531e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.25107312202453613s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.021372079849243164s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0010776519775390625s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 4.315376281738281e-05s
Believability | Calculation of trust value for webnmasunotraveler took 7.3909759521484375e-06s
INFO | --- Analysis for webnmasunotraveler took 2.855328321456909s
Availability | SPARQL endpoint availability check for Whisky Circle took 4.124641418457031e-05s
Availability | VoID file availability check for Whisky Circle took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.24965119361877441s
Reputation | Calculation of the PageRank for Whisky Circle took 0.020746707916259766s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0008823871612548828s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00011515617370605469s
Believability | Calculation of trust value for Whisky Circle took 8.821487426757812e-06s
INFO | --- Analysis for whisky-circle-info took 2.8972511291503906s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.2409191131591797s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.4332275390625e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 6.67572021484375e-06s
INFO | --- Analysis for WHOnto took 2.7795798778533936s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0003495216369628906s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.27591705322265625s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 7.62939453125e-06s
INFO | --- Analysis for whonto took 2.8217713832855225s
Availability | SPARQL endpoint availability check for Wikidata took 5.078315734863281e-05s
Availability | VoID file availability check for Wikidata took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for Wikidata took 0.2352454662322998s
Reputation | Calculation of the PageRank for Wikidata took 0.02029728889465332s
Interlinking | Calculation of Degree of Connection for Wikidata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Wikidata took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.0002815723419189453s
Believability | Calculation of trust value for Wikidata took 8.344650268554688e-06s
INFO | --- Analysis for wikidata took 2.796340227127075s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 4.100799560546875e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00032520294189453125s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.2517523765563965s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007567405700683594s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.747245788574219e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.2636184692382812e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 2.8318190574645996s
Availability | SPARQL endpoint availability check for WikiPathways took 4.029273986816406e-05s
Availability | VoID file availability check for WikiPathways took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.258284330368042s
Reputation | Calculation of the PageRank for WikiPathways took 0.020659208297729492s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0009121894836425781s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.2901763916015625e-05s
Believability | Calculation of trust value for WikiPathways took 7.152557373046875e-06s
INFO | --- Analysis for wikipathways took 2.8077001571655273s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 4.124641418457031e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0003180503845214844s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.25511908531188965s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.02042984962463379s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0007519721984863281s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 2.8371810913085938e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 6.9141387939453125e-06s
INFO | --- Analysis for wikiword_thesaurus took 2.7992138862609863s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 4.220008850097656e-05s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.0003085136413574219s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.24563932418823242s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020382165908813477s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.487701416015625e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 7.152557373046875e-06s
INFO | --- Analysis for wiktionary-dbpedia-org took 2.7968666553497314s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 3.981590270996094e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0002951622009277344s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.2609536647796631s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.020414352416992188s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Wings workflow provenance dataset took 3.0279159545898438e-05s
Believability | Calculation of trust value for Wings workflow provenance dataset took 7.152557373046875e-06s
INFO | --- Analysis for wings-workflow-provenance-dataset took 2.8557939529418945s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.2146289348602295s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0003008842468261719s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.25400662422180176s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.02032947540283203s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for The World Literature Knowledge Graph took 2.7894973754882812e-05s
Believability | Calculation of trust value for The World Literature Knowledge Graph took 7.152557373046875e-06s
INFO | --- Analysis for wl-kg took 4.282700300216675s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.57763671875e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.24872684478759766s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.020530223846435547s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 6.937980651855469e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 7.152557373046875e-06s
INFO | --- Analysis for wn-wiki-instances took 2.8321399688720703s
Availability | SPARQL endpoint availability check for World Loanword Database took 4.076957702636719e-05s
Availability | VoID file availability check for World Loanword Database took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.2661011219024658s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 7.510185241699219e-05s
Believability | Calculation of trust value for World Loanword Database took 1.621246337890625e-05s
INFO | --- Analysis for wold took 2.8351902961730957s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 3.8623809814453125e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0002536773681640625s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.24869942665100098s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.020252704620361328s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 2.765655517578125e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.2636184692382812e-05s
INFO | --- Analysis for woodtrick took 2.850043535232544s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 4.100799560546875e-05s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.00023508071899414062s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.2644796371459961s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 4.410743713378906e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 6.9141387939453125e-06s
INFO | --- Analysis for WordFormationLatin took 2.790127754211426s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 5.078315734863281e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.25029826164245605s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.02007460594177246s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0007929801940917969s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 0.00010395050048828125s
Believability | Calculation of trust value for WordLift Blog EN took 9.059906005859375e-06s
INFO | --- Analysis for wordlift-io-blog-en took 2.8745315074920654s
Availability | SPARQL endpoint availability check for WordLift IT took 4.291534423828125e-05s
Availability | VoID file availability check for WordLift IT took 0.0002655982971191406s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.26159238815307617s
Reputation | Calculation of the PageRank for WordLift IT took 0.021831035614013672s
Interlinking | Calculation of Degree of Connection for WordLift IT took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for WordLift IT took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 0.00011086463928222656s
Believability | Calculation of trust value for WordLift IT took 7.867813110351562e-06s
INFO | --- Analysis for wordlift-io-blog-it took 2.8602917194366455s
Availability | SPARQL endpoint availability check for Wordnet took 4.172325134277344e-05s
Availability | VoID file availability check for Wordnet took 0.0006134510040283203s
Completeness | Calculation of interlinking completeness for Wordnet took 0.2664639949798584s
Reputation | Calculation of the PageRank for Wordnet took 0.020778894424438477s
Interlinking | Calculation of Degree of Connection for Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Wordnet took 0.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Wordnet took 4.696846008300781e-05s
Believability | Calculation of trust value for Wordnet took 1.2159347534179688e-05s
INFO | --- Analysis for wordnet took 2.865668535232544s
Availability | SPARQL endpoint availability check for WordNet-RDF took 4.029273986816406e-05s
Availability | VoID file availability check for WordNet-RDF took 0.000370025634765625s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.2747197151184082s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 9.298324584960938e-05s
Believability | Calculation of trust value for WordNet-RDF took 8.106231689453125e-06s
INFO | --- Analysis for wordnet-rdf took 2.8610808849334717s
Availability | SPARQL endpoint availability check for wordpress took 4.029273986816406e-05s
Availability | VoID file availability check for wordpress took 0.0002574920654296875s
Completeness | Calculation of interlinking completeness for wordpress took 0.26330137252807617s
Reputation | Calculation of the PageRank for wordpress took 0.020167112350463867s
Interlinking | Calculation of Degree of Connection for wordpress took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for wordpress took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.368492126464844e-05s
Believability | Calculation of trust value for wordpress took 7.152557373046875e-06s
INFO | --- Analysis for wordpress took 2.785741090774536s
Availability | SPARQL endpoint availability check for wordpress.post took 4.076957702636719e-05s
Availability | VoID file availability check for wordpress.post took 0.0003161430358886719s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.25266098976135254s
Reputation | Calculation of the PageRank for wordpress.post took 0.020318031311035156s
Interlinking | Calculation of Degree of Connection for wordpress.post took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007462501525878906s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 2.9802322387695312e-05s
Believability | Calculation of trust value for wordpress.post took 6.9141387939453125e-06s
INFO | --- Analysis for wordpress_post took 2.86700701713562s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 6.4849853515625e-05s
Availability | VoID file availability check for World Bank Linked Data took 0.0002932548522949219s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.28080010414123535s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00012493133544921875s
Believability | Calculation of trust value for World Bank Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for world-bank-linked-data took 2.921445369720459s
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.00026154518127441406s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.2478795051574707s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02070474624633789s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 8.988380432128906e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 8.106231689453125e-06s
INFO | --- Analysis for world-factbook-fu-berlin took 2.7960190773010254s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.220008850097656e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.2714104652404785s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.58306884765625e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 6.9141387939453125e-06s
INFO | --- Analysis for world-wide-web-foundation took 2.877561569213867s
Availability | SPARQL endpoint availability check for WikiPathways took 4.00543212890625e-05s
Availability | VoID file availability check for WikiPathways took 0.00022935867309570312s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.2786245346069336s
Reputation | Calculation of the PageRank for WikiPathways took 0.020717620849609375s
Interlinking | Calculation of Degree of Connection for WikiPathways took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for WikiPathways took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 3.0040740966796875e-05s
Believability | Calculation of trust value for WikiPathways took 7.152557373046875e-06s
INFO | --- Analysis for wp took 2.9211225509643555s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 3.910064697265625e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.23791980743408203s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.020508527755737305s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.00075531005859375s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.123283386230469e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 7.867813110351562e-06s
INFO | --- Analysis for wunderground_weatherreport took 2.7494258880615234s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.27240872383117676s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0002636909484863281s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.9913265705108643s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.8486261367797852s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.2237541675567627s
Interoperability | New terms check for World War 1 as Linked Open Data took 2.0854249000549316s
Versatility | Languages check for World War 1 as Linked Open Data took 0.5890660285949707s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.21962904930114746s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.4433634281158447s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.3569338321685791s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.22064518928527832s
Availability | RDF dump link check for World War 1 as Linked Open Data took 6.95863938331604s
License | MR license check for World War 1 as Linked Open Data took 0.17303943634033203s
License | HR license check for World War 1 as Linked Open Data took 1.6271085739135742s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.1639695167541504s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.48894166946411133s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.33310961723327637s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.22618889808654785s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.16136479377746582s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.16670632362365723s
Performance | Throughput check for World War 1 as Linked Open Data took 10.819147109985352s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.07601332664489746s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.1712808609008789s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.19600701332092285s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1788311004638672s
Interlinking | skos check for World War 1 as Linked Open Data took 0.16191649436950684s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.3094613552093506s
Currency | Creation date check for World War 1 as Linked Open Data took 0.32613134384155273s
Currency | Modification date check for World War 1 as Linked Open Data took 0.16710662841796875s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.0438764095306396s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 24.86618733406067s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.1964707374572754s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.15680956840515137s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.16833949089050293s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.2173926830291748s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.050108909606933594s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.32135438919067383s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.17191648483276367s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6171095371246338s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.0811054706573486s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.3182401657104492s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.5711095333099365s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.1917743682861328s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.7500224113464355s
Security | Sign check for World War 1 as Linked Open Data took 0.20891976356506348s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1508.1563351154327s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.8939027786254883s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02186298370361328s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0007874965667724609s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.0002448558807373047s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 23.442508459091187s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for ww1lod took 1629.9373126029968s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 5.0067901611328125e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.25815868377685547s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 2.8848648071289062e-05s
Believability | Calculation of trust value for XlendiAmphorae took 7.152557373046875e-06s
INFO | --- Analysis for xlendiamphorae took 4.118718385696411s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 4.076957702636719e-05s
Availability | VoID file availability check for xLiD-Lexica took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.2461230754852295s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020624399185180664s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.985664367675781e-05s
Believability | Calculation of trust value for xLiD-Lexica took 7.152557373046875e-06s
INFO | --- Analysis for xlid-lexica took 2.875065803527832s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 3.981590270996094e-05s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.2534372806549072s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0006766319274902344s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.62396240234375e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 7.152557373046875e-06s
INFO | --- Analysis for xwn took 2.802753210067749s
Availability | SPARQL endpoint availability check for xxx took 4.029273986816406e-05s
Availability | VoID file availability check for xxx took 0.0002529621124267578s
Completeness | Calculation of interlinking completeness for xxx took 0.25536322593688965s
Reputation | Calculation of the PageRank for xxx took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for xxx took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for xxx took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for xxx took 2.8371810913085938e-05s
Believability | Calculation of trust value for xxx took 6.9141387939453125e-06s
INFO | --- Analysis for xx took 2.8092424869537354s
Availability | SPARQL endpoint availability check for YAGO took 4.029273986816406e-05s
Availability | VoID file availability check for YAGO took 0.0002257823944091797s
Completeness | Calculation of interlinking completeness for YAGO took 0.2460801601409912s
Reputation | Calculation of the PageRank for YAGO took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for YAGO took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for YAGO took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.0001251697540283203s
Believability | Calculation of trust value for YAGO took 7.3909759521484375e-06s
INFO | --- Analysis for yago took 2.788982629776001s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.2477095127105713s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 8.130073547363281e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 2.0265579223632812e-05s
INFO | --- Analysis for yahoo_geoplanet took 3.2206010818481445s
Availability | SPARQL endpoint availability check for Yale Senselab took 4.0531158447265625e-05s
Availability | VoID file availability check for Yale Senselab took 0.0002777576446533203s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.2879023551940918s
Reputation | Calculation of the PageRank for Yale Senselab took 0.02012324333190918s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Yale Senselab took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.9087066650390625e-05s
Believability | Calculation of trust value for Yale Senselab took 1.2874603271484375e-05s
INFO | --- Analysis for yale_senselab took 2.8513545989990234s
Availability | SPARQL endpoint availability check for test-dapp-2 took 3.981590270996094e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.2516481876373291s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.02068805694580078s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 3.0040740966796875e-05s
Believability | Calculation of trust value for test-dapp-2 took 6.9141387939453125e-06s
INFO | --- Analysis for yordhis took 2.768833637237549s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 4.506111145019531e-05s
Availability | VoID file availability check for Yovisto - academic video search took 0.00026726722717285156s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.2601287364959717s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.020313024520874023s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.580352783203125e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.2636184692382812e-05s
INFO | --- Analysis for yovisto took 2.8503835201263428s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 3.933906555175781e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.25342893600463867s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.409385681152344e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 6.198883056640625e-06s
INFO | --- Analysis for ysa took 2.8374741077423096s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 5.555152893066406e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.26761317253112793s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 5.0067901611328125e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 6.67572021484375e-06s
INFO | --- Analysis for yso took 2.8167760372161865s
Availability | SPARQL endpoint availability check for yso-fi-allars took 3.9577484130859375e-05s
Availability | VoID file availability check for yso-fi-allars took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.2556893825531006s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.02093052864074707s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0009684562683105469s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 4.0531158447265625e-05s
Believability | Calculation of trust value for yso-fi-allars took 1.2159347534179688e-05s
INFO | --- Analysis for yso-fi-allars took 2.8329362869262695s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 3.981590270996094e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.255157470703125s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020125150680541992s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0006775856018066406s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.266334533691406e-05s
Believability | Calculation of trust value for yso-fi-ysa took 1.3113021850585938e-05s
INFO | --- Analysis for yso-fi-ysa took 2.8928916454315186s
Availability | SPARQL endpoint availability check for YSO places took 4.2438507080078125e-05s
Availability | VoID file availability check for YSO places took 0.00026679039001464844s
Completeness | Calculation of interlinking completeness for YSO places took 0.2642800807952881s
Reputation | Calculation of the PageRank for YSO places took 0.020580768585205078s
Interlinking | Calculation of Degree of Connection for YSO places took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for YSO places took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for YSO places took 3.0279159545898438e-05s
Believability | Calculation of trust value for YSO places took 5.7220458984375e-06s
INFO | --- Analysis for yso-paikat took 2.8782386779785156s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 3.933906555175781e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.24966645240783691s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.021077394485473633s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 3.361701965332031e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 7.62939453125e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 2.7730023860931396s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.00543212890625e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.0003142356872558594s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.277454137802124s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.24249267578125e-05s
Believability | Calculation of trust value for zaragoza_turruta took 6.67572021484375e-06s
INFO | --- Analysis for zaragoza_turruta took 2.8664333820343018s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.076957702636719e-05s
Availability | VoID file availability check for ZBW Labs took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.2551133632659912s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02088785171508789s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 7.534027099609375e-05s
Believability | Calculation of trust value for ZBW Labs took 7.62939453125e-06s
INFO | --- Analysis for zbw-labs took 2.7944324016571045s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.39224982261657715s
Availability | VoID file availability check for 20th Century Press Archives took 0.00031757354736328125s
Extra | Recovery of all triples for 20th Century Press Archives took 32.97420072555542s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7467584609985352s
Amount of data | Number of triples check for 20th Century Press Archives took 1.2341375350952148s
Interoperability | New terms check for 20th Century Press Archives took 1.7242369651794434s
Versatility | Languages check for 20th Century Press Archives took 3.2704763412475586s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.9078917503356934s
Interpretability | RDF structures check for 20th Century Press Archives took 0.1520094871520996s
Versatility | Serialization formats check for 20th Century Press Archives took 0.13790273666381836s
Availability | RDF dump link check for 20th Century Press Archives took 0.13639593124389648s
License | MR license check for 20th Century Press Archives took 0.12827038764953613s
License | HR license check for 20th Century Press Archives took 5.53402042388916s
Amount of data | Number of property check for 20th Century Press Archives took 0.17279624938964844s
Understandability | Number of label check for 20th Century Press Archives took 0.5354900360107422s
Understandability | URI regex check for 20th Century Press Archives took 0.33707356452941895s
Understandability | Vocabs check for 20th Century Press Archives took 0.14740920066833496s
Verifiability | Authors check for 20th Century Press Archives took 0.16293883323669434s
Verifiability | Publishers check for 20th Century Press Archives took 0.16063165664672852s
Performance | Throughput check for 20th Century Press Archives took 10.716268301010132s
Amount of data | Check the number of entities for 20th Century Press Archives took 7.295608520507812e-05s
Verifiability | Contribs. check for 20th Century Press Archives took 0.1264207363128662s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.13957762718200684s
Interlinking | skos check for 20th Century Press Archives took 0.21161627769470215s
Interlinking | skos check for 20th Century Press Archives took 0.17742276191711426s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.16302967071533203s
Currency | Creation date check for 20th Century Press Archives took 0.31394219398498535s
Currency | Modification date check for 20th Century Press Archives took 0.2868764400482178s
Rep.Conc. | URIs length for 20th Century Press Archives took 15.426922082901001s
Interoperability | New vocabularies check for 20th Century Press Archives took 1.049041748046875e-05s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1600189208984375s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.14632511138916016s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.15136361122131348s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 5.433862924575806s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8850910663604736s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.011247158050537s
Consistency | Disjoint class check for 20th Century Press Archives took 0.15090131759643555s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.2952611446380615s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.456474542617798s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 7.6280198097229s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.572089672088623s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7833352088928223s
Security | Sign check for 20th Century Press Archives took 0.1647050380706787s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 946.4778509140015s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 1.4143152236938477s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.022227764129638672s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 6.413459777832031e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007798671722412109s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.0002052783966064453s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 1.6689300537109375e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.1920928955078125e-05s
INFO | --- Analysis for zbw-pressemappe20 took 1072.47869515419s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.267692565917969e-05s
Availability | VoID file availability check for zhishi.lemon took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.2574272155761719s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.021112442016601562s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.76837158203125e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.33514404296875e-05s
INFO | --- Analysis for zhishi-lemon took 4.5989344120025635s
Availability | SPARQL endpoint availability check for Zhishi.me took 4.00543212890625e-05s
Availability | VoID file availability check for Zhishi.me took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.26528072357177734s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.367134094238281e-05s
Believability | Calculation of trust value for Zhishi.me took 7.62939453125e-06s
INFO | --- Analysis for zhishi-me took 3.2227203845977783s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 4.482269287109375e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0002865791320800781s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.27687621116638184s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.020691871643066406s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 6.079673767089844e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 7.62939453125e-06s
INFO | --- Analysis for zitgist-musicbrainz took 2.885183811187744s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 5.054473876953125e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.24491548538208008s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.020869970321655273s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 8.106231689453125e-06s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.851146936416626s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.3134500980377197s
Availability | VoID file availability check for performing-arts.ch took 0.0003185272216796875s
Extra | Recovery of all triples for performing-arts.ch took 20.127387762069702s
Performance | Total latancy measurement for performing-arts.ch took 0.769644021987915s
Amount of data | Number of triples check for performing-arts.ch took 58.49322271347046s
Interoperability | New terms check for performing-arts.ch took 1.4771099090576172s
Versatility | Languages check for performing-arts.ch took 60.141350746154785s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.1397590637207s
Interpretability | RDF structures check for performing-arts.ch took 0.9087972640991211s
Versatility | Serialization formats check for performing-arts.ch took 0.18545866012573242s
Availability | RDF dump link check for performing-arts.ch took 0.14488792419433594s
License | MR license check for performing-arts.ch took 0.16053104400634766s
License | HR license check for performing-arts.ch took 54.35185527801514s
Amount of data | Number of property check for performing-arts.ch took 0.1861579418182373s
Understandability | Number of label check for performing-arts.ch took 2.5665576457977295s
Understandability | URI regex check for performing-arts.ch took 0.3137032985687256s
Understandability | Vocabs check for performing-arts.ch took 0.1771245002746582s
Verifiability | Authors check for performing-arts.ch took 0.1759812831878662s
Verifiability | Publishers check for performing-arts.ch took 0.17397546768188477s
Performance | Throughput check for performing-arts.ch took 10.81981372833252s
Amount of data | Check the number of entities for performing-arts.ch took 7.700920104980469e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.14396357536315918s
Interlinking | sameAs chians check for performing-arts.ch took 0.6117563247680664s
Interlinking | skos check for performing-arts.ch took 0.16688847541809082s
Interlinking | skos check for performing-arts.ch took 0.15675830841064453s
Timeliness | dataset update frequency check for performing-arts.ch took 0.16385555267333984s
Currency | Creation date check for performing-arts.ch took 0.3358955383300781s
Currency | Modification date check for performing-arts.ch took 0.31684446334838867s
Rep.Conc. | URIs length for performing-arts.ch took 21.24900984764099s
Interoperability | New vocabularies check for performing-arts.ch took 9.298324584960938e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.14383935928344727s
Accuracy | Check Functional Property for performing-arts.ch took 0.1704702377319336s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.15628552436828613s
Accuracy | Check Empty annotation labels for performing-arts.ch took 10.036998510360718s
Accuracy | Check White space in annotation for performing-arts.ch took 2.4952592849731445s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.736684083938599s
Consistency | Disjoint class check for performing-arts.ch took 0.1734929084777832s
Consistency | Check Misplaced properties for performing-arts.ch took 0.37328195571899414s
Consistency | Misplaced classes for performing-arts.ch took 8.517196655273438s
Consistency | Check Ontology hijacking for performing-arts.ch took 48.249287128448486s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15586.985315561295s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.8524744510650635s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.86383056640625s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.30927586555480957s
Security | Sign check for performing-arts.ch took 0.14318203926086426s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.25238037109375s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 1.5114552974700928s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.022261381149291992s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 2.7894973754882812e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0009434223175048828s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 2.3126602172851562e-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 1.1682510375976562e-05s
INFO | --- Analysis for performing-arts.ch took 16433.48952436447s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.6810550689697266s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0007073879241943359s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.6821298599243164s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.020669221878051758s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.4066696166992188e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 8.821487426757812e-06s
INFO | --- Analysis for The-AA-Thesaurus took 10.505495309829712s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.3998689651489258s
Availability | VoID file availability check for MiMoTextBase took 0.0006489753723144531s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.2555720806121826s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020809412002563477s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.3589859008789062e-05s
Believability | Calculation of trust value for MiMoTextBase took 8.106231689453125e-06s
INFO | --- Analysis for MiMoTextBase took 6.934959650039673s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.45854663848876953s
Availability | VoID file availability check for National Library of Sweden took 0.0006611347198486328s
Extra | Recovery of all triples for National Library of Sweden took 5.533208131790161s
Performance | Total latancy measurement for National Library of Sweden took 1.0304791927337646s
Amount of data | Number of triples check for National Library of Sweden took 18.624810457229614s
Interoperability | New terms check for National Library of Sweden took 15.780333995819092s
Versatility | Languages check for National Library of Sweden took 0.2126471996307373s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.1930601596832s
Interpretability | RDF structures check for National Library of Sweden took 0.23243379592895508s
Versatility | Serialization formats check for National Library of Sweden took 0.23208212852478027s
Availability | RDF dump link check for National Library of Sweden took 0.22431468963623047s
License | MR license check for National Library of Sweden took 0.2144477367401123s
License | HR license check for National Library of Sweden took 0.2599465847015381s
Amount of data | Number of property check for National Library of Sweden took 0.21416115760803223s
Understandability | Number of label check for National Library of Sweden took 0.20713019371032715s
Understandability | URI regex check for National Library of Sweden took 0.42526912689208984s
Understandability | Vocabs check for National Library of Sweden took 0.21208715438842773s
Verifiability | Authors check for National Library of Sweden took 0.21334147453308105s
Verifiability | Publishers check for National Library of Sweden took 0.23202991485595703s
Performance | Throughput check for National Library of Sweden took 10.676687717437744s
Amount of data | Check the number of entities for National Library of Sweden took 6.866455078125e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.21414542198181152s
Interlinking | sameAs chians check for National Library of Sweden took 0.2137758731842041s
Interlinking | skos check for National Library of Sweden took 0.26110076904296875s
Interlinking | skos check for National Library of Sweden took 0.22475147247314453s
Timeliness | dataset update frequency check for National Library of Sweden took 0.20226073265075684s
Currency | Creation date check for National Library of Sweden took 0.4158041477203369s
Currency | Modification date check for National Library of Sweden took 0.40578699111938477s
Rep.Conc. | URIs length for National Library of Sweden took 79.6667730808258s
Interoperability | New vocabularies check for National Library of Sweden took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.22372984886169434s
Accuracy | Check Functional Property for National Library of Sweden took 0.2232222557067871s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.21204900741577148s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.27805233001708984s
Consistency | Disjoint class check for National Library of Sweden took 0.2212810516357422s
Consistency | Check Misplaced properties for National Library of Sweden took 62.307631969451904s
Consistency | Misplaced classes for National Library of Sweden took 1.1339504718780518s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.2484548091888428s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3259572982788086s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 63.11488461494446s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.2811768054962158s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.37180376052856445s
Security | Sign check for National Library of Sweden took 0.2234487533569336s
Availability | Check URIs Dereferenciability for National Library of Sweden took 17.458903074264526s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 1.290175437927246s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.0209348201751709s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 2.1219253540039062e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.430511474609375e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.1920928955078125e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.1444091796875e-05s
INFO | --- Analysis for NLS took 1385.626643896103s
Availability | SPARQL endpoint availability check for Japan Search took 2.3423495292663574s
Availability | VoID file availability check for Japan Search took 0.0003275871276855469s
Extra | Recovery of all triples for Japan Search took 3.5782008171081543s
Performance | Total latancy measurement for Japan Search took 2.6246063709259033s
Amount of data | Number of triples check for Japan Search took 5.551866054534912s
Interoperability | New terms check for Japan Search took 3.814683437347412s
Versatility | Languages check for Japan Search took 0.9488785266876221s
Interpretability | Number of blank nodes check for Japan Search took 12.244092464447021s
Interpretability | RDF structures check for Japan Search took 0.9529938697814941s
Versatility | Serialization formats check for Japan Search took 0.5009818077087402s
Availability | RDF dump link check for Japan Search took 0.35477519035339355s
License | MR license check for Japan Search took 0.6902413368225098s
License | HR license check for Japan Search took 10.29481315612793s
Amount of data | Number of property check for Japan Search took 0.756903886795044s
Understandability | Number of label check for Japan Search took 2.564084529876709s
Understandability | URI regex check for Japan Search took 1.016265869140625s
Understandability | Vocabs check for Japan Search took 0.26555609703063965s
Verifiability | Authors check for Japan Search took 0.3822135925292969s
Verifiability | Publishers check for Japan Search took 0.28124547004699707s
Performance | Throughput check for Japan Search took 11.303257703781128s
Amount of data | Check the number of entities for Japan Search took 7.009506225585938e-05s
Verifiability | Contribs. check for Japan Search took 0.30303955078125s
Interlinking | sameAs chians check for Japan Search took 0.3138108253479004s
Interlinking | skos check for Japan Search took 0.3363838195800781s
Interlinking | skos check for Japan Search took 0.26691198348999023s
Timeliness | dataset update frequency check for Japan Search took 0.43448686599731445s
Currency | Creation date check for Japan Search took 0.6098229885101318s
Currency | Modification date check for Japan Search took 0.5456368923187256s
Rep.Conc. | URIs length for Japan Search took 14.45094108581543s
Interoperability | New vocabularies check for Japan Search took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7235682010650635s
Accuracy | Check Empty annotation labels for Japan Search took 1.5298962593078613s
Accuracy | Check White space in annotation for Japan Search took 0.029004812240600586s
Accuracy | Check Datatype consistency for Japan Search took 0.027960538864135742s
Consistency | Disjoint class check for Japan Search took 0.2860677242279053s
Consistency | Check Misplaced properties for Japan Search took 12.163959980010986s
Consistency | Misplaced classes for Japan Search took 1.0667638778686523s
Consistency | Check Ontology hijacking for Japan Search took 2.8128163814544678s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.337207555770874s
Consistency | Check Invalid usage of undefined properties for Japan Search took 12.83501935005188s
Conciseness | Check Extensional conciseness for Japan Search took 0.03679656982421875s
Conciseness | Check Intensional conciseness for Japan Search took 0.9781913757324219s
Security | Sign check for Japan Search took 0.7523202896118164s
Availability | Check URIs Dereferenciability for Japan Search took 15.586269617080688s
Completeness | Calculation of interlinking completeness for Japan Search took 0.7314655780792236s
Reputation | Calculation of the PageRank for Japan Search took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Japan Search took 1.33514404296875e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 9.5367431640625e-07s
Believability | Calculation of trust value for Japan Search took 3.552436828613281e-05s
INFO | --- Analysis for Japan-Search took 411.1164836883545s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.107497215270996s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.25818657875061035s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.02142620086669922s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.3828277587890625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.7404556274414062e-05s
INFO | --- Analysis for Rijksmuseum took 4.629603147506714s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 0.4604930877685547s
Availability | VoID file availability check for Finnish Public Libraries took 0.0005567073822021484s
Extra | Recovery of all triples for Finnish Public Libraries took 18.31544518470764s
Performance | Total latancy measurement for Finnish Public Libraries took 1.16294264793396s
Amount of data | Number of triples check for Finnish Public Libraries took 60.27901530265808s
Interoperability | New terms check for Finnish Public Libraries took 17.829005241394043s
Versatility | Languages check for Finnish Public Libraries took 60.28687334060669s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 60.33507704734802s
Interpretability | RDF structures check for Finnish Public Libraries took 0.4859120845794678s
Versatility | Serialization formats check for Finnish Public Libraries took 0.33542346954345703s
Availability | RDF dump link check for Finnish Public Libraries took 0.27475666999816895s
License | MR license check for Finnish Public Libraries took 0.13371896743774414s
License | HR license check for Finnish Public Libraries took 57.25826597213745s
Amount of data | Number of property check for Finnish Public Libraries took 0.397519588470459s
Understandability | Number of label check for Finnish Public Libraries took 15.662243127822876s
Understandability | URI regex check for Finnish Public Libraries took 0.27715611457824707s
Understandability | Vocabs check for Finnish Public Libraries took 0.4234042167663574s
Verifiability | Authors check for Finnish Public Libraries took 0.13287067413330078s
Verifiability | Publishers check for Finnish Public Libraries took 0.7980823516845703s
Performance | Throughput check for Finnish Public Libraries took 11.503009557723999s
Amount of data | Check the number of entities for Finnish Public Libraries took 6.914138793945312e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.13501358032226562s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.3181133270263672s
Interlinking | skos check for Finnish Public Libraries took 0.13902544975280762s
Interlinking | skos check for Finnish Public Libraries took 0.1256241798400879s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.29196667671203613s
Currency | Creation date check for Finnish Public Libraries took 0.32959794998168945s
Currency | Modification date check for Finnish Public Libraries took 0.41658592224121094s
Rep.Conc. | URIs length for Finnish Public Libraries took 85.88858652114868s
Interoperability | New vocabularies check for Finnish Public Libraries took 3.0994415283203125e-06s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.7640912532806396s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.57462739944458s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.157594680786133s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.308152675628662s
Consistency | Disjoint class check for Finnish Public Libraries took 0.30599045753479004s
Consistency | Check Misplaced properties for Finnish Public Libraries took 60.676565408706665s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 16.396620988845825s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5596575736999512s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 61.682167291641235s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.763193130493164s
Security | Sign check for Finnish Public Libraries took 0.31940484046936035s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.7816777229309082s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.48217272758483887s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.023671627044677734s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 2.5033950805664062e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.000993967056274414s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.4543533325195312e-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 8.106231689453125e-06s
INFO | --- Analysis for FI-Library took 697.6336545944214s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 3.54032039642334s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.2540144920349121s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.0211641788482666s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 3.1948089599609375e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.5020370483398438e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 8.821487426757812e-06s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 9.331415891647339s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.4357917308807373s
Availability | VoID file availability check for National Library Netherlands took 0.000583648681640625s
Extra | Recovery of all triples for National Library Netherlands took 1.0507090091705322s
Performance | Total latancy measurement for National Library Netherlands took 0.7911629676818848s
Amount of data | Number of triples check for National Library Netherlands took 0.16816401481628418s
Interoperability | New terms check for National Library Netherlands took 1.4913785457611084s
Versatility | Languages check for National Library Netherlands took 58.15526008605957s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.15992307662963867s
Interpretability | RDF structures check for National Library Netherlands took 0.15901541709899902s
Versatility | Serialization formats check for National Library Netherlands took 0.16575002670288086s
Availability | RDF dump link check for National Library Netherlands took 0.16121363639831543s
License | MR license check for National Library Netherlands took 0.1712477207183838s
License | HR license check for National Library Netherlands took 0.19111418724060059s
Amount of data | Number of property check for National Library Netherlands took 0.1518383026123047s
Understandability | Number of label check for National Library Netherlands took 0.16917872428894043s
Understandability | URI regex check for National Library Netherlands took 0.3230462074279785s
Understandability | Vocabs check for National Library Netherlands took 0.2163066864013672s
Verifiability | Authors check for National Library Netherlands took 0.17748522758483887s
Verifiability | Publishers check for National Library Netherlands took 0.16077160835266113s
Performance | Throughput check for National Library Netherlands took 11.057557106018066s
Amount of data | Check the number of entities for National Library Netherlands took 6.556510925292969e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.17543721199035645s
Interlinking | sameAs chians check for National Library Netherlands took 0.16432452201843262s
Interlinking | skos check for National Library Netherlands took 0.19481277465820312s
Interlinking | skos check for National Library Netherlands took 0.15831804275512695s
Timeliness | dataset update frequency check for National Library Netherlands took 0.17049288749694824s
Currency | Creation date check for National Library Netherlands took 0.3122122287750244s
Currency | Modification date check for National Library Netherlands took 0.3041665554046631s
Rep.Conc. | URIs length for National Library Netherlands took 0.660668134689331s
Interoperability | New vocabularies check for National Library Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.15253686904907227s
Accuracy | Check Functional Property for National Library Netherlands took 0.16792583465576172s
Accuracy | Check Inverse Functional Property for National Library Netherlands took 0.16113591194152832s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.44322776794433594s
Accuracy | Check White space in annotation for National Library Netherlands took 0.026761531829833984s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.02918863296508789s
Consistency | Disjoint class check for National Library Netherlands took 0.18362188339233398s
Consistency | Check Misplaced properties for National Library Netherlands took 0.3315443992614746s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.8114674091339111s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 2.268982172012329s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.5161099433898926s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.03523516654968262s
Security | Sign check for National Library Netherlands took 0.16625690460205078s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1973.5549540519714s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 1.693331003189087s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.02197408676147461s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.9325485229492188e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0018548965454101562s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 0.00014638900756835938s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 1.9073486328125e-06s
Believability | Calculation of trust value for National Library Netherlands took 7.867813110351562e-06s
INFO | --- Analysis for National-Library-Netherlands took 2085.5636291503906s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.6102633476257324s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007367134094238281s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.2454218864440918s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.02141427993774414s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.430511474609375e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 8.58306884765625e-06s
INFO | --- Analysis for Antique-Renaissance took 7.252926349639893s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.767343282699585s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007193088531494141s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.26421260833740234s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020977020263671875s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007574558258056641s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.5020370483398438e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 7.3909759521484375e-06s
INFO | --- Analysis for ARTSDATA-CA took 10.712655782699585s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.17954564094543457s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.26500582695007324s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02081155776977539s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.3113021850585938e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 8.344650268554688e-06s
INFO | --- Analysis for ArCo took 3.287181854248047s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.4175121784210205s
Availability | VoID file availability check for ConfermentSampo took 0.0002810955047607422s
Extra | Recovery of all triples for ConfermentSampo took 104.88417601585388s
Performance | Total latancy measurement for ConfermentSampo took 0.809734582901001s
Amount of data | Number of triples check for ConfermentSampo took 17.952437162399292s
Interoperability | New terms check for ConfermentSampo took 2.6864657402038574s
Versatility | Languages check for ConfermentSampo took 31.226003885269165s
Interpretability | Number of blank nodes check for ConfermentSampo took 7.4937896728515625s
Security | Check HTTPS for ConfermentSampo took 0.41936802864074707s
Interpretability | RDF structures check for ConfermentSampo took 0.1888885498046875s
Versatility | Serialization formats check for ConfermentSampo took 0.20326995849609375s
Availability | RDF dump link check for ConfermentSampo took 3.1501517295837402s
License | MR license check for ConfermentSampo took 0.20200753211975098s
License | HR license check for ConfermentSampo took 0.2349851131439209s
Amount of data | Number of property check for ConfermentSampo took 0.17026495933532715s
Understandability | Number of label check for ConfermentSampo took 5.397428750991821s
Understandability | URI regex check for ConfermentSampo took 0.37807369232177734s
Understandability | Vocabs check for ConfermentSampo took 0.17401933670043945s
Verifiability | Authors check for ConfermentSampo took 0.1790452003479004s
Verifiability | Publishers check for ConfermentSampo took 0.17878365516662598s
Performance | Throughput check for ConfermentSampo took 11.237479209899902s
Amount of data | Check the number of entities for ConfermentSampo took 0.0002951622009277344s
Verifiability | Contribs. check for ConfermentSampo took 0.17992758750915527s
Interlinking | sameAs chians check for ConfermentSampo took 0.46570420265197754s
Interlinking | skos check for ConfermentSampo took 0.185882568359375s
Interlinking | skos check for ConfermentSampo took 0.16994786262512207s
Timeliness | dataset update frequency check for ConfermentSampo took 0.17042160034179688s
Currency | Creation date check for ConfermentSampo took 0.3543527126312256s
Currency | Modification date check for ConfermentSampo took 0.35291171073913574s
Rep.Conc. | URIs length for ConfermentSampo took 31.66776394844055s
Interoperability | New vocabularies check for ConfermentSampo took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.18314719200134277s
Accuracy | Check Functional Property for ConfermentSampo took 0.1813361644744873s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.18201279640197754s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.685678482055664s
Accuracy | Check White space in annotation for ConfermentSampo took 2.9779176712036133s
Consistency | Disjoint class check for ConfermentSampo took 0.17937874794006348s
Consistency | Check Misplaced properties for ConfermentSampo took 6.489834785461426s
Consistency | Check Ontology hijacking for ConfermentSampo took 15.833343029022217s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.6750423908233643s
Conciseness | Check Extensional conciseness for ConfermentSampo took 0.0001823902130126953s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.2106790542602539s
Security | Sign check for ConfermentSampo took 0.1638655662536621s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.41693735122680664s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.021141529083251953s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for ConfermentSampo took 8.344650268554688e-06s
INFO | --- Analysis for ConfermentSampo took 397.33076643943787s
Availability | SPARQL endpoint availability check for Museum Finland took 0.27638912200927734s
Availability | VoID file availability check for Museum Finland took 0.0002791881561279297s
Extra | Recovery of all triples for Museum Finland took 7.876733064651489s
Performance | Total latancy measurement for Museum Finland took 0.8428118228912354s
Amount of data | Number of triples check for Museum Finland took 0.3206923007965088s
Interoperability | New terms check for Museum Finland took 2.4474592208862305s
Versatility | Languages check for Museum Finland took 0.6776096820831299s
Interpretability | Number of blank nodes check for Museum Finland took 0.2969329357147217s
Security | Check HTTPS for Museum Finland took 0.24712419509887695s
Interpretability | RDF structures check for Museum Finland took 0.40177226066589355s
Versatility | Serialization formats check for Museum Finland took 0.2730581760406494s
Availability | RDF dump link check for Museum Finland took 0.19144201278686523s
License | MR license check for Museum Finland took 0.19898343086242676s
License | HR license check for Museum Finland took 0.560633659362793s
Amount of data | Number of property check for Museum Finland took 0.15518879890441895s
Understandability | Number of label check for Museum Finland took 0.4028451442718506s
Understandability | URI regex check for Museum Finland took 0.3330514430999756s
Understandability | Vocabs check for Museum Finland took 0.17416596412658691s
Verifiability | Authors check for Museum Finland took 0.16062021255493164s
Verifiability | Publishers check for Museum Finland took 0.16387414932250977s
Performance | Throughput check for Museum Finland took 10.905040264129639s
Amount of data | Check the number of entities for Museum Finland took 7.677078247070312e-05s
Verifiability | Contribs. check for Museum Finland took 0.16315150260925293s
Interlinking | sameAs chians check for Museum Finland took 0.2222297191619873s
Interlinking | skos check for Museum Finland took 0.17151308059692383s
Interlinking | skos check for Museum Finland took 0.16979122161865234s
Timeliness | dataset update frequency check for Museum Finland took 0.16359305381774902s
Currency | Creation date check for Museum Finland took 0.3377566337585449s
Currency | Modification date check for Museum Finland took 0.36237406730651855s
Rep.Conc. | URIs length for Museum Finland took 3.5938189029693604s
Interoperability | New vocabularies check for Museum Finland took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.15700435638427734s
Accuracy | Check Functional Property for Museum Finland took 0.17429471015930176s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.1696169376373291s
Accuracy | Check Empty annotation labels for Museum Finland took 0.9492528438568115s
Accuracy | Check White space in annotation for Museum Finland took 0.06048870086669922s
Accuracy | Check Datatype consistency for Museum Finland took 0.9672355651855469s
Consistency | Disjoint class check for Museum Finland took 0.16434311866760254s
Consistency | Check Misplaced properties for Museum Finland took 0.634148359298706s
Consistency | Check Ontology hijacking for Museum Finland took 2.1045939922332764s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.3474762439727783s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.5362210273742676s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6502368450164795s
Conciseness | Check Intensional conciseness for Museum Finland took 0.2435901165008545s
Security | Sign check for Museum Finland took 0.15614628791809082s
Availability | Check URIs Dereferenciability for Museum Finland took 3134.8951284885406s
Completeness | Calculation of interlinking completeness for Museum Finland took 1.5001027584075928s
Reputation | Calculation of the PageRank for Museum Finland took 0.022714614868164062s
Interlinking | Calculation of Degree of Connection for Museum Finland took 2.765655517578125e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0008232593536376953s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 0.00016617774963378906s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 2.1457672119140625e-06s
Believability | Calculation of trust value for Museum Finland took 8.58306884765625e-06s
INFO | --- Analysis for FI-Museum took 3196.5793442726135s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.18914508819580078s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0006642341613769531s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 17.246577739715576s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8874242305755615s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 33.29428219795227s
Interoperability | New terms check for Mapping Manuscript Migrations took 5.0079545974731445s
Versatility | Languages check for Mapping Manuscript Migrations took 76.83372855186462s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 30.68278694152832s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.40886831283569336s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.16436123847961426s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.1581106185913086s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.17323541641235352s
License | MR license check for Mapping Manuscript Migrations took 0.1786503791809082s
License | HR license check for Mapping Manuscript Migrations took 1.8147034645080566s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.1776435375213623s
Understandability | Number of label check for Mapping Manuscript Migrations took 9.278339385986328s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.3349723815917969s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.16571664810180664s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.16620302200317383s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.17770051956176758s
Performance | Throughput check for Mapping Manuscript Migrations took 10.757739543914795s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.1087489128112793s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.17299461364746094s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5069434642791748s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1584630012512207s
Interlinking | skos check for Mapping Manuscript Migrations took 0.1694626808166504s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.16542720794677734s
Currency | Creation date check for Mapping Manuscript Migrations took 0.32351112365722656s
Currency | Modification date check for Mapping Manuscript Migrations took 0.17396855354309082s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 50.262187242507935s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 1.0967254638671875e-05s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.16540074348449707s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.17169523239135742s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.17027664184570312s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.610837459564209s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.428492546081543s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.676841974258423s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.172926664352417s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 23.678213357925415s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 17.181572437286377s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.6758325099945068s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6596829891204834s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.8338139057159424s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.17280960083007812s
Security | Sign check for Mapping Manuscript Migrations took 0.16364693641662598s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 21.82421040534973s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.7577972412109375s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.022912025451660156s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 2.002716064453125e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0008819103240966797s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.3828277587890625e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 2.1457672119140625e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 9.059906005859375e-06s
INFO | --- Analysis for MMM took 544.4218518733978s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.28804469108581543s
Availability | VoID file availability check for Semantic Kalevala took 0.0005152225494384766s
Extra | Recovery of all triples for Semantic Kalevala took 7.427204132080078s
Performance | Total latancy measurement for Semantic Kalevala took 0.8244743347167969s
Amount of data | Number of triples check for Semantic Kalevala took 0.37348175048828125s
Interoperability | New terms check for Semantic Kalevala took 3.904531717300415s
Versatility | Languages check for Semantic Kalevala took 0.9437954425811768s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.3479044437408447s
Security | Check HTTPS for Semantic Kalevala took 0.24079608917236328s
Interpretability | RDF structures check for Semantic Kalevala took 0.5065333843231201s
Versatility | Serialization formats check for Semantic Kalevala took 0.17119216918945312s
Availability | RDF dump link check for Semantic Kalevala took 0.16106057167053223s
License | MR license check for Semantic Kalevala took 0.18999361991882324s
License | HR license check for Semantic Kalevala took 1.1169192790985107s
Amount of data | Number of property check for Semantic Kalevala took 0.1690664291381836s
Understandability | Number of label check for Semantic Kalevala took 1.4012041091918945s
Understandability | URI regex check for Semantic Kalevala took 0.340496301651001s
Understandability | Vocabs check for Semantic Kalevala took 0.17803525924682617s
Verifiability | Authors check for Semantic Kalevala took 0.16643023490905762s
Verifiability | Publishers check for Semantic Kalevala took 0.17713427543640137s
Performance | Throughput check for Semantic Kalevala took 11.012950420379639s
Amount of data | Check the number of entities for Semantic Kalevala took 7.200241088867188e-05s
Verifiability | Contribs. check for Semantic Kalevala took 0.19487953186035156s
Interlinking | sameAs chians check for Semantic Kalevala took 0.15760159492492676s
Interlinking | skos check for Semantic Kalevala took 0.29313182830810547s
Interlinking | skos check for Semantic Kalevala took 0.16222810745239258s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.19145655632019043s
Currency | Creation date check for Semantic Kalevala took 0.34914207458496094s
Currency | Modification date check for Semantic Kalevala took 0.324840784072876s
Rep.Conc. | URIs length for Semantic Kalevala took 4.929008722305298s
Interoperability | New vocabularies check for Semantic Kalevala took 1.1920928955078125e-05s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.19727444648742676s
Accuracy | Check Functional Property for Semantic Kalevala took 0.17001748085021973s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.16404008865356445s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.863837718963623s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2982778549194336s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.4531500339508057s
Consistency | Disjoint class check for Semantic Kalevala took 0.16936349868774414s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.775925874710083s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.460481643676758s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.5554001331329346s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.7834222316741943s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.9183914661407471s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.23284196853637695s
Security | Sign check for Semantic Kalevala took 0.16375517845153809s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3051.070320367813s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 1.4840238094329834s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.4543533325195312e-05s
Interoperability | Check the re-using of existing vocabs for Semantic Kalevala took 2.384185791015625e-06s
Believability | Calculation of trust value for Semantic Kalevala took 8.58306884765625e-06s
INFO | --- Analysis for Semantic-Kalevala took 3118.785322666168s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9690594673156738s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0007388591766357422s
Extra | Recovery of all triples for Smithsonian American Art Museum took 288.86989974975586s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.0028443336486816s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5834391117095947s
Interoperability | New terms check for Smithsonian American Art Museum took 2.928614616394043s
Versatility | Languages check for Smithsonian American Art Museum took 24.98624014854431s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.590996503829956s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3670670986175537s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.6372818946838379s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6096231937408447s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.60494065284729s
License | MR license check for Smithsonian American Art Museum took 0.5863070487976074s
License | HR license check for Smithsonian American Art Museum took 17.032365798950195s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5755717754364014s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5805819034576416s
Understandability | URI regex check for Smithsonian American Art Museum took 1.164980173110962s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.6010634899139404s
Verifiability | Authors check for Smithsonian American Art Museum took 0.588162899017334s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5839734077453613s
Performance | Throughput check for Smithsonian American Art Museum took 11.743247032165527s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.081031799316406e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6046700477600098s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.585162878036499s
Interlinking | skos check for Smithsonian American Art Museum took 0.5841104984283447s
Interlinking | skos check for Smithsonian American Art Museum took 0.5946061611175537s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6018338203430176s
Currency | Creation date check for Smithsonian American Art Museum took 1.2208445072174072s
Currency | Modification date check for Smithsonian American Art Museum took 1.2157855033874512s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 105.77520108222961s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.2636184692382812e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5969808101654053s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 22.667814254760742s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.4968538284301758s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.340308427810669s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5798022747039795s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.721582651138306s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 101.21964406967163s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.7438359260559082s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.858992576599121s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9125585556030273s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6167445182800293s
Security | Sign check for Smithsonian American Art Museum took 0.6057534217834473s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.2805562019348145s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 1.4392063617706299s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020881175994873047s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006732940673828125s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.4066696166992188e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 1.6689300537109375e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 8.344650268554688e-06s
INFO | --- Analysis for Smithsonian took 715.7203884124756s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.17031240463256836s
Availability | VoID file availability check for Zeri Photo Archive took 0.0007498264312744141s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.2628791332244873s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.02108025550842285s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.8835067749023438e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.33514404296875e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 9.059906005859375e-06s
INFO | --- Analysis for Zeri-Photo-Archive took 8.079424381256104s
Availability | SPARQL endpoint availability check for Archives Hub took 21.375020265579224s
Availability | VoID file availability check for Archives Hub took 0.0002980232238769531s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.24875879287719727s
Reputation | Calculation of the PageRank for Archives Hub took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.430511474609375e-05s
Believability | Calculation of trust value for Archives Hub took 8.106231689453125e-06s
INFO | --- Analysis for Archives-Hub took 55.219435930252075s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.47171950340271s
Availability | VoID file availability check for Yale centre of British Art took 0.00026535987854003906s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.24896478652954102s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.0211184024810791s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.2159347534179688e-05s
Believability | Calculation of trust value for Yale centre of British Art took 8.344650268554688e-06s
INFO | --- Analysis for Yale took 4.357403993606567s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.4398362636566s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.25341057777404785s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.02223944664001465s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0009829998016357422s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.3828277587890625e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 8.58306884765625e-06s
INFO | --- Analysis for ADL took 537.3803555965424s
Availability | SPARQL endpoint availability check for MusicKG took 0.7011971473693848s
Availability | VoID file availability check for MusicKG took 0.0005953311920166016s
Completeness | Calculation of interlinking completeness for MusicKG took 0.709735631942749s
Reputation | Calculation of the PageRank for MusicKG took 0.020824193954467773s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.1682510375976562e-05s
Believability | Calculation of trust value for MusicKG took 8.106231689453125e-06s
INFO | --- Analysis for MusicKG took 6.629565715789795s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 0.7887556552886963s
Availability | VoID file availability check for CIDOC-CRM took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.2736072540283203s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.2874603271484375e-05s
Believability | Calculation of trust value for CIDOC-CRM took 6.9141387939453125e-06s
INFO | --- Analysis for CIDOC-CRM took 3.787071704864502s
Availability | SPARQL endpoint availability check for Mondis took 0.35539817810058594s
Availability | VoID file availability check for Mondis took 0.00028896331787109375s
Completeness | Calculation of interlinking completeness for Mondis took 0.2720670700073242s
Reputation | Calculation of the PageRank for Mondis took 0.020645856857299805s
Interlinking | Calculation of Degree of Connection for Mondis took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.1920928955078125e-05s
Believability | Calculation of trust value for Mondis took 7.3909759521484375e-06s
INFO | --- Analysis for Mondis took 3.205364227294922s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.5215232372283936s
Availability | VoID file availability check for DigitalNZ took 0.00036263465881347656s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.27445363998413086s
Reputation | Calculation of the PageRank for DigitalNZ took 0.020465373992919922s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.52587890625e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.2874603271484375e-05s
Believability | Calculation of trust value for DigitalNZ took 7.867813110351562e-06s
INFO | --- Analysis for DigitalNZ took 7.641066551208496s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.1615889072418213s
Availability | VoID file availability check for Fondazione Zeri took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.2571141719818115s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.02096867561340332s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.2636184692382812e-05s
Believability | Calculation of trust value for Fondazione Zeri took 8.344650268554688e-06s
INFO | --- Analysis for Fondazione-Zeri took 3.0197057723999023s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.24120879173278809s
Availability | VoID file availability check for Digital Public Library of America took 0.0006825923919677734s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.2605576515197754s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.021061420440673828s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.4066696166992188e-05s
Believability | Calculation of trust value for Digital Public Library of America took 8.106231689453125e-06s
INFO | --- Analysis for Library-of-America took 3.747180700302124s
Availability | SPARQL endpoint availability check for Auckland Museum took 0.8847293853759766s
Availability | VoID file availability check for Auckland Museum took 0.0006020069122314453s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.26651740074157715s
Reputation | Calculation of the PageRank for Auckland Museum took 0.020821809768676758s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.71661376953125e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0007576942443847656s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.2874603271484375e-05s
Believability | Calculation of trust value for Auckland Museum took 7.867813110351562e-06s
INFO | --- Analysis for Auckland-Museum took 5.49409556388855s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.9020187854766846s
Availability | VoID file availability check for National Library of Spain took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.2866384983062744s
Reputation | Calculation of the PageRank for National Library of Spain took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.1920928955078125e-05s
Believability | Calculation of trust value for National Library of Spain took 7.867813110351562e-06s
INFO | --- Analysis for BNE took 4.7337963581085205s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.4504964351654053s
Availability | VoID file availability check for National Library of Korea took 0.0002727508544921875s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.25377416610717773s
Reputation | Calculation of the PageRank for National Library of Korea took 0.02056121826171875s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.2636184692382812e-05s
Believability | Calculation of trust value for National Library of Korea took 7.3909759521484375e-06s
INFO | --- Analysis for Korea-Library took 5.234853506088257s
Availability | SPARQL endpoint availability check for The State Russian Museum took 2.410658836364746s
Availability | VoID file availability check for The State Russian Museum took 0.00028777122497558594s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.24546599388122559s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020687580108642578s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for The State Russian Museum took 1.3828277587890625e-05s
Believability | Calculation of trust value for The State Russian Museum took 1.1682510375976562e-05s
INFO | --- Analysis for Russian-Museum took 5.223489046096802s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7010438442230225s
Availability | VoID file availability check for National Library of Scotland took 0.0006413459777832031s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.26958656311035156s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.0206453800201416s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.0007412433624267578s
Interlinking | Calculation of Clustering coefficient for National Library of Scotland took 1.3828277587890625e-05s
Believability | Calculation of trust value for National Library of Scotland took 7.3909759521484375e-06s
INFO | --- Analysis for National-Library-of-Scotland took 6.960463762283325s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.28881239891052246s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.000537872314453125s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.2651209831237793s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.021079540252685547s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.7404556274414062e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0007717609405517578s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.4066696166992188e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.1205673217773438e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 3.3350987434387207s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.20459246635437012s
Availability | VoID file availability check for OntoComedySources took 0.0006296634674072266s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.26547884941101074s
Reputation | Calculation of the PageRank for OntoComedySources took 0.02087235450744629s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.3113021850585938e-05s
Believability | Calculation of trust value for OntoComedySources took 1.2159347534179688e-05s
INFO | --- Analysis for OntoComedySources took 3.862508773803711s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.20281648635864258s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0006761550903320312s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.2591257095336914s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.020617961883544922s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.3113021850585938e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 7.62939453125e-06s
INFO | --- Analysis for OntoCeramic-2.0 took 4.175219297409058s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.16659212112426758s
Availability | VoID file availability check for SaintGall Ontology took 0.0002810955047607422s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.26708531379699707s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.020756244659423828s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.2636184692382812e-05s
Believability | Calculation of trust value for SaintGall Ontology took 7.867813110351562e-06s
INFO | --- Analysis for SaintGall-Ontology took 3.0215327739715576s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.9147121906280518s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0005536079406738281s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.255279541015625s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.4781951904296875e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 7.62939453125e-06s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.932582139968872s
Availability | SPARQL endpoint availability check for ICON took 0.4712052345275879s
Availability | VoID file availability check for ICON took 0.0007042884826660156s
Completeness | Calculation of interlinking completeness for ICON took 0.28734850883483887s
Reputation | Calculation of the PageRank for ICON took 0.020701169967651367s
Interlinking | Calculation of Degree of Connection for ICON took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for ICON took 1.3113021850585938e-05s
Believability | Calculation of trust value for ICON took 1.1444091796875e-05s
INFO | --- Analysis for ICON took 4.339978933334351s
Availability | SPARQL endpoint availability check for Polifonia took 0.2782728672027588s
Availability | VoID file availability check for Polifonia took 0.0006299018859863281s
Completeness | Calculation of interlinking completeness for Polifonia took 0.2582862377166748s
Reputation | Calculation of the PageRank for Polifonia took 0.020823001861572266s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0007693767547607422s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.3589859008789062e-05s
Believability | Calculation of trust value for Polifonia took 7.867813110351562e-06s
INFO | --- Analysis for Polifonia took 4.290052652359009s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.2574765682220459s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0007147789001464844s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.26457977294921875s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020717859268188477s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.239776611328125e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 8.106231689453125e-06s
INFO | --- Analysis for Atlas-of-Paths took 3.7586045265197754s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.20621252059936523s
Availability | VoID file availability check for Music Note Ontology took 0.0006844997406005859s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.2659037113189697s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020793437957763672s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.5974044799804688e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.33514404296875e-05s
Believability | Calculation of trust value for Music Note Ontology took 6.67572021484375e-06s
INFO | --- Analysis for Music-Note-Ontology took 7.8097779750823975s
Availability | SPARQL endpoint availability check for HaMSE took 0.1943516731262207s
Availability | VoID file availability check for HaMSE took 0.0006630420684814453s
Completeness | Calculation of interlinking completeness for HaMSE took 0.2558929920196533s
Reputation | Calculation of the PageRank for HaMSE took 0.020963668823242188s
Interlinking | Calculation of Degree of Connection for HaMSE took 2.1696090698242188e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.0007550716400146484s
Interlinking | Calculation of Clustering coefficient for HaMSE took 2.0265579223632812e-05s
Believability | Calculation of trust value for HaMSE took 1.1205673217773438e-05s
INFO | --- Analysis for HaMSE took 4.7566752433776855s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.06810760498046875s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005567073822021484s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.2728087902069092s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.021009445190429688s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for FOOD: FOod in Open Data took 1.2636184692382812e-05s
Believability | Calculation of trust value for FOOD: FOod in Open Data took 7.62939453125e-06s
INFO | --- Analysis for FOod took 3.17083740234375s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 1.5589866638183594s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.2567460536956787s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0007073879241943359s
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 8.106231689453125e-06s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 5.67613959312439s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.32444429397583s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.00042438507080078125s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.23876523971557617s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.02066946029663086s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007457733154296875s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.33514404296875e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 8.58306884765625e-06s
INFO | --- Analysis for ARIADNE took 5.237720489501953s
Availability | SPARQL endpoint availability check for MappingChange took 0.4742403030395508s
Availability | VoID file availability check for MappingChange took 0.0002880096435546875s
Extra | Recovery of all triples for MappingChange took 76.90617370605469s
Performance | Total latancy measurement for MappingChange took 1.484954833984375s
Amount of data | Number of triples check for MappingChange took 32.36419415473938s
Interoperability | New terms check for MappingChange took 7.910065174102783s
Versatility | Languages check for MappingChange took 39.7253680229187s
Interpretability | Number of blank nodes check for MappingChange took 16.110352277755737s
Interpretability | RDF structures check for MappingChange took 0.3120920658111572s
Versatility | Serialization formats check for MappingChange took 0.29166412353515625s
Availability | RDF dump link check for MappingChange took 0.29729199409484863s
License | MR license check for MappingChange took 0.30005860328674316s
License | HR license check for MappingChange took 5.265650987625122s
Amount of data | Number of property check for MappingChange took 0.2983510494232178s
Understandability | Number of label check for MappingChange took 2.39961314201355s
Understandability | URI regex check for MappingChange took 0.5787110328674316s
Understandability | Vocabs check for MappingChange took 0.299713134765625s
Verifiability | Authors check for MappingChange took 0.2909700870513916s
Verifiability | Publishers check for MappingChange took 0.29920434951782227s
Performance | Throughput check for MappingChange took 11.687131643295288s
Amount of data | Check the number of entities for MappingChange took 7.081031799316406e-05s
Verifiability | Contribs. check for MappingChange took 0.2902553081512451s
Interlinking | sameAs chians check for MappingChange took 0.30394721031188965s
Interlinking | skos check for MappingChange took 0.3032960891723633s
Interlinking | skos check for MappingChange took 0.28960752487182617s
Timeliness | dataset update frequency check for MappingChange took 0.2887451648712158s
Currency | Creation date check for MappingChange took 0.593207597732544s
Currency | Modification date check for MappingChange took 0.5966765880584717s
Rep.Conc. | URIs length for MappingChange took 64.3745105266571s
Interoperability | New vocabularies check for MappingChange took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for MappingChange took 0.30379176139831543s
Accuracy | Check Functional Property for MappingChange took 0.28095436096191406s
Accuracy | Check Inverse Functional Property for MappingChange took 0.29494667053222656s
Accuracy | Check Empty annotation labels for MappingChange took 4.793049335479736s
Accuracy | Check White space in annotation for MappingChange took 0.45682239532470703s
Accuracy | Check Datatype consistency for MappingChange took 4.903622627258301s
Consistency | Disjoint class check for MappingChange took 0.2942936420440674s
Consistency | Check Misplaced properties for MappingChange took 9.998896360397339s
Consistency | Check Ontology hijacking for MappingChange took 29.61911368370056s
Consistency | Check Invalid usage of undefined classes for MappingChange took 1.5155401229858398s
Consistency | Check Invalid usage of undefined properties for MappingChange took 12.610086441040039s
Conciseness | Check Extensional conciseness for MappingChange took 3.160054922103882s
Conciseness | Check Intensional conciseness for MappingChange took 0.30318379402160645s
Security | Sign check for MappingChange took 0.30556321144104004s
Availability | Check URIs Dereferenciability for MappingChange took 22.939275979995728s
Completeness | Calculation of interlinking completeness for MappingChange took 1.4132835865020752s
Reputation | Calculation of the PageRank for MappingChange took 0.02203059196472168s
Interlinking | Calculation of Degree of Connection for MappingChange took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for MappingChange took 0.0007512569427490234s
Interlinking | Calculation of Clustering coefficient for MappingChange took 1.4066696166992188e-05s
Interoperability | Check the re-using of existing vocabs for MappingChange took 6.67572021484375e-06s
Believability | Calculation of trust value for MappingChange took 7.152557373046875e-06s
INFO | --- Analysis for mappingch took 1828.3453800678253s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.3572964668273926s
Availability | VoID file availability check for Odeuropa Ontology took 0.0002853870391845703s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.25675344467163086s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.021100997924804688s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.430511474609375e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Odeuropa took 4.504305124282837s

--- Total time for analysis:73421.5023124218s ---
--- Total time for analysis:20.3948617534505 hours ---