Availability | SPARQL endpoint availability check for Korespondencja Emila Szramka z Janem Kuderą took 4.220008850097656e-05s
Availability | VoID file availability check for Korespondencja Emila Szramka z Janem Kuderą took 0.0005042552947998047s
Completeness | Calculation of interlinking completeness for Korespondencja Emila Szramka z Janem Kuderą took 0.1922588348388672s
Reputation | Calculation of the PageRank for Korespondencja Emila Szramka z Janem Kuderą took 0.46784377098083496s
Interlinking | Calculation of Degree of Connection for Korespondencja Emila Szramka z Janem Kuderą took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Korespondencja Emila Szramka z Janem Kuderą took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Korespondencja Emila Szramka z Janem Kuderą took 0.00035500526428222656s
Believability | Calculation of trust value for Korespondencja Emila Szramka z Janem Kuderą took 1.811981201171875e-05s
INFO | --- Analysis for 0080-3626 took 2.7361299991607666s
Availability | SPARQL endpoint availability check for 土地利用图 took 9.131431579589844e-05s
Availability | VoID file availability check for 土地利用图 took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for 土地利用图 took 0.1750354766845703s
Reputation | Calculation of the PageRank for 土地利用图 took 0.021416187286376953s
Interlinking | Calculation of Degree of Connection for 土地利用图 took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for 土地利用图 took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for 土地利用图 took 5.245208740234375e-05s
Believability | Calculation of trust value for 土地利用图 took 9.059906005859375e-06s
INFO | --- Analysis for 10.12041geodata.290864223.ver1.db_ took 1.9980700016021729s
Availability | SPARQL endpoint availability check for 113322 took 4.887580871582031e-05s
Availability | VoID file availability check for 113322 took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for 113322 took 0.17290544509887695s
Reputation | Calculation of the PageRank for 113322 took 0.02062082290649414s
Interlinking | Calculation of Degree of Connection for 113322 took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for 113322 took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for 113322 took 4.5299530029296875e-05s
Believability | Calculation of trust value for 113322 took 1.5974044799804688e-05s
INFO | --- Analysis for 11 took 2.010016441345215s
Availability | SPARQL endpoint availability check for Korepetycje Buki took 0.00015234947204589844s
Availability | VoID file availability check for Korepetycje Buki took 0.0003330707550048828s
Completeness | Calculation of interlinking completeness for Korepetycje Buki took 0.18233418464660645s
Reputation | Calculation of the PageRank for Korepetycje Buki took 0.021776914596557617s
Interlinking | Calculation of Degree of Connection for Korepetycje Buki took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Korepetycje Buki took 0.0007381439208984375s
Interlinking | Calculation of Clustering coefficient for Korepetycje Buki took 4.3392181396484375e-05s
Believability | Calculation of trust value for Korepetycje Buki took 1.7404556274414062e-05s
INFO | --- Analysis for 12323 took 2.014864444732666s
Availability | SPARQL endpoint availability check for 2000 U.S. Census in RDF (rdfabout.com) took 5.698204040527344e-05s
Availability | VoID file availability check for 2000 U.S. Census in RDF (rdfabout.com) took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for 2000 U.S. Census in RDF (rdfabout.com) took 0.18217825889587402s
Reputation | Calculation of the PageRank for 2000 U.S. Census in RDF (rdfabout.com) took 0.02069568634033203s
Interlinking | Calculation of Degree of Connection for 2000 U.S. Census in RDF (rdfabout.com) took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for 2000 U.S. Census in RDF (rdfabout.com) took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for 2000 U.S. Census in RDF (rdfabout.com) took 0.00010418891906738281s
Believability | Calculation of trust value for 2000 U.S. Census in RDF (rdfabout.com) took 1.6450881958007812e-05s
INFO | --- Analysis for 2000-us-census-rdf took 1.9814908504486084s
Availability | SPARQL endpoint availability check for 2001 Spanish Census to RDF took 4.696846008300781e-05s
Availability | VoID file availability check for 2001 Spanish Census to RDF took 0.0005295276641845703s
Completeness | Calculation of interlinking completeness for 2001 Spanish Census to RDF took 0.1842663288116455s
Reputation | Calculation of the PageRank for 2001 Spanish Census to RDF took 0.020694732666015625s
Interlinking | Calculation of Degree of Connection for 2001 Spanish Census to RDF took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for 2001 Spanish Census to RDF took 0.0008115768432617188s
Interlinking | Calculation of Clustering coefficient for 2001 Spanish Census to RDF took 5.6743621826171875e-05s
Believability | Calculation of trust value for 2001 Spanish Census to RDF took 1.6689300537109375e-05s
INFO | --- Analysis for 2001-spanish-census-to-rdf took 2.0354206562042236s
Availability | SPARQL endpoint availability check for Open Data Web took 0.00010824203491210938s
Availability | VoID file availability check for Open Data Web took 0.00037932395935058594s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.19043183326721191s
Reputation | Calculation of the PageRank for Open Data Web took 0.02173781394958496s
Interlinking | Calculation of Degree of Connection for Open Data Web took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Open Data Web took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 4.863739013671875e-05s
Believability | Calculation of trust value for Open Data Web took 1.5020370483398438e-05s
INFO | --- Analysis for _data.odw.tw took 2.050009250640869s
Availability | SPARQL endpoint availability check for 土地利用 took 4.172325134277344e-05s
Availability | VoID file availability check for 土地利用 took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for 土地利用 took 0.1790471076965332s
Reputation | Calculation of the PageRank for 土地利用 took 0.020402908325195312s
Interlinking | Calculation of Degree of Connection for 土地利用 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 土地利用 took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for 土地利用 took 3.314018249511719e-05s
Believability | Calculation of trust value for 土地利用 took 5.9604644775390625e-06s
INFO | --- Analysis for _data1.odw.tw took 2.014183759689331s
Availability | SPARQL endpoint availability check for 土地利用模型 took 8.821487426757812e-05s
Availability | VoID file availability check for 土地利用模型 took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for 土地利用模型 took 0.1790165901184082s
Reputation | Calculation of the PageRank for 土地利用模型 took 0.020163774490356445s
Interlinking | Calculation of Degree of Connection for 土地利用模型 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for 土地利用模型 took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for 土地利用模型 took 3.457069396972656e-05s
Believability | Calculation of trust value for 土地利用模型 took 1.1205673217773438e-05s
INFO | --- Analysis for _data2.odw.tw took 2.044421672821045s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.559226989746094e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.18264484405517578s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020760297775268555s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0967254638671875e-05s
INFO | --- Analysis for _https:data.bioontology.orgontologiesBOFdownloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb&download_format=rdf took 2.0287396907806396s
Availability | SPARQL endpoint availability check for A collection of Papers for LREC2014 and related Workshops took 8.535385131835938e-05s
Availability | VoID file availability check for A collection of Papers for LREC2014 and related Workshops took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for A collection of Papers for LREC2014 and related Workshops took 0.18410086631774902s
Reputation | Calculation of the PageRank for A collection of Papers for LREC2014 and related Workshops took 0.01999950408935547s
Interlinking | Calculation of Degree of Connection for A collection of Papers for LREC2014 and related Workshops took 7.62939453125e-06s
Interlinking | Calculation of Centrality for A collection of Papers for LREC2014 and related Workshops took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for A collection of Papers for LREC2014 and related Workshops took 2.8371810913085938e-05s
Believability | Calculation of trust value for A collection of Papers for LREC2014 and related Workshops took 1.0013580322265625e-05s
INFO | --- Analysis for a-collection-of-papers-for-lrec2014-and-related-workshops took 2.0141761302948s
Availability | SPARQL endpoint availability check for ITS TEST DATASET took 8.440017700195312e-05s
Availability | VoID file availability check for ITS TEST DATASET took 0.00043201446533203125s
Completeness | Calculation of interlinking completeness for ITS TEST DATASET took 0.18352556228637695s
Reputation | Calculation of the PageRank for ITS TEST DATASET took 0.020232200622558594s
Interlinking | Calculation of Degree of Connection for ITS TEST DATASET took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ITS TEST DATASET took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for ITS TEST DATASET took 3.218650817871094e-05s
Believability | Calculation of trust value for ITS TEST DATASET took 1.0967254638671875e-05s
INFO | --- Analysis for A1 took 1.9963479042053223s
Availability | SPARQL endpoint availability check for SummerOlympics took 9.703636169433594e-05s
Availability | VoID file availability check for SummerOlympics took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for SummerOlympics took 0.1876969337463379s
Reputation | Calculation of the PageRank for SummerOlympics took 0.021219730377197266s
Interlinking | Calculation of Degree of Connection for SummerOlympics took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for SummerOlympics took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for SummerOlympics took 6.29425048828125e-05s
Believability | Calculation of trust value for SummerOlympics took 1.1682510375976562e-05s
INFO | --- Analysis for abc took 2.0433785915374756s
Availability | SPARQL endpoint availability check for Test_m took 8.940696716308594e-05s
Availability | VoID file availability check for Test_m took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Test_m took 0.1933116912841797s
Reputation | Calculation of the PageRank for Test_m took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for Test_m took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test_m took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Test_m took 2.9802322387695312e-05s
Believability | Calculation of trust value for Test_m took 1.1920928955078125e-05s
INFO | --- Analysis for ABC took 2.14750075340271s
Availability | SPARQL endpoint availability check for my intro took 8.368492126464844e-05s
Availability | VoID file availability check for my intro took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for my intro took 0.18508219718933105s
Reputation | Calculation of the PageRank for my intro took 0.020076274871826172s
Interlinking | Calculation of Degree of Connection for my intro took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for my intro took 0.0006816387176513672s
Interlinking | Calculation of Clustering coefficient for my intro took 3.075599670410156e-05s
Believability | Calculation of trust value for my intro took 1.1444091796875e-05s
INFO | --- Analysis for abhay_intro took 2.0029962062835693s
Availability | SPARQL endpoint availability check for Australian Bureau of Statistics (ABS) Linked Data took 8.368492126464844e-05s
Availability | VoID file availability check for Australian Bureau of Statistics (ABS) Linked Data took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Australian Bureau of Statistics (ABS) Linked Data took 0.1938931941986084s
Reputation | Calculation of the PageRank for Australian Bureau of Statistics (ABS) Linked Data took 0.02018880844116211s
Interlinking | Calculation of Degree of Connection for Australian Bureau of Statistics (ABS) Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Australian Bureau of Statistics (ABS) Linked Data took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Australian Bureau of Statistics (ABS) Linked Data took 9.965896606445312e-05s
Believability | Calculation of trust value for Australian Bureau of Statistics (ABS) Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for abs-linked-data took 1.9937467575073242s
Availability | SPARQL endpoint availability check for Academic Offer of UNL took 8.177757263183594e-05s
Availability | VoID file availability check for Academic Offer of UNL took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Academic Offer of UNL took 0.18635869026184082s
Reputation | Calculation of the PageRank for Academic Offer of UNL took 0.021717309951782227s
Interlinking | Calculation of Degree of Connection for Academic Offer of UNL took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Academic Offer of UNL took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Academic Offer of UNL took 2.9087066650390625e-05s
Believability | Calculation of trust value for Academic Offer of UNL took 1.049041748046875e-05s
INFO | --- Analysis for academic-offer-of-unl took 2.034458637237549s
Availability | SPARQL endpoint availability check for AcadOnto took 8.487701416015625e-05s
Availability | VoID file availability check for AcadOnto took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for AcadOnto took 0.17620062828063965s
Reputation | Calculation of the PageRank for AcadOnto took 0.020134925842285156s
Interlinking | Calculation of Degree of Connection for AcadOnto took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for AcadOnto took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for AcadOnto took 2.8848648071289062e-05s
Believability | Calculation of trust value for AcadOnto took 1.049041748046875e-05s
INFO | --- Analysis for acadonto took 2.0087156295776367s
Availability | SPARQL endpoint availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.933906555175781e-05s
Availability | VoID file availability check for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.1970226764678955s
Reputation | Calculation of the PageRank for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 0.0218050479888916s
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.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for Australian Climate Observations Reference Network - Surface Air Temperature Dataset took 1.0251998901367188e-05s
INFO | --- Analysis for acorn-sat took 2.075929880142212s
Availability | SPARQL endpoint availability check for Addgene took 3.933906555175781e-05s
Availability | VoID file availability check for Addgene took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for Addgene took 0.1944408416748047s
Reputation | Calculation of the PageRank for Addgene took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Addgene took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Addgene took 0.0006775856018066406s
Interlinking | Calculation of Clustering coefficient for Addgene took 3.266334533691406e-05s
Believability | Calculation of trust value for Addgene took 5.9604644775390625e-06s
INFO | --- Analysis for addgene took 2.211207628250122s
Availability | SPARQL endpoint availability check for AEGP, Spanish Textile and Clothing Association took 4.076957702636719e-05s
Availability | VoID file availability check for AEGP, Spanish Textile and Clothing Association took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for AEGP, Spanish Textile and Clothing Association took 0.17482852935791016s
Reputation | Calculation of the PageRank for AEGP, Spanish Textile and Clothing Association took 0.019925832748413086s
Interlinking | Calculation of Degree of Connection for AEGP, Spanish Textile and Clothing Association took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for AEGP, Spanish Textile and Clothing Association took 0.0006768703460693359s
Interlinking | Calculation of Clustering coefficient for AEGP, Spanish Textile and Clothing Association took 8.797645568847656e-05s
Believability | Calculation of trust value for AEGP, Spanish Textile and Clothing Association took 1.0013580322265625e-05s
INFO | --- Analysis for aegp-spanish-textile-and-clothing-association took 2.0218141078948975s
Availability | SPARQL endpoint availability check for AEMET metereological dataset took 4.363059997558594e-05s
Availability | VoID file availability check for AEMET metereological dataset took 0.0005447864532470703s
Completeness | Calculation of interlinking completeness for AEMET metereological dataset took 0.18516898155212402s
Reputation | Calculation of the PageRank for AEMET metereological dataset took 0.02066349983215332s
Interlinking | Calculation of Degree of Connection for AEMET metereological dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AEMET metereological dataset took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for AEMET metereological dataset took 4.315376281738281e-05s
Believability | Calculation of trust value for AEMET metereological dataset took 7.3909759521484375e-06s
INFO | --- Analysis for aemet took 2.0294251441955566s
Availability | SPARQL endpoint availability check for Agenda de Zaragoza took 4.1484832763671875e-05s
Availability | VoID file availability check for Agenda de Zaragoza took 0.0004773139953613281s
Completeness | Calculation of interlinking completeness for Agenda de Zaragoza took 0.18559670448303223s
Reputation | Calculation of the PageRank for Agenda de Zaragoza took 0.02011251449584961s
Interlinking | Calculation of Degree of Connection for Agenda de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Agenda de Zaragoza took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Agenda de Zaragoza took 3.24249267578125e-05s
Believability | Calculation of trust value for Agenda de Zaragoza took 1.0967254638671875e-05s
INFO | --- Analysis for agenda-de-zaragoza took 2.156184196472168s
Availability | SPARQL endpoint availability check for AgriNepalData took 4.57763671875e-05s
Availability | VoID file availability check for AgriNepalData took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for AgriNepalData took 0.17571210861206055s
Reputation | Calculation of the PageRank for AgriNepalData took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for AgriNepalData took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for AgriNepalData took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for AgriNepalData took 6.914138793945312e-05s
Believability | Calculation of trust value for AgriNepalData took 1.1205673217773438e-05s
INFO | --- Analysis for agrinepaldata took 2.0037543773651123s
Availability | SPARQL endpoint availability check for AGRIS took 4.1961669921875e-05s
Availability | VoID file availability check for AGRIS took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for AGRIS took 0.18259096145629883s
Reputation | Calculation of the PageRank for AGRIS took 0.020494937896728516s
Interlinking | Calculation of Degree of Connection for AGRIS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AGRIS took 0.0006835460662841797s
Interlinking | Calculation of Clustering coefficient for AGRIS took 7.081031799316406e-05s
Believability | Calculation of trust value for AGRIS took 1.2159347534179688e-05s
INFO | --- Analysis for agris took 2.007812738418579s
Availability | SPARQL endpoint availability check for AGROVOC took 5.6743621826171875e-05s
Availability | VoID file availability check for AGROVOC took 0.0005888938903808594s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.18271160125732422s
Reputation | Calculation of the PageRank for AGROVOC took 0.026605606079101562s
Interlinking | Calculation of Degree of Connection for AGROVOC took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for AGROVOC took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 0.00011420249938964844s
Believability | Calculation of trust value for AGROVOC took 1.239776611328125e-05s
INFO | --- Analysis for agrovoc took 2.0048422813415527s
Availability | SPARQL endpoint availability check for AGROVOC took 8.416175842285156e-05s
Availability | VoID file availability check for AGROVOC took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for AGROVOC took 0.17384576797485352s
Reputation | Calculation of the PageRank for AGROVOC took 0.020293235778808594s
Interlinking | Calculation of Degree of Connection for AGROVOC took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AGROVOC took 0.0006823539733886719s
Interlinking | Calculation of Clustering coefficient for AGROVOC took 7.557868957519531e-05s
Believability | Calculation of trust value for AGROVOC took 1.0728836059570312e-05s
INFO | --- Analysis for agrovoc-skos took 1.9707684516906738s
Availability | SPARQL endpoint availability check for Analytics India Magazine took 4.124641418457031e-05s
Availability | VoID file availability check for Analytics India Magazine took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for Analytics India Magazine took 0.1753396987915039s
Reputation | Calculation of the PageRank for Analytics India Magazine took 0.020327329635620117s
Interlinking | Calculation of Degree of Connection for Analytics India Magazine took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Analytics India Magazine took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for Analytics India Magazine took 3.0279159545898438e-05s
Believability | Calculation of trust value for Analytics India Magazine took 1.1920928955078125e-05s
INFO | --- Analysis for AIM took 1.9811971187591553s
Availability | SPARQL endpoint availability check for All India Survey of Higher Education took 8.58306884765625e-05s
Availability | VoID file availability check for All India Survey of Higher Education took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for All India Survey of Higher Education took 0.17327499389648438s
Reputation | Calculation of the PageRank for All India Survey of Higher Education took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for All India Survey of Higher Education took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for All India Survey of Higher Education took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for All India Survey of Higher Education took 3.075599670410156e-05s
Believability | Calculation of trust value for All India Survey of Higher Education took 1.0251998901367188e-05s
INFO | --- Analysis for AISHE took 1.9704055786132812s
Availability | SPARQL endpoint availability check for  equipment ontology took 4.076957702636719e-05s
Availability | VoID file availability check for  equipment ontology took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for  equipment ontology took 0.18462204933166504s
Reputation | Calculation of the PageRank for  equipment ontology took 0.020300626754760742s
Interlinking | Calculation of Degree of Connection for  equipment ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for  equipment ontology took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for  equipment ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for  equipment ontology took 5.9604644775390625e-06s
INFO | --- Analysis for akash took 1.9934003353118896s
Availability | SPARQL endpoint availability check for aksw.org Research Group dataset took 8.368492126464844e-05s
Availability | VoID file availability check for aksw.org Research Group dataset took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for aksw.org Research Group dataset took 0.18668484687805176s
Reputation | Calculation of the PageRank for aksw.org Research Group dataset took 0.020223140716552734s
Interlinking | Calculation of Degree of Connection for aksw.org Research Group dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for aksw.org Research Group dataset took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for aksw.org Research Group dataset took 3.075599670410156e-05s
Believability | Calculation of trust value for aksw.org Research Group dataset took 5.4836273193359375e-06s
INFO | --- Analysis for aksworg took 1.9965689182281494s
Availability | SPARQL endpoint availability check for AlchemyAPI took 4.076957702636719e-05s
Availability | VoID file availability check for AlchemyAPI took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for AlchemyAPI took 0.18767166137695312s
Reputation | Calculation of the PageRank for AlchemyAPI took 0.020373821258544922s
Interlinking | Calculation of Degree of Connection for AlchemyAPI took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for AlchemyAPI took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for AlchemyAPI took 3.147125244140625e-05s
Believability | Calculation of trust value for AlchemyAPI took 1.0728836059570312e-05s
INFO | --- Analysis for alchemyapi took 2.008556604385376s
Availability | SPARQL endpoint availability check for Alexandria Digital Library (ADL) Gazetteer took 6.532669067382812e-05s
Availability | VoID file availability check for Alexandria Digital Library (ADL) Gazetteer took 0.00042557716369628906s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library (ADL) Gazetteer took 0.17487764358520508s
Reputation | Calculation of the PageRank for Alexandria Digital Library (ADL) Gazetteer took 0.020190715789794922s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library (ADL) Gazetteer took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Alexandria Digital Library (ADL) Gazetteer took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library (ADL) Gazetteer took 3.123283386230469e-05s
Believability | Calculation of trust value for Alexandria Digital Library (ADL) Gazetteer took 1.0013580322265625e-05s
INFO | --- Analysis for alexandria-digital-library-adl-gazetteer took 1.9532089233398438s
Availability | SPARQL endpoint availability check for aliada-scanbit-net took 1.1286838054656982s
Availability | VoID file availability check for aliada-scanbit-net took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for aliada-scanbit-net took 0.17816591262817383s
Reputation | Calculation of the PageRank for aliada-scanbit-net took 0.02024388313293457s
Interlinking | Calculation of Degree of Connection for aliada-scanbit-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for aliada-scanbit-net took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for aliada-scanbit-net took 0.00010919570922851562s
Believability | Calculation of trust value for aliada-scanbit-net took 9.298324584960938e-06s
INFO | --- Analysis for aliada-scanbit-net took 3.127765655517578s
Availability | SPARQL endpoint availability check for Allen Brain Atlas took 8.368492126464844e-05s
Availability | VoID file availability check for Allen Brain Atlas took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Allen Brain Atlas took 0.17635297775268555s
Reputation | Calculation of the PageRank for Allen Brain Atlas took 0.020240306854248047s
Interlinking | Calculation of Degree of Connection for Allen Brain Atlas took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Allen Brain Atlas took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Allen Brain Atlas took 3.170967102050781e-05s
Believability | Calculation of trust value for Allen Brain Atlas took 9.775161743164062e-06s
INFO | --- Analysis for allen-brain-atlas took 2.0020132064819336s
Availability | SPARQL endpoint availability check for Allie Abbreviation And Long Form Database in Life Science took 4.00543212890625e-05s
Availability | VoID file availability check for Allie Abbreviation And Long Form Database in Life Science took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Allie Abbreviation And Long Form Database in Life Science took 0.18561220169067383s
Reputation | Calculation of the PageRank for Allie Abbreviation And Long Form Database in Life Science took 0.021924495697021484s
Interlinking | Calculation of Degree of Connection for Allie Abbreviation And Long Form Database in Life Science took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Allie Abbreviation And Long Form Database in Life Science took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Allie Abbreviation And Long Form Database in Life Science took 6.508827209472656e-05s
Believability | Calculation of trust value for Allie Abbreviation And Long Form Database in Life Science took 1.2636184692382812e-05s
INFO | --- Analysis for allie-abbreviation-and-long-form-database-in-life-science took 1.9824843406677246s
Availability | SPARQL endpoint availability check for Alojamientos took 4.100799560546875e-05s
Availability | VoID file availability check for Alojamientos took 0.001069784164428711s
Completeness | Calculation of interlinking completeness for Alojamientos took 0.17366790771484375s
Reputation | Calculation of the PageRank for Alojamientos took 0.02291703224182129s
Interlinking | Calculation of Degree of Connection for Alojamientos took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Alojamientos took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Alojamientos took 3.218650817871094e-05s
Believability | Calculation of trust value for Alojamientos took 1.1920928955078125e-05s
INFO | --- Analysis for alojamientos-zaragoza took 2.006349563598633s
Availability | SPARQL endpoint availability check for ALPINO RDF Treebank took 8.296966552734375e-05s
Availability | VoID file availability check for ALPINO RDF Treebank took 0.00020074844360351562s
Completeness | Calculation of interlinking completeness for ALPINO RDF Treebank took 0.1796128749847412s
Reputation | Calculation of the PageRank for ALPINO RDF Treebank took 0.020412683486938477s
Interlinking | Calculation of Degree of Connection for ALPINO RDF Treebank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ALPINO RDF Treebank took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for ALPINO RDF Treebank took 3.8623809814453125e-05s
Believability | Calculation of trust value for ALPINO RDF Treebank took 4.76837158203125e-06s
INFO | --- Analysis for alpino-rdf took 1.973479986190796s
Availability | SPARQL endpoint availability check for AAT-atawil took 8.559226989746094e-05s
Availability | VoID file availability check for AAT-atawil took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for AAT-atawil took 0.17492389678955078s
Reputation | Calculation of the PageRank for AAT-atawil took 0.021649599075317383s
Interlinking | Calculation of Degree of Connection for AAT-atawil took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AAT-atawil took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for AAT-atawil took 3.147125244140625e-05s
Believability | Calculation of trust value for AAT-atawil took 1.0967254638671875e-05s
INFO | --- Analysis for Altawil took 1.97115159034729s
Availability | SPARQL endpoint availability check for Auckland Museum Collections Online took 8.559226989746094e-05s
Availability | VoID file availability check for Auckland Museum Collections Online took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Auckland Museum Collections Online took 0.17349934577941895s
Reputation | Calculation of the PageRank for Auckland Museum Collections Online took 0.020316600799560547s
Interlinking | Calculation of Degree of Connection for Auckland Museum Collections Online took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Auckland Museum Collections Online took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Auckland Museum Collections Online took 3.218650817871094e-05s
Believability | Calculation of trust value for Auckland Museum Collections Online took 1.049041748046875e-05s
INFO | --- Analysis for am-collections-online took 1.9634182453155518s
Availability | SPARQL endpoint availability check for Amer Nejma took 4.172325134277344e-05s
Availability | VoID file availability check for Amer Nejma took 0.0002002716064453125s
Completeness | Calculation of interlinking completeness for Amer Nejma took 0.177290678024292s
Reputation | Calculation of the PageRank for Amer Nejma took 0.022272109985351562s
Interlinking | Calculation of Degree of Connection for Amer Nejma took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Amer Nejma took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Amer Nejma took 3.147125244140625e-05s
Believability | Calculation of trust value for Amer Nejma took 5.245208740234375e-06s
INFO | --- Analysis for Amer_Nejma took 1.986682415008545s
Availability | SPARQL endpoint availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.17461061477661133s
Reputation | Calculation of the PageRank for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for AMOn+: Cultural Variations in Interpersonal Communication Ontology took 1.1444091796875e-05s
INFO | --- Analysis for amon took 2.0141284465789795s
Availability | SPARQL endpoint availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.7885551452636719s
Availability | VoID file availability check for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.18793916702270508s
Reputation | Calculation of the PageRank for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.02200913429260254s
Interlinking | Calculation of Degree of Connection for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 8.630752563476562e-05s
Believability | Calculation of trust value for Amsterdam Museum as Linked Open Data in the Europeana Data Model took 4.76837158203125e-06s
INFO | --- Analysis for amsterdam-museum-as-edm-lod took 2.7863097190856934s
Availability | SPARQL endpoint availability check for Analisi del blog http://www.beppegrillo.it/ took 8.511543273925781e-05s
Availability | VoID file availability check for Analisi del blog http://www.beppegrillo.it/ took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Analisi del blog http://www.beppegrillo.it/ took 0.1816697120666504s
Reputation | Calculation of the PageRank for Analisi del blog http://www.beppegrillo.it/ took 0.021126747131347656s
Interlinking | Calculation of Degree of Connection for Analisi del blog http://www.beppegrillo.it/ took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Analisi del blog http://www.beppegrillo.it/ took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Analisi del blog http://www.beppegrillo.it/ took 3.1948089599609375e-05s
Believability | Calculation of trust value for Analisi del blog http://www.beppegrillo.it/ took 1.1205673217773438e-05s
INFO | --- Analysis for analisi-del-blog-http-www-beppegrillo-it took 2.048450469970703s
Availability | SPARQL endpoint availability check for Animal Diversity Web took 8.296966552734375e-05s
Availability | VoID file availability check for Animal Diversity Web took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for Animal Diversity Web took 0.1837937831878662s
Reputation | Calculation of the PageRank for Animal Diversity Web took 0.0201566219329834s
Interlinking | Calculation of Degree of Connection for Animal Diversity Web took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Animal Diversity Web took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Animal Diversity Web took 3.147125244140625e-05s
Believability | Calculation of trust value for Animal Diversity Web took 1.5735626220703125e-05s
INFO | --- Analysis for animal-diversity-web took 2.0402274131774902s
Availability | SPARQL endpoint availability check for Anime Dataset took 8.392333984375e-05s
Availability | VoID file availability check for Anime Dataset took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Anime Dataset took 0.17527556419372559s
Reputation | Calculation of the PageRank for Anime Dataset took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Anime Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Anime Dataset took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Anime Dataset took 3.0517578125e-05s
Believability | Calculation of trust value for Anime Dataset took 1.0728836059570312e-05s
INFO | --- Analysis for Anime took 1.9864685535430908s
Availability | SPARQL endpoint availability check for ANNO took 8.440017700195312e-05s
Availability | VoID file availability check for ANNO took 0.0001976490020751953s
Completeness | Calculation of interlinking completeness for ANNO took 0.17182278633117676s
Reputation | Calculation of the PageRank for ANNO took 0.02036881446838379s
Interlinking | Calculation of Degree of Connection for ANNO took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ANNO took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for ANNO took 3.3855438232421875e-05s
Believability | Calculation of trust value for ANNO took 9.775161743164062e-06s
INFO | --- Analysis for anno took 1.9724628925323486s
Availability | SPARQL endpoint availability check for Antique Cars Collection (Linked Cars) took 4.076957702636719e-05s
Availability | VoID file availability check for Antique Cars Collection (Linked Cars) took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for Antique Cars Collection (Linked Cars) took 0.1766970157623291s
Reputation | Calculation of the PageRank for Antique Cars Collection (Linked Cars) took 0.020151615142822266s
Interlinking | Calculation of Degree of Connection for Antique Cars Collection (Linked Cars) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Antique Cars Collection (Linked Cars) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Antique Cars Collection (Linked Cars) took 7.510185241699219e-05s
Believability | Calculation of trust value for Antique Cars Collection (Linked Cars) took 5.0067901611328125e-06s
INFO | --- Analysis for AntiqueCarsCollection took 1.9531443119049072s
Availability | SPARQL endpoint availability check for apache took 4.0531158447265625e-05s
Availability | VoID file availability check for apache took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for apache took 0.17393803596496582s
Reputation | Calculation of the PageRank for apache took 0.02019643783569336s
Interlinking | Calculation of Degree of Connection for apache took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for apache took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for apache took 5.459785461425781e-05s
Believability | Calculation of trust value for apache took 5.245208740234375e-06s
INFO | --- Analysis for apache took 2.0008580684661865s
Availability | SPARQL endpoint availability check for Apertium RDF took 4.363059997558594e-05s
Availability | VoID file availability check for Apertium RDF took 0.00020265579223632812s
Completeness | Calculation of interlinking completeness for Apertium RDF took 0.1788473129272461s
Reputation | Calculation of the PageRank for Apertium RDF took 0.020293712615966797s
Interlinking | Calculation of Degree of Connection for Apertium RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf took 1.8927791118621826s
Availability | SPARQL endpoint availability check for Apertium RDF CA-IT took 5.14984130859375e-05s
Availability | VoID file availability check for Apertium RDF CA-IT took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Apertium RDF CA-IT took 0.18526053428649902s
Reputation | Calculation of the PageRank for Apertium RDF CA-IT took 0.020445585250854492s
Interlinking | Calculation of Degree of Connection for Apertium RDF CA-IT took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF CA-IT took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Apertium RDF CA-IT took 4.696846008300781e-05s
Believability | Calculation of trust value for Apertium RDF CA-IT took 6.198883056640625e-06s
INFO | --- Analysis for apertium-rdf-ca-it took 1.9466536045074463s
Availability | SPARQL endpoint availability check for Apertium RDF EN-CA took 3.9577484130859375e-05s
Availability | VoID file availability check for Apertium RDF EN-CA took 0.0002040863037109375s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-CA took 0.1761918067932129s
Reputation | Calculation of the PageRank for Apertium RDF EN-CA took 0.02023601531982422s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-CA took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-CA took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EN-CA took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-en-ca took 1.9224705696105957s
Availability | SPARQL endpoint availability check for Apertium RDF EN-ES took 3.981590270996094e-05s
Availability | VoID file availability check for Apertium RDF EN-ES took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-ES took 0.17569875717163086s
Reputation | Calculation of the PageRank for Apertium RDF EN-ES took 0.020204782485961914s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-ES took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-ES took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF EN-ES took 6.4373016357421875e-06s
INFO | --- Analysis for apertium-rdf-en-es took 1.9404761791229248s
Availability | SPARQL endpoint availability check for Apertium RDF EN-GL took 4.029273986816406e-05s
Availability | VoID file availability check for Apertium RDF EN-GL took 0.00020551681518554688s
Completeness | Calculation of interlinking completeness for Apertium RDF EN-GL took 0.18158197402954102s
Reputation | Calculation of the PageRank for Apertium RDF EN-GL took 0.020231962203979492s
Interlinking | Calculation of Degree of Connection for Apertium RDF EN-GL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EN-GL took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EN-GL took 4.7206878662109375e-05s
Believability | Calculation of trust value for Apertium RDF EN-GL took 5.9604644775390625e-06s
INFO | --- Analysis for apertium-rdf-en-gl took 1.92411208152771s
Availability | SPARQL endpoint availability check for Apertium RDF EO-CA took 3.886222839355469e-05s
Availability | VoID file availability check for Apertium RDF EO-CA took 0.00020599365234375s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-CA took 0.17842960357666016s
Reputation | Calculation of the PageRank for Apertium RDF EO-CA took 0.020150423049926758s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-CA took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EO-CA took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-CA took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF EO-CA took 1.3589859008789062e-05s
INFO | --- Analysis for apertium-rdf-eo-ca took 1.9842290878295898s
Availability | SPARQL endpoint availability check for Apertium RDF EO-EN took 8.273124694824219e-05s
Availability | VoID file availability check for Apertium RDF EO-EN took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-EN took 0.17524385452270508s
Reputation | Calculation of the PageRank for Apertium RDF EO-EN took 0.021871328353881836s
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.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-EN took 4.744529724121094e-05s
Believability | Calculation of trust value for Apertium RDF EO-EN took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-eo-en took 1.9590740203857422s
Availability | SPARQL endpoint availability check for Apertium RDF EO-ES took 3.981590270996094e-05s
Availability | VoID file availability check for Apertium RDF EO-ES took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-ES took 0.17382478713989258s
Reputation | Calculation of the PageRank for Apertium RDF EO-ES took 0.022232532501220703s
Interlinking | Calculation of Degree of Connection for Apertium RDF EO-ES took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Apertium RDF EO-ES took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-ES took 5.14984130859375e-05s
Believability | Calculation of trust value for Apertium RDF EO-ES took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-eo-es took 1.9819958209991455s
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.00020265579223632812s
Completeness | Calculation of interlinking completeness for Apertium RDF EO-FR took 0.1753978729248047s
Reputation | Calculation of the PageRank for Apertium RDF EO-FR took 0.02045440673828125s
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.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EO-FR took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF EO-FR took 1.0967254638671875e-05s
INFO | --- Analysis for apertium-rdf-eo-fr took 1.977341890335083s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AN took 8.296966552734375e-05s
Availability | VoID file availability check for Apertium RDF ES-AN took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AN took 0.18553757667541504s
Reputation | Calculation of the PageRank for Apertium RDF ES-AN took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AN took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AN took 4.649162292480469e-05s
Believability | Calculation of trust value for Apertium RDF ES-AN took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-es-an took 2.070208787918091s
Availability | SPARQL endpoint availability check for Apertium RDF ES-AST took 8.249282836914062e-05s
Availability | VoID file availability check for Apertium RDF ES-AST took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-AST took 0.17325067520141602s
Reputation | Calculation of the PageRank for Apertium RDF ES-AST took 0.020708799362182617s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-AST took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-AST took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-AST took 4.553794860839844e-05s
Believability | Calculation of trust value for Apertium RDF ES-AST took 5.4836273193359375e-06s
INFO | --- Analysis for apertium-rdf-es-ast took 1.9495303630828857s
Availability | SPARQL endpoint availability check for Apertium RDF ES-CA took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF ES-CA took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-CA took 0.1848924160003662s
Reputation | Calculation of the PageRank for Apertium RDF ES-CA took 0.02020859718322754s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-CA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-CA took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-CA took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF ES-CA took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-es-ca took 1.9916129112243652s
Availability | SPARQL endpoint availability check for Apertium RDF ES-GL took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF ES-GL took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-GL took 0.1782839298248291s
Reputation | Calculation of the PageRank for Apertium RDF ES-GL took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-GL took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-GL took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-GL took 4.410743713378906e-05s
Believability | Calculation of trust value for Apertium RDF ES-GL took 1.1444091796875e-05s
INFO | --- Analysis for apertium-rdf-es-gl took 2.005208969116211s
Availability | SPARQL endpoint availability check for Apertium RDF ES-PT took 4.029273986816406e-05s
Availability | VoID file availability check for Apertium RDF ES-PT took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-PT took 0.17161107063293457s
Reputation | Calculation of the PageRank for Apertium RDF ES-PT took 0.020218610763549805s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-PT took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-PT took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-PT took 4.601478576660156e-05s
Believability | Calculation of trust value for Apertium RDF ES-PT took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-es-pt took 1.9902548789978027s
Availability | SPARQL endpoint availability check for Apertium RDF ES-RO took 0.00015616416931152344s
Availability | VoID file availability check for Apertium RDF ES-RO took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Apertium RDF ES-RO took 0.1813523769378662s
Reputation | Calculation of the PageRank for Apertium RDF ES-RO took 0.022073030471801758s
Interlinking | Calculation of Degree of Connection for Apertium RDF ES-RO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF ES-RO took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for Apertium RDF ES-RO took 4.673004150390625e-05s
Believability | Calculation of trust value for Apertium RDF ES-RO took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-es-ro took 1.997215747833252s
Availability | SPARQL endpoint availability check for Apertium RDF EU-EN took 9.560585021972656e-05s
Availability | VoID file availability check for Apertium RDF EU-EN took 0.0005221366882324219s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-EN took 0.1752777099609375s
Reputation | Calculation of the PageRank for Apertium RDF EU-EN took 0.01989269256591797s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-EN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-EN took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-EN took 4.506111145019531e-05s
Believability | Calculation of trust value for Apertium RDF EU-EN took 1.239776611328125e-05s
INFO | --- Analysis for apertium-rdf-eu-en took 1.9794180393218994s
Availability | SPARQL endpoint availability check for Apertium RDF EU-ES took 0.00012636184692382812s
Availability | VoID file availability check for Apertium RDF EU-ES took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Apertium RDF EU-ES took 0.18495702743530273s
Reputation | Calculation of the PageRank for Apertium RDF EU-ES took 0.02029252052307129s
Interlinking | Calculation of Degree of Connection for Apertium RDF EU-ES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF EU-ES took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF EU-ES took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF EU-ES took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-eu-es took 2.0081915855407715s
Availability | SPARQL endpoint availability check for Apertium RDF FR-CA took 0.00010061264038085938s
Availability | VoID file availability check for Apertium RDF FR-CA took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-CA took 0.18880200386047363s
Reputation | Calculation of the PageRank for Apertium RDF FR-CA took 0.021210908889770508s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-CA took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-CA took 0.0006856918334960938s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-CA took 4.38690185546875e-05s
Believability | Calculation of trust value for Apertium RDF FR-CA took 1.049041748046875e-05s
INFO | --- Analysis for apertium-rdf-fr-ca took 2.0193114280700684s
Availability | SPARQL endpoint availability check for Apertium RDF FR-ES took 8.559226989746094e-05s
Availability | VoID file availability check for Apertium RDF FR-ES took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Apertium RDF FR-ES took 0.185211181640625s
Reputation | Calculation of the PageRank for Apertium RDF FR-ES took 0.02137899398803711s
Interlinking | Calculation of Degree of Connection for Apertium RDF FR-ES took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Apertium RDF FR-ES took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Apertium RDF FR-ES took 4.482269287109375e-05s
Believability | Calculation of trust value for Apertium RDF FR-ES took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-fr-es took 2.0852110385894775s
Availability | SPARQL endpoint availability check for Apertium RDF OC-CA took 4.0531158447265625e-05s
Availability | VoID file availability check for Apertium RDF OC-CA took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-CA took 0.18099713325500488s
Reputation | Calculation of the PageRank for Apertium RDF OC-CA took 0.020171642303466797s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-CA took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-CA took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF OC-CA took 5.7220458984375e-06s
INFO | --- Analysis for apertium-rdf-oc-ca took 1.9960229396820068s
Availability | SPARQL endpoint availability check for Apertium RDF OC-ES took 8.320808410644531e-05s
Availability | VoID file availability check for Apertium RDF OC-ES took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Apertium RDF OC-ES took 0.19054222106933594s
Reputation | Calculation of the PageRank for Apertium RDF OC-ES took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for Apertium RDF OC-ES took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Apertium RDF OC-ES took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Apertium RDF OC-ES took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF OC-ES took 1.2159347534179688e-05s
INFO | --- Analysis for apertium-rdf-oc-es took 2.014751434326172s
Availability | SPARQL endpoint availability check for Apertium RDF PT-CA took 8.296966552734375e-05s
Availability | VoID file availability check for Apertium RDF PT-CA took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-CA took 0.18683171272277832s
Reputation | Calculation of the PageRank for Apertium RDF PT-CA took 0.022052526473999023s
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.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-CA took 4.363059997558594e-05s
Believability | Calculation of trust value for Apertium RDF PT-CA took 1.1205673217773438e-05s
INFO | --- Analysis for apertium-rdf-pt-ca took 2.0157742500305176s
Availability | SPARQL endpoint availability check for Apertium RDF PT-GL took 8.559226989746094e-05s
Availability | VoID file availability check for Apertium RDF PT-GL took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Apertium RDF PT-GL took 0.17668461799621582s
Reputation | Calculation of the PageRank for Apertium RDF PT-GL took 0.02021050453186035s
Interlinking | Calculation of Degree of Connection for Apertium RDF PT-GL took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Apertium RDF PT-GL took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Apertium RDF PT-GL took 4.57763671875e-05s
Believability | Calculation of trust value for Apertium RDF PT-GL took 1.0251998901367188e-05s
INFO | --- Analysis for apertium-rdf-pt-gl took 2.030582904815674s
Availability | SPARQL endpoint availability check for AragoDBPedia took 8.559226989746094e-05s
Availability | VoID file availability check for AragoDBPedia took 0.0005314350128173828s
Completeness | Calculation of interlinking completeness for AragoDBPedia took 0.18520069122314453s
Reputation | Calculation of the PageRank for AragoDBPedia took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for AragoDBPedia took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for AragoDBPedia took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for AragoDBPedia took 4.076957702636719e-05s
Believability | Calculation of trust value for AragoDBPedia took 1.1682510375976562e-05s
INFO | --- Analysis for aragodbpedia took 2.027606964111328s
Availability | SPARQL endpoint availability check for Archives Hub Linked Data took 3.933906555175781e-05s
Availability | VoID file availability check for Archives Hub Linked Data took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for Archives Hub Linked Data took 0.17400908470153809s
Reputation | Calculation of the PageRank for Archives Hub Linked Data took 0.020080089569091797s
Interlinking | Calculation of Degree of Connection for Archives Hub Linked Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Archives Hub Linked Data took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Archives Hub Linked Data took 5.221366882324219e-05s
Believability | Calculation of trust value for Archives Hub Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for archiveshub-linkeddata took 1.9995763301849365s
Availability | SPARQL endpoint availability check for Archivi ISMA took 3.886222839355469e-05s
Availability | VoID file availability check for Archivi ISMA took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for Archivi ISMA took 0.17646384239196777s
Reputation | Calculation of the PageRank for Archivi ISMA took 0.02158951759338379s
Interlinking | Calculation of Degree of Connection for Archivi ISMA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Archivi ISMA took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Archivi ISMA took 3.075599670410156e-05s
Believability | Calculation of trust value for Archivi ISMA took 1.0251998901367188e-05s
INFO | --- Analysis for archivio-isma took 2.045053720474243s
Availability | SPARQL endpoint availability check for ARIADNE took 8.058547973632812e-05s
Availability | VoID file availability check for ARIADNE took 0.00020694732666015625s
Completeness | Calculation of interlinking completeness for ARIADNE took 0.17639565467834473s
Reputation | Calculation of the PageRank for ARIADNE took 0.020021438598632812s
Interlinking | Calculation of Degree of Connection for ARIADNE took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ARIADNE took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for ARIADNE took 2.9802322387695312e-05s
Believability | Calculation of trust value for ARIADNE took 9.775161743164062e-06s
INFO | --- Analysis for ariadne took 1.9928817749023438s
Availability | SPARQL endpoint availability check for Aristotle University took 4.2438507080078125e-05s
Availability | VoID file availability check for Aristotle University took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Aristotle University took 0.18694067001342773s
Reputation | Calculation of the PageRank for Aristotle University took 0.02023625373840332s
Interlinking | Calculation of Degree of Connection for Aristotle University took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Aristotle University took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Aristotle University took 3.528594970703125e-05s
Believability | Calculation of trust value for Aristotle University took 9.775161743164062e-06s
INFO | --- Analysis for aristotle-university took 1.9697458744049072s
Availability | SPARQL endpoint availability check for Transcription profiling of human, chimp and mouse brain took 8.273124694824219e-05s
Availability | VoID file availability check for Transcription profiling of human, chimp and mouse brain took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Transcription profiling of human, chimp and mouse brain took 0.18235373497009277s
Reputation | Calculation of the PageRank for Transcription profiling of human, chimp and mouse brain took 0.02230072021484375s
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.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of human, chimp and mouse brain took 3.123283386230469e-05s
Believability | Calculation of trust value for Transcription profiling of human, chimp and mouse brain took 1.0251998901367188e-05s
INFO | --- Analysis for arrayexpress-e-afmx-1 took 2.014011859893799s
Availability | SPARQL endpoint availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 4.3392181396484375e-05s
Availability | VoID file availability check for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.18516278266906738s
Reputation | Calculation of the PageRank for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.021353721618652344s
Interlinking | Calculation of Degree of Connection for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 0.0006861686706542969s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Transcription profiling of mouse cell types and tissues (GNF/Novartis) took 1.3113021850585938e-05s
INFO | --- Analysis for arrayexpress_e-afmx-4 took 2.0247085094451904s
Availability | SPARQL endpoint availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 4.172325134277344e-05s
Availability | VoID file availability check for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.17943525314331055s
Reputation | Calculation of the PageRank for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.02007770538330078s
Interlinking | Calculation of Degree of Connection for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 3.981590270996094e-05s
Believability | Calculation of trust value for Transcription profiling of rat bladder after inoculation with bladder cancer cells took 1.2874603271484375e-05s
INFO | --- Analysis for arrayexpress_e-mtab-104 took 2.0951762199401855s
Availability | SPARQL endpoint availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 7.987022399902344e-05s
Availability | VoID file availability check for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.00020074844360351562s
Completeness | Calculation of interlinking completeness for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.18442678451538086s
Reputation | Calculation of the PageRank for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.020148038864135742s
Interlinking | Calculation of Degree of Connection for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 9.703636169433594e-05s
Believability | Calculation of trust value for Entornos interactivos. Arte en los nuevos medios (GNOSS) took 1.049041748046875e-05s
INFO | --- Analysis for artenuevosmedios-gnoss took 1.9892148971557617s
Availability | SPARQL endpoint availability check for Arthroscopy community took 8.225440979003906e-05s
Availability | VoID file availability check for Arthroscopy community took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for Arthroscopy community took 0.20584821701049805s
Reputation | Calculation of the PageRank for Arthroscopy community took 0.02249288558959961s
Interlinking | Calculation of Degree of Connection for Arthroscopy community took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Arthroscopy community took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Arthroscopy community took 9.655952453613281e-05s
Believability | Calculation of trust value for Arthroscopy community took 9.298324584960938e-06s
INFO | --- Analysis for arthroscopy took 1.9904437065124512s
Availability | SPARQL endpoint availability check for Wikidata entry for Art × Science International took 8.20159912109375e-05s
Availability | VoID file availability check for Wikidata entry for Art × Science International took 0.00041174888610839844s
Completeness | Calculation of interlinking completeness for Wikidata entry for Art × Science International took 0.17654752731323242s
Reputation | Calculation of the PageRank for Wikidata entry for Art × Science International took 0.020143508911132812s
Interlinking | Calculation of Degree of Connection for Wikidata entry for Art × Science International took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Wikidata entry for Art × Science International took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Wikidata entry for Art × Science International took 1.3828277587890625e-05s
Believability | Calculation of trust value for Wikidata entry for Art × Science International took 1.0251998901367188e-05s
INFO | --- Analysis for artxscienceinternational-wikidata took 1.9766030311584473s
Availability | SPARQL endpoint availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 3.660444736480713s
Availability | VoID file availability check for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.18131589889526367s
Reputation | Calculation of the PageRank for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.02008366584777832s
Interlinking | Calculation of Degree of Connection for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 0.0006661415100097656s
Interlinking | Calculation of Clustering coefficient for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 7.224082946777344e-05s
Believability | Calculation of trust value for The National Taiwan Museum's Formosan Aborigines Collections Digitizing Project (NTM-Formosan-Aborigines) took 9.775161743164062e-06s
INFO | --- Analysis for ASCDC-_NTM-Formosan-Aborigines took 5.677746057510376s
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.3845510482788086s
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.0004639625549316406s
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.1742877960205078s
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.020937204360961914s
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.0013580322265625e-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.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 7.414817810058594e-05s
Believability | Calculation of trust value for Archive of the Art Textbooks of Elementary and Public Schools in the Japanese Colonial Period (AS-NTUE-School-Art-Textbooks) took 9.5367431640625e-06s
INFO | --- Analysis for ASCDC-AS-NTUE-School-Art-Textbooks took 4.3808510303497314s
Availability | SPARQL endpoint availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 2.3800461292266846s
Availability | VoID file availability check for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.18044424057006836s
Reputation | Calculation of the PageRank for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.02083611488342285s
Interlinking | Calculation of Degree of Connection for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Taiwan Fauna Database Research: Taiwan Digital Fish Species Database (AS-TFD-Fish-Species) took 0.0006861686706542969s
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.0251998901367188e-05s
INFO | --- Analysis for ASCDC-AS-TFD-Fish-Species took 4.3405351638793945s
Availability | SPARQL endpoint availability check for Database of Chinese Rare Books (CRB) took 2.377904176712036s
Availability | VoID file availability check for Database of Chinese Rare Books (CRB) took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Database of Chinese Rare Books (CRB) took 0.1840837001800537s
Reputation | Calculation of the PageRank for Database of Chinese Rare Books (CRB) took 0.021795988082885742s
Interlinking | Calculation of Degree of Connection for Database of Chinese Rare Books (CRB) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of Chinese Rare Books (CRB) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Database of Chinese Rare Books (CRB) took 4.220008850097656e-05s
Believability | Calculation of trust value for Database of Chinese Rare Books (CRB) took 8.821487426757812e-06s
INFO | --- Analysis for ASCDC-CRB took 4.365959405899048s
Availability | SPARQL endpoint availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 2.379525661468506s
Availability | VoID file availability check for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.186981201171875s
Reputation | Calculation of the PageRank for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.021976470947265625s
Interlinking | Calculation of Degree of Connection for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 8.58306884765625e-05s
Believability | Calculation of trust value for The Chinese Television System Educational and Cultural Programs Digital Archive (CTS-TV-Programs) took 9.5367431640625e-06s
INFO | --- Analysis for ASCDC-CTS-TV-Programs took 4.377150535583496s
Availability | SPARQL endpoint availability check for Database of Qing Official Titles (DQOT) took 2.3818416595458984s
Availability | VoID file availability check for Database of Qing Official Titles (DQOT) took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Database of Qing Official Titles (DQOT) took 0.184769868850708s
Reputation | Calculation of the PageRank for Database of Qing Official Titles (DQOT) took 0.021989107131958008s
Interlinking | Calculation of Degree of Connection for Database of Qing Official Titles (DQOT) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Database of Qing Official Titles (DQOT) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Database of Qing Official Titles (DQOT) took 3.695487976074219e-05s
Believability | Calculation of trust value for Database of Qing Official Titles (DQOT) took 1.0967254638671875e-05s
INFO | --- Analysis for ASCDC-DQOT took 4.401392459869385s
Availability | SPARQL endpoint availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 2.390202283859253s
Availability | VoID file availability check for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0002651214599609375s
Completeness | Calculation of interlinking completeness for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.17915940284729004s
Reputation | Calculation of the PageRank for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.021210193634033203s
Interlinking | Calculation of Degree of Connection for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Database of the Han Wooden Slips Character Dictionary (WCD) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Database of the Han Wooden Slips Character Dictionary (WCD) took 7.677078247070312e-05s
Believability | Calculation of trust value for Database of the Han Wooden Slips Character Dictionary (WCD) took 1.1920928955078125e-05s
INFO | --- Analysis for ASCDC-IHP-WCD took 4.362901449203491s
Availability | SPARQL endpoint availability check for Linked Taiwan Artists (LTA) took 3.1622390747070312s
Availability | VoID file availability check for Linked Taiwan Artists (LTA) took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Linked Taiwan Artists (LTA) took 0.18618535995483398s
Reputation | Calculation of the PageRank for Linked Taiwan Artists (LTA) took 0.0223543643951416s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Artists (LTA) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Artists (LTA) took 0.0006837844848632812s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Artists (LTA) took 7.486343383789062e-05s
Believability | Calculation of trust value for Linked Taiwan Artists (LTA) took 1.0013580322265625e-05s
INFO | --- Analysis for ASCDC-Linked-Taiwan-Artists took 5.208405494689941s
Availability | SPARQL endpoint availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 2.3806560039520264s
Availability | VoID file availability check for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.18067002296447754s
Reputation | Calculation of the PageRank for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.02232074737548828s
Interlinking | Calculation of Degree of Connection for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 5.078315734863281e-05s
Believability | Calculation of trust value for Research on the Aquatic Animals in Taiwan and its Neighborhood Area (NMMBA-Aquatic-Animals-in-Taiwan) took 1.2874603271484375e-05s
INFO | --- Analysis for ASCDC-NMMBA-Aquatic-Animals-in-Taiwan took 4.376503229141235s
Availability | SPARQL endpoint availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 2.379535436630249s
Availability | VoID file availability check for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.18358874320983887s
Reputation | Calculation of the PageRank for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.01999211311340332s
Interlinking | Calculation of Degree of Connection for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 5.078315734863281e-05s
Believability | Calculation of trust value for The Digital Collection of Taiwan's Fish Otoliths (NMMBA-Fish-Otoliths) took 1.049041748046875e-05s
INFO | --- Analysis for ASCDC-NMMBA-Fish-Otoliths took 4.361166000366211s
Availability | SPARQL endpoint availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 3.85663104057312s
Availability | VoID file availability check for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.1806490421295166s
Reputation | Calculation of the PageRank for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.02249908447265625s
Interlinking | Calculation of Degree of Connection for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 5.1975250244140625e-05s
Believability | Calculation of trust value for Dataset of the Qing Secret Societies (Sect of the Shifokou Wangs' Clan) took 1.0728836059570312e-05s
INFO | --- Analysis for ASCDC-Qing-Secret-Societies took 5.856685161590576s
Availability | SPARQL endpoint availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 2.381058692932129s
Availability | VoID file availability check for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.17249441146850586s
Reputation | Calculation of the PageRank for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.020197391510009766s
Interlinking | Calculation of Degree of Connection for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 7.343292236328125e-05s
Believability | Calculation of trust value for The Tibetan Collection Audio Archive Research Project (Tibetan Audio Archive) took 1.049041748046875e-05s
INFO | --- Analysis for ASCDC-Tibetan-Audio-Archive took 4.3999433517456055s
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.3824305534362793s
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.0005009174346923828s
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.30222105979919434s
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.021612167358398438s
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 8.58306884765625e-06s
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.0006866455078125s
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.534027099609375e-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 5.245208740234375e-06s
INFO | --- Analysis for ASCDC_-_CCP_Archive took 4.480677366256714s
Availability | SPARQL endpoint availability check for Database of Names and Biographies (DNB) took 2.381931781768799s
Availability | VoID file availability check for Database of Names and Biographies (DNB) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Database of Names and Biographies (DNB) took 0.17940759658813477s
Reputation | Calculation of the PageRank for Database of Names and Biographies (DNB) took 0.019980192184448242s
Interlinking | Calculation of Degree of Connection for Database of Names and Biographies (DNB) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Database of Names and Biographies (DNB) took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for Database of Names and Biographies (DNB) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Database of Names and Biographies (DNB) took 5.4836273193359375e-06s
INFO | --- Analysis for ASCDC_-_DNB took 4.36377215385437s
Availability | SPARQL endpoint availability check for Atlante Sintattico d'Italia (ASIt) took 8.296966552734375e-05s
Availability | VoID file availability check for Atlante Sintattico d'Italia (ASIt) took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Atlante Sintattico d'Italia (ASIt) took 0.18639826774597168s
Reputation | Calculation of the PageRank for Atlante Sintattico d'Italia (ASIt) took 0.021648645401000977s
Interlinking | Calculation of Degree of Connection for Atlante Sintattico d'Italia (ASIt) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Atlante Sintattico d'Italia (ASIt) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Atlante Sintattico d'Italia (ASIt) took 6.818771362304688e-05s
Believability | Calculation of trust value for Atlante Sintattico d'Italia (ASIt) took 1.4066696166992188e-05s
INFO | --- Analysis for asit took 2.044088363647461s
Availability | SPARQL endpoint availability check for Automated Similarity Judgment Program lexical data took 3.910064697265625e-05s
Availability | VoID file availability check for Automated Similarity Judgment Program lexical data took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Automated Similarity Judgment Program lexical data took 0.183197021484375s
Reputation | Calculation of the PageRank for Automated Similarity Judgment Program lexical data took 0.021383285522460938s
Interlinking | Calculation of Degree of Connection for Automated Similarity Judgment Program lexical data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Automated Similarity Judgment Program lexical data took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Automated Similarity Judgment Program lexical data took 3.933906555175781e-05s
Believability | Calculation of trust value for Automated Similarity Judgment Program lexical data took 1.2159347534179688e-05s
INFO | --- Analysis for asjp took 1.9694676399230957s
Availability | SPARQL endpoint availability check for ASN:US took 8.606910705566406e-05s
Availability | VoID file availability check for ASN:US took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for ASN:US took 0.17369842529296875s
Reputation | Calculation of the PageRank for ASN:US took 0.02048659324645996s
Interlinking | Calculation of Degree of Connection for ASN:US took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ASN:US took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for ASN:US took 6.413459777832031e-05s
Believability | Calculation of trust value for ASN:US took 8.106231689453125e-06s
INFO | --- Analysis for asn-us took 1.9608354568481445s
Availability | SPARQL endpoint availability check for Talis Aspire - Manchester Metropolitan University took 8.821487426757812e-05s
Availability | VoID file availability check for Talis Aspire - Manchester Metropolitan University took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Talis Aspire - Manchester Metropolitan University took 0.17346835136413574s
Reputation | Calculation of the PageRank for Talis Aspire - Manchester Metropolitan University took 0.022070646286010742s
Interlinking | Calculation of Degree of Connection for Talis Aspire - Manchester Metropolitan University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Talis Aspire - Manchester Metropolitan University took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Talis Aspire - Manchester Metropolitan University took 3.2901763916015625e-05s
Believability | Calculation of trust value for Talis Aspire - Manchester Metropolitan University took 1.2874603271484375e-05s
INFO | --- Analysis for aspire-mmu took 1.9598019123077393s
Availability | SPARQL endpoint availability check for associations took 8.368492126464844e-05s
Availability | VoID file availability check for associations took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for associations took 0.18205499649047852s
Reputation | Calculation of the PageRank for associations took 0.02133011817932129s
Interlinking | Calculation of Degree of Connection for associations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for associations took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for associations took 6.461143493652344e-05s
Believability | Calculation of trust value for associations took 1.2159347534179688e-05s
INFO | --- Analysis for associations took 1.9674150943756104s
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.0005233287811279297s
Completeness | Calculation of interlinking completeness for ATC publikovaná SÚKL took 0.1744685173034668s
Reputation | Calculation of the PageRank for ATC publikovaná SÚKL took 0.02223992347717285s
Interlinking | Calculation of Degree of Connection for ATC publikovaná SÚKL took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for ATC publikovaná SÚKL took 0.0010929107666015625s
Interlinking | Calculation of Clustering coefficient for ATC publikovaná SÚKL took 4.291534423828125e-05s
Believability | Calculation of trust value for ATC publikovaná SÚKL took 1.239776611328125e-05s
INFO | --- Analysis for atc-publikovan--s-kl took 1.955627679824829s
Availability | SPARQL endpoint availability check for Athelia RFID, a global knowledge network of RFID technology took 4.00543212890625e-05s
Availability | VoID file availability check for Athelia RFID, a global knowledge network of RFID technology took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Athelia RFID, a global knowledge network of RFID technology took 0.17491698265075684s
Reputation | Calculation of the PageRank for Athelia RFID, a global knowledge network of RFID technology took 0.020109891891479492s
Interlinking | Calculation of Degree of Connection for Athelia RFID, a global knowledge network of RFID technology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Athelia RFID, a global knowledge network of RFID technology took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Athelia RFID, a global knowledge network of RFID technology took 8.702278137207031e-05s
Believability | Calculation of trust value for Athelia RFID, a global knowledge network of RFID technology took 1.2159347534179688e-05s
INFO | --- Analysis for athelia-rfid took 2.0085582733154297s
Availability | SPARQL endpoint availability check for AUEB Linked Open Data took 3.933906555175781e-05s
Availability | VoID file availability check for AUEB Linked Open Data took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for AUEB Linked Open Data took 0.1853494644165039s
Reputation | Calculation of the PageRank for AUEB Linked Open Data took 0.020164012908935547s
Interlinking | Calculation of Degree of Connection for AUEB Linked Open Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for AUEB Linked Open Data took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for AUEB Linked Open Data took 2.956390380859375e-05s
Believability | Calculation of trust value for AUEB Linked Open Data took 1.1682510375976562e-05s
INFO | --- Analysis for aueb-linked-open-data took 1.9836626052856445s
Availability | SPARQL endpoint availability check for Augustini Confessiones in LiLa took 8.7738037109375e-05s
Availability | VoID file availability check for Augustini Confessiones in LiLa took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Augustini Confessiones in LiLa took 0.18243622779846191s
Reputation | Calculation of the PageRank for Augustini Confessiones in LiLa took 0.020220518112182617s
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.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Augustini Confessiones in LiLa took 4.982948303222656e-05s
Believability | Calculation of trust value for Augustini Confessiones in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for AugustiniConfessiones took 1.9891486167907715s
Availability | SPARQL endpoint availability check for Alpine Ski Racers of Austria took 8.296966552734375e-05s
Availability | VoID file availability check for Alpine Ski Racers of Austria took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Alpine Ski Racers of Austria took 0.17528009414672852s
Reputation | Calculation of the PageRank for Alpine Ski Racers of Austria took 0.02016282081604004s
Interlinking | Calculation of Degree of Connection for Alpine Ski Racers of Austria took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Alpine Ski Racers of Austria took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Alpine Ski Racers of Austria took 8.726119995117188e-05s
Believability | Calculation of trust value for Alpine Ski Racers of Austria took 1.2636184692382812e-05s
INFO | --- Analysis for austrian_ski_racers took 1.9788334369659424s
Availability | SPARQL endpoint availability check for AVsOnto took 8.368492126464844e-05s
Availability | VoID file availability check for AVsOnto took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for AVsOnto took 0.1864316463470459s
Reputation | Calculation of the PageRank for AVsOnto took 0.021728515625s
Interlinking | Calculation of Degree of Connection for AVsOnto took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for AVsOnto took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for AVsOnto took 3.0517578125e-05s
Believability | Calculation of trust value for AVsOnto took 1.1682510375976562e-05s
INFO | --- Analysis for AVsOnto took 2.004970073699951s
Availability | SPARQL endpoint availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.3133060932159424s
Availability | VoID file availability check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0004897117614746094s
Extra | Recovery of all triples for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 194.9137134552002s
Performance | Total latancy measurement for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.5039722919464111s
Amount of data | Number of triples check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0783817768097s
Interoperability | New terms check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 207.31481432914734s
Versatility | Languages check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.02681159973145s
Interpretability | Number of blank nodes check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10337710380554s
Security | Check HTTPS for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.46564698219299316s
Interpretability | RDF structures check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.153702974319458s
Versatility | Serialization formats check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1526482105255127s
Availability | RDF dump link check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10504007339477539s
License | MR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 44.34609866142273s
License | HR license check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.08004689216614s
Amount of data | Number of property check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13791704177856445s
Understandability | Number of label check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.0717713832855s
Understandability | URI regex check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.24677276611328125s
Understandability | Vocabs check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.10633230209350586s
Verifiability | Authors check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1604936122894287s
Verifiability | Publishers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.09674358367919922s
Performance | Throughput check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 10.51204538345337s
Amount of data | Check the number of entities for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 6.866455078125e-05s
Verifiability | Contribs. check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0957498550415039s
Interlinking | sameAs chians check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.10285329818726s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.16019153594970703s
Interlinking | skos check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.1117408275604248s
Timeliness | dataset update frequency check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.12551283836364746s
Currency | Creation date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.22209572792053223s
Currency | Modification date check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.27747488021850586s
Rep.Conc. | URIs length for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 725.1084806919098s
Interoperability | New vocabularies check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 7.62939453125e-06s
Consistency | Deprecated classes/propertiers check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.14655756950378418s
Accuracy | Check Empty annotation labels for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 11.440062761306763s
Accuracy | Check White space in annotation for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.1562983989715576s
Accuracy | Check Datatype consistency for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 4.67991828918457s
Consistency | Disjoint class check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.13686585426330566s
Consistency | Check Misplaced properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 300.30660581588745s
Consistency | Check Ontology hijacking for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 27.92451786994934s
Consistency | Check Invalid usage of undefined classes for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 3.219116687774658s
Consistency | Check Invalid usage of undefined properties for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 301.39499258995056s
Conciseness | Check Extensional conciseness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.8094100952148438s
Security | Sign check for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.2592658996582031s
Availability | Check URIs Dereferenciability for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.120412826538086s
Completeness | Calculation of interlinking completeness for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.4793221950531006s
Reputation | Calculation of the PageRank for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.021121501922607422s
Interlinking | Calculation of Degree of Connection for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 0.0007154941558837891s
Interlinking | Calculation of Clustering coefficient for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 8.58306884765625e-05s
Interoperability | Check the re-using of existing vocabs for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 2.384185791015625e-06s
Believability | Calculation of trust value for B3Kat - Library Union Catalogues of Bavaria, Berlin and Brandenburg took 9.059906005859375e-06s
INFO | --- Analysis for b3kat took 4277.973699092865s
Availability | SPARQL endpoint availability check for BabelNet took 4.267692565917969e-05s
Availability | VoID file availability check for BabelNet took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for BabelNet took 0.17952871322631836s
Reputation | Calculation of the PageRank for BabelNet took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for BabelNet took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BabelNet took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for BabelNet took 0.0001633167266845703s
Believability | Calculation of trust value for BabelNet took 1.239776611328125e-05s
INFO | --- Analysis for babelnet took 2.037698984146118s
Availability | SPARQL endpoint availability check for Bacevicius.lt took 5.14984130859375e-05s
Availability | VoID file availability check for Bacevicius.lt took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Bacevicius.lt took 0.18135905265808105s
Reputation | Calculation of the PageRank for Bacevicius.lt took 0.0200192928314209s
Interlinking | Calculation of Degree of Connection for Bacevicius.lt took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bacevicius.lt took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Bacevicius.lt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bacevicius.lt took 1.1205673217773438e-05s
INFO | --- Analysis for Bacevicius.lt took 2.02429461479187s
Availability | SPARQL endpoint availability check for Basisregistratie Adressen en Gebouwen took 8.559226989746094e-05s
Availability | VoID file availability check for Basisregistratie Adressen en Gebouwen took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Basisregistratie Adressen en Gebouwen took 0.1788167953491211s
Reputation | Calculation of the PageRank for Basisregistratie Adressen en Gebouwen took 0.02252340316772461s
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.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Basisregistratie Adressen en Gebouwen took 4.9114227294921875e-05s
Believability | Calculation of trust value for Basisregistratie Adressen en Gebouwen took 1.0967254638671875e-05s
INFO | --- Analysis for bag took 1.9654982089996338s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 0.00010204315185546875s
Availability | VoID file availability check for 红色经典歌曲 took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.17540740966796875s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020201921463012695s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 3.0040740966796875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1444091796875e-05s
INFO | --- Analysis for baixue took 1.9570674896240234s
Availability | SPARQL endpoint availability check for baixue composer took 8.487701416015625e-05s
Availability | VoID file availability check for baixue composer took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for baixue composer took 0.18221020698547363s
Reputation | Calculation of the PageRank for baixue composer took 0.01999211311340332s
Interlinking | Calculation of Degree of Connection for baixue composer took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for baixue composer took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for baixue composer took 2.86102294921875e-05s
Believability | Calculation of trust value for baixue composer took 1.1205673217773438e-05s
INFO | --- Analysis for baixue_composer took 1.971634864807129s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 5.14984130859375e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.17927837371826172s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.020162582397460938s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.8371810913085938e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.1444091796875e-05s
INFO | --- Analysis for baixue_imagery took 1.9800200462341309s
Availability | SPARQL endpoint availability check for 红色经典歌曲 took 3.981590270996094e-05s
Availability | VoID file availability check for 红色经典歌曲 took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for 红色经典歌曲 took 0.1875143051147461s
Reputation | Calculation of the PageRank for 红色经典歌曲 took 0.02022719383239746s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲 took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for 红色经典歌曲 took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲 took 2.86102294921875e-05s
Believability | Calculation of trust value for 红色经典歌曲 took 1.0728836059570312e-05s
INFO | --- Analysis for baixue_imagery1 took 1.9618027210235596s
Availability | SPARQL endpoint availability check for BAMS took 8.726119995117188e-05s
Availability | VoID file availability check for BAMS took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for BAMS took 0.17371368408203125s
Reputation | Calculation of the PageRank for BAMS took 0.02012324333190918s
Interlinking | Calculation of Degree of Connection for BAMS took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for BAMS took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for BAMS took 3.0040740966796875e-05s
Believability | Calculation of trust value for BAMS took 1.2636184692382812e-05s
INFO | --- Analysis for bams took 1.984656810760498s
Availability | SPARQL endpoint availability check for Basque EuroWordNet-lemon lexicon (3.0) took 8.58306884765625e-05s
Availability | VoID file availability check for Basque EuroWordNet-lemon lexicon (3.0) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for Basque EuroWordNet-lemon lexicon (3.0) took 0.1750192642211914s
Reputation | Calculation of the PageRank for Basque EuroWordNet-lemon lexicon (3.0) took 0.019962072372436523s
Interlinking | Calculation of Degree of Connection for Basque EuroWordNet-lemon lexicon (3.0) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Basque EuroWordNet-lemon lexicon (3.0) took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Basque EuroWordNet-lemon lexicon (3.0) took 3.790855407714844e-05s
Believability | Calculation of trust value for Basque EuroWordNet-lemon lexicon (3.0) took 5.4836273193359375e-06s
INFO | --- Analysis for basque-eurowordnet-lemon-lexicon-3-0 took 1.9740626811981201s
Availability | SPARQL endpoint availability check for BBC Music took 0.4503457546234131s
Availability | VoID file availability check for BBC Music took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for BBC Music took 0.18237090110778809s
Reputation | Calculation of the PageRank for BBC Music took 0.02154231071472168s
Interlinking | Calculation of Degree of Connection for BBC Music took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BBC Music took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for BBC Music took 0.00012135505676269531s
Believability | Calculation of trust value for BBC Music took 5.7220458984375e-06s
INFO | --- Analysis for bbc-music took 2.452690601348877s
Availability | SPARQL endpoint availability check for BBC Programmes took 8.487701416015625e-05s
Availability | VoID file availability check for BBC Programmes took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for BBC Programmes took 0.18036770820617676s
Reputation | Calculation of the PageRank for BBC Programmes took 0.01996326446533203s
Interlinking | Calculation of Degree of Connection for BBC Programmes took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BBC Programmes took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for BBC Programmes took 9.918212890625e-05s
Believability | Calculation of trust value for BBC Programmes took 1.0967254638671875e-05s
INFO | --- Analysis for bbc-programmes took 1.990365743637085s
Availability | SPARQL endpoint availability check for BBC Wildlife Finder took 0.4665822982788086s
Availability | VoID file availability check for BBC Wildlife Finder took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for BBC Wildlife Finder took 0.18110251426696777s
Reputation | Calculation of the PageRank for BBC Wildlife Finder took 0.02309274673461914s
Interlinking | Calculation of Degree of Connection for BBC Wildlife Finder took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBC Wildlife Finder took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for BBC Wildlife Finder took 9.799003601074219e-05s
Believability | Calculation of trust value for BBC Wildlife Finder took 1.049041748046875e-05s
INFO | --- Analysis for bbc-wildlife-finder took 2.471771001815796s
Availability | SPARQL endpoint availability check for BBOP took 8.940696716308594e-05s
Availability | VoID file availability check for BBOP took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for BBOP took 0.18382787704467773s
Reputation | Calculation of the PageRank for BBOP took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for BBOP took 7.3909759521484375e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0006830692291259766s
Interlinking | Calculation of Clustering coefficient for BBOP took 2.8371810913085938e-05s
Believability | Calculation of trust value for BBOP took 1.1444091796875e-05s
INFO | --- Analysis for bbop took 1.9955739974975586s
Availability | SPARQL endpoint availability check for BBOP took 4.172325134277344e-05s
Availability | VoID file availability check for BBOP took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for BBOP took 0.17729949951171875s
Reputation | Calculation of the PageRank for BBOP took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for BBOP took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for BBOP took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for BBOP took 3.123283386230469e-05s
Believability | Calculation of trust value for BBOP took 1.239776611328125e-05s
INFO | --- Analysis for bbop-selected took 1.991403341293335s
Availability | SPARQL endpoint availability check for Bdgp took 4.100799560546875e-05s
Availability | VoID file availability check for Bdgp took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Bdgp took 0.4197547435760498s
Reputation | Calculation of the PageRank for Bdgp took 0.02039194107055664s
Interlinking | Calculation of Degree of Connection for Bdgp took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bdgp took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Bdgp took 3.314018249511719e-05s
Believability | Calculation of trust value for Bdgp took 1.33514404296875e-05s
INFO | --- Analysis for bdgp took 2.222031593322754s
Availability | SPARQL endpoint availability check for Bendev Junior took 4.1484832763671875e-05s
Availability | VoID file availability check for Bendev Junior took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for Bendev Junior took 0.17567753791809082s
Reputation | Calculation of the PageRank for Bendev Junior took 0.02009725570678711s
Interlinking | Calculation of Degree of Connection for Bendev Junior took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Bendev Junior took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Bendev Junior took 3.337860107421875e-05s
Believability | Calculation of trust value for Bendev Junior took 1.1682510375976562e-05s
INFO | --- Analysis for bendevoficial took 2.004343032836914s
Availability | SPARQL endpoint availability check for EU: fintrans.publicdata.eu took 9.202957153320312e-05s
Availability | VoID file availability check for EU: fintrans.publicdata.eu took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for EU: fintrans.publicdata.eu took 0.18596458435058594s
Reputation | Calculation of the PageRank for EU: fintrans.publicdata.eu took 0.020153045654296875s
Interlinking | Calculation of Degree of Connection for EU: fintrans.publicdata.eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU: fintrans.publicdata.eu took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for EU: fintrans.publicdata.eu took 6.67572021484375e-05s
Believability | Calculation of trust value for EU: fintrans.publicdata.eu took 1.1920928955078125e-05s
INFO | --- Analysis for beneficiaries-of-the-european-commission took 1.9771313667297363s
Availability | SPARQL endpoint availability check for Berlin Offener Haushalt took 4.0531158447265625e-05s
Availability | VoID file availability check for Berlin Offener Haushalt took 0.0005204677581787109s
Completeness | Calculation of interlinking completeness for Berlin Offener Haushalt took 0.1836071014404297s
Reputation | Calculation of the PageRank for Berlin Offener Haushalt took 0.022621870040893555s
Interlinking | Calculation of Degree of Connection for Berlin Offener Haushalt took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Berlin Offener Haushalt took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Berlin Offener Haushalt took 2.9802322387695312e-05s
Believability | Calculation of trust value for Berlin Offener Haushalt took 1.0251998901367188e-05s
INFO | --- Analysis for berlin-offener-haushalt took 1.98055100440979s
Availability | SPARQL endpoint availability check for berlios took 8.225440979003906e-05s
Availability | VoID file availability check for berlios took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for berlios took 0.1748056411743164s
Reputation | Calculation of the PageRank for berlios took 0.019976139068603516s
Interlinking | Calculation of Degree of Connection for berlios took 7.62939453125e-06s
Interlinking | Calculation of Centrality for berlios took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for berlios took 8.082389831542969e-05s
Believability | Calculation of trust value for berlios took 1.0251998901367188e-05s
INFO | --- Analysis for berlios took 1.983041524887085s
Availability | SPARQL endpoint availability check for Between Our Worlds took 3.910064697265625e-05s
Availability | VoID file availability check for Between Our Worlds took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Between Our Worlds took 0.17918658256530762s
Reputation | Calculation of the PageRank for Between Our Worlds took 0.02024054527282715s
Interlinking | Calculation of Degree of Connection for Between Our Worlds took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Between Our Worlds took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Between Our Worlds took 6.127357482910156e-05s
Believability | Calculation of trust value for Between Our Worlds took 1.0251998901367188e-05s
INFO | --- Analysis for betweenourworlds took 1.9650976657867432s
Availability | SPARQL endpoint availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 4.5299530029296875e-05s
Availability | VoID file availability check for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.18281769752502441s
Reputation | Calculation of the PageRank for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.020831584930419922s
Interlinking | Calculation of Degree of Connection for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 8.487701416015625e-05s
Believability | Calculation of trust value for Bundesamt für Statistik (BFS) - Swiss Federal Statistical Office (FSO) Linked Data took 1.0728836059570312e-05s
INFO | --- Analysis for bfs-linked-data took 1.9756619930267334s
Availability | SPARQL endpoint availability check for BibBase took 8.153915405273438e-05s
Availability | VoID file availability check for BibBase took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for BibBase took 0.19896888732910156s
Reputation | Calculation of the PageRank for BibBase took 0.01992201805114746s
Interlinking | Calculation of Degree of Connection for BibBase took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for BibBase took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for BibBase took 8.940696716308594e-05s
Believability | Calculation of trust value for BibBase took 1.049041748046875e-05s
INFO | --- Analysis for bibbase took 2.0299854278564453s
Availability | SPARQL endpoint availability check for Biblioteca Escolar Digital CITA took 8.249282836914062e-05s
Availability | VoID file availability check for Biblioteca Escolar Digital CITA took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Biblioteca Escolar Digital CITA took 0.17820405960083008s
Reputation | Calculation of the PageRank for Biblioteca Escolar Digital CITA took 0.02103400230407715s
Interlinking | Calculation of Degree of Connection for Biblioteca Escolar Digital CITA took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Biblioteca Escolar Digital CITA took 0.0011031627655029297s
Interlinking | Calculation of Clustering coefficient for Biblioteca Escolar Digital CITA took 0.00011396408081054688s
Believability | Calculation of trust value for Biblioteca Escolar Digital CITA took 1.2636184692382812e-05s
INFO | --- Analysis for biblioteca-escolar-digital-cita took 1.9859721660614014s
Availability | SPARQL endpoint availability check for Biblioteca Nacional Escolar (BNEscolar) took 8.7738037109375e-05s
Availability | VoID file availability check for Biblioteca Nacional Escolar (BNEscolar) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Biblioteca Nacional Escolar (BNEscolar) took 0.1762709617614746s
Reputation | Calculation of the PageRank for Biblioteca Nacional Escolar (BNEscolar) took 0.020183563232421875s
Interlinking | Calculation of Degree of Connection for Biblioteca Nacional Escolar (BNEscolar) took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Biblioteca Nacional Escolar (BNEscolar) took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Biblioteca Nacional Escolar (BNEscolar) took 9.393692016601562e-05s
Believability | Calculation of trust value for Biblioteca Nacional Escolar (BNEscolar) took 1.049041748046875e-05s
INFO | --- Analysis for biblioteca-nacional-escolar-bnescolar took 2.002624988555908s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.933906555175781e-05s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.17976880073547363s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.020663976669311523s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 3.4332275390625e-05s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes (BVMC) - Linked Open Data took 8.106231689453125e-06s
INFO | --- Analysis for biblioteca-virtual-miguel-de-cervantes-bvmc-linked-open-data took 1.9685790538787842s
Availability | SPARQL endpoint availability check for BibSonomy - The blue social bookmark and publication sharing system. took 8.58306884765625e-05s
Availability | VoID file availability check for BibSonomy - The blue social bookmark and publication sharing system. took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for BibSonomy - The blue social bookmark and publication sharing system. took 0.1739518642425537s
Reputation | Calculation of the PageRank for BibSonomy - The blue social bookmark and publication sharing system. took 0.020168066024780273s
Interlinking | Calculation of Degree of Connection for BibSonomy - The blue social bookmark and publication sharing system. took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for BibSonomy - The blue social bookmark and publication sharing system. took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for BibSonomy - The blue social bookmark and publication sharing system. took 3.3855438232421875e-05s
Believability | Calculation of trust value for BibSonomy - The blue social bookmark and publication sharing system. took 1.1205673217773438e-05s
INFO | --- Analysis for BibSonomy took 2.0205330848693848s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2008 took 3.981590270996094e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2008 took 0.00020551681518554688s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2008 took 0.1774585247039795s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2008 took 0.019926071166992188s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2008 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2008 took 0.0006868839263916016s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2008 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2008 took 1.1205673217773438e-05s
INFO | --- Analysis for billion_triples_challenge_dataset2008 took 1.978773832321167s
Availability | SPARQL endpoint availability check for Billion Triples Challenge Dataset 2010 took 8.58306884765625e-05s
Availability | VoID file availability check for Billion Triples Challenge Dataset 2010 took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Billion Triples Challenge Dataset 2010 took 0.19053030014038086s
Reputation | Calculation of the PageRank for Billion Triples Challenge Dataset 2010 took 0.02214980125427246s
Interlinking | Calculation of Degree of Connection for Billion Triples Challenge Dataset 2010 took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Billion Triples Challenge Dataset 2010 took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Billion Triples Challenge Dataset 2010 took 2.8371810913085938e-05s
Believability | Calculation of trust value for Billion Triples Challenge Dataset 2010 took 1.0251998901367188e-05s
INFO | --- Analysis for billion_triples_challenge_dataset_2010 took 2.0454540252685547s
Availability | SPARQL endpoint availability check for Bio2RDF::ACFSID took 4.410743713378906e-05s
Availability | VoID file availability check for Bio2RDF::ACFSID took 0.00020551681518554688s
Completeness | Calculation of interlinking completeness for Bio2RDF::ACFSID took 0.1753392219543457s
Reputation | Calculation of the PageRank for Bio2RDF::ACFSID took 0.020085811614990234s
Interlinking | Calculation of Degree of Connection for Bio2RDF::ACFSID took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bio2RDF::ACFSID took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::ACFSID took 2.7418136596679688e-05s
Believability | Calculation of trust value for Bio2RDF::ACFSID took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-acfsid took 1.9872710704803467s
Availability | SPARQL endpoint availability check for Bio2RDF::Affymetrix took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Affymetrix took 0.0006339550018310547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Affymetrix took 0.21404075622558594s
Reputation | Calculation of the PageRank for Bio2RDF::Affymetrix took 0.02004718780517578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Affymetrix took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Affymetrix took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Affymetrix took 9.298324584960938e-05s
Believability | Calculation of trust value for Bio2RDF::Affymetrix took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-affymetrix took 2.0270256996154785s
Availability | SPARQL endpoint availability check for Bio2RDF::Biomodels took 8.368492126464844e-05s
Availability | VoID file availability check for Bio2RDF::Biomodels took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Biomodels took 0.18083667755126953s
Reputation | Calculation of the PageRank for Bio2RDF::Biomodels took 0.020006418228149414s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Biomodels took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Biomodels took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Biomodels took 0.00012731552124023438s
Believability | Calculation of trust value for Bio2RDF::Biomodels took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-biomodels took 2.00920033454895s
Availability | SPARQL endpoint availability check for Bio2RDF::BioModels::BioPAX took 3.981590270996094e-05s
Availability | VoID file availability check for Bio2RDF::BioModels::BioPAX took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Bio2RDF::BioModels::BioPAX took 0.17552661895751953s
Reputation | Calculation of the PageRank for Bio2RDF::BioModels::BioPAX took 0.020929336547851562s
Interlinking | Calculation of Degree of Connection for Bio2RDF::BioModels::BioPAX took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bio2RDF::BioModels::BioPAX took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::BioModels::BioPAX took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bio2RDF::BioModels::BioPAX took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-biomodels-biopax took 2.0403316020965576s
Availability | SPARQL endpoint availability check for Bio2RDF::Bioportal took 3.8623809814453125e-05s
Availability | VoID file availability check for Bio2RDF::Bioportal took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for Bio2RDF::Bioportal took 0.18353867530822754s
Reputation | Calculation of the PageRank for Bio2RDF::Bioportal took 0.02228236198425293s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Bioportal took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Bioportal took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Bioportal took 0.00041294097900390625s
Believability | Calculation of trust value for Bio2RDF::Bioportal took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-bioportal took 1.9695281982421875s
Availability | SPARQL endpoint availability check for Bio2RDF::Chembl took 8.392333984375e-05s
Availability | VoID file availability check for Bio2RDF::Chembl took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Chembl took 0.18731689453125s
Reputation | Calculation of the PageRank for Bio2RDF::Chembl took 0.021458864212036133s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Chembl took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Chembl took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Chembl took 5.984306335449219e-05s
Believability | Calculation of trust value for Bio2RDF::Chembl took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-chembl took 2.0025529861450195s
Availability | SPARQL endpoint availability check for Bio2RDF::Clinicaltrials took 8.058547973632812e-05s
Availability | VoID file availability check for Bio2RDF::Clinicaltrials took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for Bio2RDF::Clinicaltrials took 0.18097233772277832s
Reputation | Calculation of the PageRank for Bio2RDF::Clinicaltrials took 0.020111083984375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Clinicaltrials took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Clinicaltrials took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Clinicaltrials took 4.649162292480469e-05s
Believability | Calculation of trust value for Bio2RDF::Clinicaltrials took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-clinicaltrials took 1.992974042892456s
Availability | SPARQL endpoint availability check for Bio2RDF::Ctd took 8.296966552734375e-05s
Availability | VoID file availability check for Bio2RDF::Ctd took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ctd took 0.19610595703125s
Reputation | Calculation of the PageRank for Bio2RDF::Ctd took 0.02045297622680664s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ctd took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ctd took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ctd took 6.437301635742188e-05s
Believability | Calculation of trust value for Bio2RDF::Ctd took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-ctd took 2.0033602714538574s
Availability | SPARQL endpoint availability check for bio2rdf-dataset took 7.843971252441406e-05s
Availability | VoID file availability check for bio2rdf-dataset took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for bio2rdf-dataset took 0.18314433097839355s
Reputation | Calculation of the PageRank for bio2rdf-dataset took 0.02040553092956543s
Interlinking | Calculation of Degree of Connection for bio2rdf-dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for bio2rdf-dataset took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for bio2rdf-dataset took 4.7206878662109375e-05s
Believability | Calculation of trust value for bio2rdf-dataset took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-dataset took 1.9727463722229004s
Availability | SPARQL endpoint availability check for Bio2RDF::Dbsnp took 8.034706115722656e-05s
Availability | VoID file availability check for Bio2RDF::Dbsnp took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Bio2RDF::Dbsnp took 0.1827714443206787s
Reputation | Calculation of the PageRank for Bio2RDF::Dbsnp took 0.020343780517578125s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Dbsnp took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Dbsnp took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Dbsnp took 6.556510925292969e-05s
Believability | Calculation of trust value for Bio2RDF::Dbsnp took 1.0967254638671875e-05s
INFO | --- Analysis for bio2rdf-dbsnp took 1.9593489170074463s
Availability | SPARQL endpoint availability check for Bio2RDF::Drugbank took 7.891654968261719e-05s
Availability | VoID file availability check for Bio2RDF::Drugbank took 0.00022530555725097656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Drugbank took 0.179060697555542s
Reputation | Calculation of the PageRank for Bio2RDF::Drugbank took 0.0200192928314209s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Drugbank took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Drugbank took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Drugbank took 0.0001010894775390625s
Believability | Calculation of trust value for Bio2RDF::Drugbank took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-drugbank took 1.9745795726776123s
Availability | SPARQL endpoint availability check for Bio2RDF::Genage took 9.107589721679688e-05s
Availability | VoID file availability check for Bio2RDF::Genage took 0.00041675567626953125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Genage took 0.17905497550964355s
Reputation | Calculation of the PageRank for Bio2RDF::Genage took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Genage took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Genage took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Genage took 5.269050598144531e-05s
Believability | Calculation of trust value for Bio2RDF::Genage took 4.863739013671875e-05s
INFO | --- Analysis for bio2rdf-genage took 1.9690093994140625s
Availability | SPARQL endpoint availability check for Bio2RDF::GenBank took 8.177757263183594e-05s
Availability | VoID file availability check for Bio2RDF::GenBank took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Bio2RDF::GenBank took 0.17597484588623047s
Reputation | Calculation of the PageRank for Bio2RDF::GenBank took 0.02016448974609375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::GenBank took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bio2RDF::GenBank took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::GenBank took 5.698204040527344e-05s
Believability | Calculation of trust value for Bio2RDF::GenBank took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-genbank took 1.9834480285644531s
Availability | SPARQL endpoint availability check for Bio2RDF::Gendr took 3.910064697265625e-05s
Availability | VoID file availability check for Bio2RDF::Gendr took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Gendr took 0.18252038955688477s
Reputation | Calculation of the PageRank for Bio2RDF::Gendr took 0.020168781280517578s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Gendr took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Gendr took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Gendr took 5.0067901611328125e-05s
Believability | Calculation of trust value for Bio2RDF::Gendr took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-gendr took 1.990910530090332s
Availability | SPARQL endpoint availability check for Bio2RDF::Goa took 8.726119995117188e-05s
Availability | VoID file availability check for Bio2RDF::Goa took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Goa took 0.17851591110229492s
Reputation | Calculation of the PageRank for Bio2RDF::Goa took 0.020760536193847656s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Goa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Goa took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Goa took 6.008148193359375e-05s
Believability | Calculation of trust value for Bio2RDF::Goa took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-goa took 2.0298242568969727s
Availability | SPARQL endpoint availability check for Bio2RDF::Hgnc took 8.20159912109375e-05s
Availability | VoID file availability check for Bio2RDF::Hgnc took 0.0005576610565185547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Hgnc took 0.2946126461029053s
Reputation | Calculation of the PageRank for Bio2RDF::Hgnc took 0.02006220817565918s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Hgnc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Hgnc took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Hgnc took 0.00010657310485839844s
Believability | Calculation of trust value for Bio2RDF::Hgnc took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-hgnc took 2.138361930847168s
Availability | SPARQL endpoint availability check for Bio2RDF::Homologene took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Homologene took 0.0005497932434082031s
Completeness | Calculation of interlinking completeness for Bio2RDF::Homologene took 0.1802082061767578s
Reputation | Calculation of the PageRank for Bio2RDF::Homologene took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Homologene took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Homologene took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Homologene took 5.14984130859375e-05s
Believability | Calculation of trust value for Bio2RDF::Homologene took 1.0251998901367188e-05s
INFO | --- Analysis for bio2rdf-homologene took 1.9967305660247803s
Availability | SPARQL endpoint availability check for Bio2RDF::INOH took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::INOH took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Bio2RDF::INOH took 0.1885673999786377s
Reputation | Calculation of the PageRank for Bio2RDF::INOH took 0.020153522491455078s
Interlinking | Calculation of Degree of Connection for Bio2RDF::INOH took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::INOH took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::INOH took 3.0994415283203125e-05s
Believability | Calculation of trust value for Bio2RDF::INOH took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-inoh took 1.9589848518371582s
Availability | SPARQL endpoint availability check for Bio2RDF::Interpro took 8.153915405273438e-05s
Availability | VoID file availability check for Bio2RDF::Interpro took 0.00020837783813476562s
Completeness | Calculation of interlinking completeness for Bio2RDF::Interpro took 0.1812269687652588s
Reputation | Calculation of the PageRank for Bio2RDF::Interpro took 0.021025419235229492s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Interpro took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Interpro took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Interpro took 9.72747802734375e-05s
Believability | Calculation of trust value for Bio2RDF::Interpro took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-interpro took 1.9982578754425049s
Availability | SPARQL endpoint availability check for Bio2RDF::Iproclass took 8.273124694824219e-05s
Availability | VoID file availability check for Bio2RDF::Iproclass took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Iproclass took 0.1894972324371338s
Reputation | Calculation of the PageRank for Bio2RDF::Iproclass took 0.021289587020874023s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Iproclass took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Iproclass took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Iproclass took 7.748603820800781e-05s
Believability | Calculation of trust value for Bio2RDF::Iproclass took 1.33514404296875e-05s
INFO | --- Analysis for bio2rdf-iproclass took 1.979102373123169s
Availability | SPARQL endpoint availability check for Bio2RDF::Irefindex took 9.965896606445312e-05s
Availability | VoID file availability check for Bio2RDF::Irefindex took 0.0002033710479736328s
Completeness | Calculation of interlinking completeness for Bio2RDF::Irefindex took 0.17251944541931152s
Reputation | Calculation of the PageRank for Bio2RDF::Irefindex took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Irefindex took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Irefindex took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Irefindex took 7.891654968261719e-05s
Believability | Calculation of trust value for Bio2RDF::Irefindex took 9.5367431640625e-06s
INFO | --- Analysis for bio2rdf-irefindex took 2.015155553817749s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG took 8.58306884765625e-05s
Availability | VoID file availability check for Bio2RDF::KEGG took 0.0008997917175292969s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG took 0.18902039527893066s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG took 0.02093362808227539s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG took 6.580352783203125e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-kegg took 2.017310380935669s
Availability | SPARQL endpoint availability check for Bio2RDF::KEGG::BioPAX took 5.14984130859375e-05s
Availability | VoID file availability check for Bio2RDF::KEGG::BioPAX took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for Bio2RDF::KEGG::BioPAX took 0.18092751502990723s
Reputation | Calculation of the PageRank for Bio2RDF::KEGG::BioPAX took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for Bio2RDF::KEGG::BioPAX took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::KEGG::BioPAX took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::KEGG::BioPAX took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::KEGG::BioPAX took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-kegg-biopax took 1.9847588539123535s
Availability | SPARQL endpoint availability check for Bio2RDF::Linkedspl took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Linkedspl took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Bio2RDF::Linkedspl took 0.18128657341003418s
Reputation | Calculation of the PageRank for Bio2RDF::Linkedspl took 0.01988077163696289s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Linkedspl took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Linkedspl took 0.0006854534149169922s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Linkedspl took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::Linkedspl took 5.4836273193359375e-06s
INFO | --- Analysis for bio2rdf-linkedspl took 1.9645824432373047s
Availability | SPARQL endpoint availability check for Bio2RDF::Lsr took 4.291534423828125e-05s
Availability | VoID file availability check for Bio2RDF::Lsr took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Lsr took 0.17251086235046387s
Reputation | Calculation of the PageRank for Bio2RDF::Lsr took 0.02080988883972168s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Lsr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Lsr took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Lsr took 4.124641418457031e-05s
Believability | Calculation of trust value for Bio2RDF::Lsr took 5.4836273193359375e-06s
INFO | --- Analysis for bio2rdf-lsr took 1.9768171310424805s
Availability | SPARQL endpoint availability check for Bio2RDF::Mesh took 3.933906555175781e-05s
Availability | VoID file availability check for Bio2RDF::Mesh took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mesh took 0.18100547790527344s
Reputation | Calculation of the PageRank for Bio2RDF::Mesh took 0.02048635482788086s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mesh took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mesh took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mesh took 7.486343383789062e-05s
Believability | Calculation of trust value for Bio2RDF::Mesh took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-mesh took 1.950063705444336s
Availability | SPARQL endpoint availability check for Bio2RDF::Mgi took 9.679794311523438e-05s
Availability | VoID file availability check for Bio2RDF::Mgi took 0.000423431396484375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Mgi took 0.4220850467681885s
Reputation | Calculation of the PageRank for Bio2RDF::Mgi took 0.020164966583251953s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Mgi took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Mgi took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Mgi took 9.72747802734375e-05s
Believability | Calculation of trust value for Bio2RDF::Mgi took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-mgi took 2.229261636734009s
Availability | SPARQL endpoint availability check for Bio2RDF::Ncbigene took 8.034706115722656e-05s
Availability | VoID file availability check for Bio2RDF::Ncbigene took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ncbigene took 0.18533563613891602s
Reputation | Calculation of the PageRank for Bio2RDF::Ncbigene took 0.020191669464111328s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ncbigene took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ncbigene took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ncbigene took 0.0001347064971923828s
Believability | Calculation of trust value for Bio2RDF::Ncbigene took 1.1444091796875e-05s
INFO | --- Analysis for bio2rdf-ncbigene took 1.9743611812591553s
Availability | SPARQL endpoint availability check for Bio2RDF::Ndc took 5.53131103515625e-05s
Availability | VoID file availability check for Bio2RDF::Ndc took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Bio2RDF::Ndc took 0.1752779483795166s
Reputation | Calculation of the PageRank for Bio2RDF::Ndc took 0.020226478576660156s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Ndc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Ndc took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Ndc took 4.6253204345703125e-05s
Believability | Calculation of trust value for Bio2RDF::Ndc took 1.1205673217773438e-05s
INFO | --- Analysis for bio2rdf-ndc took 2.0202198028564453s
Availability | SPARQL endpoint availability check for Bio2RDF::NetPath took 4.076957702636719e-05s
Availability | VoID file availability check for Bio2RDF::NetPath took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for Bio2RDF::NetPath took 0.17346525192260742s
Reputation | Calculation of the PageRank for Bio2RDF::NetPath took 0.02017498016357422s
Interlinking | Calculation of Degree of Connection for Bio2RDF::NetPath took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::NetPath took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::NetPath took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bio2RDF::NetPath took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-netpath took 1.9759573936462402s
Availability | SPARQL endpoint availability check for Bio2RDF::neXtProt took 5.1975250244140625e-05s
Availability | VoID file availability check for Bio2RDF::neXtProt took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Bio2RDF::neXtProt took 0.17748498916625977s
Reputation | Calculation of the PageRank for Bio2RDF::neXtProt took 0.020171403884887695s
Interlinking | Calculation of Degree of Connection for Bio2RDF::neXtProt took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Bio2RDF::neXtProt took 0.0007262229919433594s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::neXtProt took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::neXtProt took 1.2874603271484375e-05s
INFO | --- Analysis for bio2rdf-nextprot took 1.9492976665496826s
Availability | SPARQL endpoint availability check for Bio2RDF::Omim took 8.630752563476562e-05s
Availability | VoID file availability check for Bio2RDF::Omim took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Omim took 0.17754411697387695s
Reputation | Calculation of the PageRank for Bio2RDF::Omim took 0.020461082458496094s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Omim took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Omim took 0.0007483959197998047s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Omim took 0.00012803077697753906s
Believability | Calculation of trust value for Bio2RDF::Omim took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-omim took 1.977238416671753s
Availability | SPARQL endpoint availability check for bio2rdf-omim-resources took 0.00011968612670898438s
Availability | VoID file availability check for bio2rdf-omim-resources took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for bio2rdf-omim-resources took 0.18306612968444824s
Reputation | Calculation of the PageRank for bio2rdf-omim-resources took 0.0209808349609375s
Interlinking | Calculation of Degree of Connection for bio2rdf-omim-resources took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for bio2rdf-omim-resources took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for bio2rdf-omim-resources took 4.220008850097656e-05s
Believability | Calculation of trust value for bio2rdf-omim-resources took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-omim-resources took 1.9622714519500732s
Availability | SPARQL endpoint availability check for Bio2RDF::Orphanet took 4.124641418457031e-05s
Availability | VoID file availability check for Bio2RDF::Orphanet took 0.00023627281188964844s
Completeness | Calculation of interlinking completeness for Bio2RDF::Orphanet took 0.171661376953125s
Reputation | Calculation of the PageRank for Bio2RDF::Orphanet took 0.0201568603515625s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Orphanet took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Orphanet took 0.0008935928344726562s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Orphanet took 8.606910705566406e-05s
Believability | Calculation of trust value for Bio2RDF::Orphanet took 7.3909759521484375e-06s
INFO | --- Analysis for bio2rdf-orphanet took 1.9566025733947754s
Availability | SPARQL endpoint availability check for Bio2RDF::Pathwaycommons took 4.220008850097656e-05s
Availability | VoID file availability check for Bio2RDF::Pathwaycommons took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pathwaycommons took 0.16835522651672363s
Reputation | Calculation of the PageRank for Bio2RDF::Pathwaycommons took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pathwaycommons took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Bio2RDF::Pathwaycommons took 0.0009119510650634766s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pathwaycommons took 3.5762786865234375e-05s
Believability | Calculation of trust value for Bio2RDF::Pathwaycommons took 6.9141387939453125e-06s
INFO | --- Analysis for bio2rdf-pathwaycommons took 1.9338161945343018s
Availability | SPARQL endpoint availability check for Bio2RDF::Pharmgkb took 8.177757263183594e-05s
Availability | VoID file availability check for Bio2RDF::Pharmgkb took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pharmgkb took 0.18052983283996582s
Reputation | Calculation of the PageRank for Bio2RDF::Pharmgkb took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pharmgkb took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pharmgkb took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pharmgkb took 6.842613220214844e-05s
Believability | Calculation of trust value for Bio2RDF::Pharmgkb took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-pharmgkb took 2.017716407775879s
Availability | SPARQL endpoint availability check for Bio2RDF::PharmGKB::BioPAX took 4.553794860839844e-05s
Availability | VoID file availability check for Bio2RDF::PharmGKB::BioPAX took 0.0004241466522216797s
Completeness | Calculation of interlinking completeness for Bio2RDF::PharmGKB::BioPAX took 0.2093508243560791s
Reputation | Calculation of the PageRank for Bio2RDF::PharmGKB::BioPAX took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PharmGKB::BioPAX took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PharmGKB::BioPAX took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PharmGKB::BioPAX took 3.123283386230469e-05s
Believability | Calculation of trust value for Bio2RDF::PharmGKB::BioPAX took 1.049041748046875e-05s
INFO | --- Analysis for bio2rdf-pharmgkb-biopax took 1.9993224143981934s
Availability | SPARQL endpoint availability check for Bio2RDF::PID took 3.9577484130859375e-05s
Availability | VoID file availability check for Bio2RDF::PID took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Bio2RDF::PID took 0.1740245819091797s
Reputation | Calculation of the PageRank for Bio2RDF::PID took 0.02123856544494629s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PID took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PID took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PID took 3.147125244140625e-05s
Believability | Calculation of trust value for Bio2RDF::PID took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-pid took 1.9612140655517578s
Availability | SPARQL endpoint availability check for Bio2RDF::PubChem took 7.915496826171875e-05s
Availability | VoID file availability check for Bio2RDF::PubChem took 0.00041174888610839844s
Completeness | Calculation of interlinking completeness for Bio2RDF::PubChem took 0.1901707649230957s
Reputation | Calculation of the PageRank for Bio2RDF::PubChem took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for Bio2RDF::PubChem took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bio2RDF::PubChem took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::PubChem took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::PubChem took 1.0013580322265625e-05s
INFO | --- Analysis for bio2rdf-pubchem-2 took 1.9804167747497559s
Availability | SPARQL endpoint availability check for Bio2RDF::Pubmed took 8.463859558105469e-05s
Availability | VoID file availability check for Bio2RDF::Pubmed took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Pubmed took 0.1780860424041748s
Reputation | Calculation of the PageRank for Bio2RDF::Pubmed took 0.02025604248046875s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Pubmed took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Pubmed took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Pubmed took 0.0001308917999267578s
Believability | Calculation of trust value for Bio2RDF::Pubmed took 1.0728836059570312e-05s
INFO | --- Analysis for bio2rdf-pubmed took 1.9665615558624268s
Availability | SPARQL endpoint availability check for Bio2RDF::Reactome took 8.296966552734375e-05s
Availability | VoID file availability check for Bio2RDF::Reactome took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Bio2RDF::Reactome took 0.18952703475952148s
Reputation | Calculation of the PageRank for Bio2RDF::Reactome took 0.020037174224853516s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Reactome took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Reactome took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Reactome took 6.67572021484375e-05s
Believability | Calculation of trust value for Bio2RDF::Reactome took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-reactome took 2.002532482147217s
Availability | SPARQL endpoint availability check for Bio2RDF::Rhea took 8.368492126464844e-05s
Availability | VoID file availability check for Bio2RDF::Rhea took 0.0002288818359375s
Completeness | Calculation of interlinking completeness for Bio2RDF::Rhea took 0.17532062530517578s
Reputation | Calculation of the PageRank for Bio2RDF::Rhea took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Rhea took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Rhea took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Rhea took 5.698204040527344e-05s
Believability | Calculation of trust value for Bio2RDF::Rhea took 6.198883056640625e-06s
INFO | --- Analysis for bio2rdf-rhea took 1.9600515365600586s
Availability | SPARQL endpoint availability check for Bio2RDF::Sabiork took 4.00543212890625e-05s
Availability | VoID file availability check for Bio2RDF::Sabiork took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sabiork took 0.18560028076171875s
Reputation | Calculation of the PageRank for Bio2RDF::Sabiork took 0.021077871322631836s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sabiork took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sabiork took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sabiork took 7.510185241699219e-05s
Believability | Calculation of trust value for Bio2RDF::Sabiork took 1.2159347534179688e-05s
INFO | --- Analysis for bio2rdf-sabiork took 1.9828135967254639s
Availability | SPARQL endpoint availability check for Bio2RDF::Sgd took 4.100799560546875e-05s
Availability | VoID file availability check for Bio2RDF::Sgd took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sgd took 0.1732025146484375s
Reputation | Calculation of the PageRank for Bio2RDF::Sgd took 0.020000696182250977s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sgd took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sgd took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sgd took 9.846687316894531e-05s
Believability | Calculation of trust value for Bio2RDF::Sgd took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-sgd took 2.0554816722869873s
Availability | SPARQL endpoint availability check for bio2rdf-sgd-resources took 3.981590270996094e-05s
Availability | VoID file availability check for bio2rdf-sgd-resources took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for bio2rdf-sgd-resources took 0.1761033535003662s
Reputation | Calculation of the PageRank for bio2rdf-sgd-resources took 0.019948482513427734s
Interlinking | Calculation of Degree of Connection for bio2rdf-sgd-resources took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for bio2rdf-sgd-resources took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for bio2rdf-sgd-resources took 3.2901763916015625e-05s
Believability | Calculation of trust value for bio2rdf-sgd-resources took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-sgd-resources took 1.990912914276123s
Availability | SPARQL endpoint availability check for Bio2RDF::Sider took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::Sider took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Bio2RDF::Sider took 0.18204998970031738s
Reputation | Calculation of the PageRank for Bio2RDF::Sider took 0.022818326950073242s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Sider took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Sider took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Sider took 3.6716461181640625e-05s
Believability | Calculation of trust value for Bio2RDF::Sider took 1.2636184692382812e-05s
INFO | --- Analysis for bio2rdf-sider took 2.002279281616211s
Availability | SPARQL endpoint availability check for Bio2RDF::SPIKE took 8.440017700195312e-05s
Availability | VoID file availability check for Bio2RDF::SPIKE took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for Bio2RDF::SPIKE took 0.18220806121826172s
Reputation | Calculation of the PageRank for Bio2RDF::SPIKE took 0.01995062828063965s
Interlinking | Calculation of Degree of Connection for Bio2RDF::SPIKE took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::SPIKE took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::SPIKE took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bio2RDF::SPIKE took 1.3113021850585938e-05s
INFO | --- Analysis for bio2rdf-spike took 2.0334110260009766s
Availability | SPARQL endpoint availability check for bio2rdf-taxon took 8.988380432128906e-05s
Availability | VoID file availability check for bio2rdf-taxon took 0.0005223751068115234s
Completeness | Calculation of interlinking completeness for bio2rdf-taxon took 0.1871781349182129s
Reputation | Calculation of the PageRank for bio2rdf-taxon took 0.019914865493774414s
Interlinking | Calculation of Degree of Connection for bio2rdf-taxon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for bio2rdf-taxon took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for bio2rdf-taxon took 4.0531158447265625e-05s
Believability | Calculation of trust value for bio2rdf-taxon took 1.239776611328125e-05s
INFO | --- Analysis for bio2rdf-taxon took 2.0010738372802734s
Availability | SPARQL endpoint availability check for Bio2RDF::Taxonomy took 3.838539123535156e-05s
Availability | VoID file availability check for Bio2RDF::Taxonomy took 0.00020194053649902344s
Completeness | Calculation of interlinking completeness for Bio2RDF::Taxonomy took 0.17554354667663574s
Reputation | Calculation of the PageRank for Bio2RDF::Taxonomy took 0.019918441772460938s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Taxonomy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Taxonomy took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Taxonomy took 9.417533874511719e-05s
Believability | Calculation of trust value for Bio2RDF::Taxonomy took 4.5299530029296875e-06s
INFO | --- Analysis for bio2rdf-taxonomy took 1.959562063217163s
Availability | SPARQL endpoint availability check for Bio2RDF::Wikipathways took 8.440017700195312e-05s
Availability | VoID file availability check for Bio2RDF::Wikipathways took 0.0005290508270263672s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wikipathways took 0.17890262603759766s
Reputation | Calculation of the PageRank for Bio2RDF::Wikipathways took 0.019954681396484375s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wikipathways took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Wikipathways took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wikipathways took 3.075599670410156e-05s
Believability | Calculation of trust value for Bio2RDF::Wikipathways took 1.1920928955078125e-05s
INFO | --- Analysis for bio2rdf-wikipathways took 2.002084493637085s
Availability | SPARQL endpoint availability check for Bio2RDF::Wormbase took 4.029273986816406e-05s
Availability | VoID file availability check for Bio2RDF::Wormbase took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Bio2RDF::Wormbase took 0.18617939949035645s
Reputation | Calculation of the PageRank for Bio2RDF::Wormbase took 0.019991636276245117s
Interlinking | Calculation of Degree of Connection for Bio2RDF::Wormbase took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bio2RDF::Wormbase took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Bio2RDF::Wormbase took 7.510185241699219e-05s
Believability | Calculation of trust value for Bio2RDF::Wormbase took 1.1682510375976562e-05s
INFO | --- Analysis for bio2rdf-wormbase took 2.0241756439208984s
Availability | SPARQL endpoint availability check for Biografías y Vidas took 8.606910705566406e-05s
Availability | VoID file availability check for Biografías y Vidas took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Biografías y Vidas took 0.1726233959197998s
Reputation | Calculation of the PageRank for Biografías y Vidas took 0.020027637481689453s
Interlinking | Calculation of Degree of Connection for Biografías y Vidas took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Biografías y Vidas took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Biografías y Vidas took 1.1444091796875e-05s
Believability | Calculation of trust value for Biografías y Vidas took 1.1920928955078125e-05s
INFO | --- Analysis for biografiasyvidas took 1.9912590980529785s
Availability | SPARQL endpoint availability check for Biographical Directory of the United States Congress took 3.9577484130859375e-05s
Availability | VoID file availability check for Biographical Directory of the United States Congress took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Biographical Directory of the United States Congress took 0.17691612243652344s
Reputation | Calculation of the PageRank for Biographical Directory of the United States Congress took 0.02012324333190918s
Interlinking | Calculation of Degree of Connection for Biographical Directory of the United States Congress took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Biographical Directory of the United States Congress took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Biographical Directory of the United States Congress took 7.748603820800781e-05s
Believability | Calculation of trust value for Biographical Directory of the United States Congress took 1.1920928955078125e-05s
INFO | --- Analysis for biographical-directory-of-the-united-states-congress took 1.9986615180969238s
Availability | SPARQL endpoint availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 8.535385131835938e-05s
Availability | VoID file availability check for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.17905330657958984s
Reputation | Calculation of the PageRank for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.022003173828125s
Interlinking | Calculation of Degree of Connection for A Short Biographical Dictionary of English Literature (RKBExplorer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for A Short Biographical Dictionary of English Literature (RKBExplorer) took 0.0007882118225097656s
Interlinking | Calculation of Clustering coefficient for A Short Biographical Dictionary of English Literature (RKBExplorer) took 3.123283386230469e-05s
Believability | Calculation of trust value for A Short Biographical Dictionary of English Literature (RKBExplorer) took 1.1444091796875e-05s
INFO | --- Analysis for biolit took 1.9678490161895752s
Availability | SPARQL endpoint availability check for BioLOD for Protein Data Bank Japan took 8.559226989746094e-05s
Availability | VoID file availability check for BioLOD for Protein Data Bank Japan took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for BioLOD for Protein Data Bank Japan took 0.18277478218078613s
Reputation | Calculation of the PageRank for BioLOD for Protein Data Bank Japan took 0.019960641860961914s
Interlinking | Calculation of Degree of Connection for BioLOD for Protein Data Bank Japan took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BioLOD for Protein Data Bank Japan took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for BioLOD for Protein Data Bank Japan took 3.790855407714844e-05s
Believability | Calculation of trust value for BioLOD for Protein Data Bank Japan took 1.1920928955078125e-05s
INFO | --- Analysis for biolod-pdb took 2.0291831493377686s
Availability | SPARQL endpoint availability check for BioModels RDF took 4.00543212890625e-05s
Availability | VoID file availability check for BioModels RDF took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for BioModels RDF took 0.18079328536987305s
Reputation | Calculation of the PageRank for BioModels RDF took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for BioModels RDF took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for BioModels RDF took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for BioModels RDF took 3.528594970703125e-05s
Believability | Calculation of trust value for BioModels RDF took 1.049041748046875e-05s
INFO | --- Analysis for biomodels-rdf took 1.9925811290740967s
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.0004756450653076172s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.17422699928283691s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 1.239776611328125e-05s
INFO | --- Analysis for Biop took 1.9957756996154785s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 9.775161743164062e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0002319812774658203s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.17130160331726074s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0215303897857666s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.4332275390625e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.811981201171875e-05s
INFO | --- Analysis for Bioportal took 1.9802799224853516s
Availability | SPARQL endpoint availability check for Amphibian gross anatomy took 5.14984130859375e-05s
Availability | VoID file availability check for Amphibian gross anatomy took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Amphibian gross anatomy took 0.18373560905456543s
Reputation | Calculation of the PageRank for Amphibian gross anatomy took 0.022933483123779297s
Interlinking | Calculation of Degree of Connection for Amphibian gross anatomy took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Amphibian gross anatomy took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for Amphibian gross anatomy took 0.0006220340728759766s
Believability | Calculation of trust value for Amphibian gross anatomy took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-aao took 2.0103838443756104s
Availability | SPARQL endpoint availability check for ABA Adult Mouse Brain took 8.916854858398438e-05s
Availability | VoID file availability check for ABA Adult Mouse Brain took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for ABA Adult Mouse Brain took 0.17619109153747559s
Reputation | Calculation of the PageRank for ABA Adult Mouse Brain took 0.021330833435058594s
Interlinking | Calculation of Degree of Connection for ABA Adult Mouse Brain took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ABA Adult Mouse Brain took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for ABA Adult Mouse Brain took 0.0002925395965576172s
Believability | Calculation of trust value for ABA Adult Mouse Brain took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-aba took 1.9916532039642334s
Availability | SPARQL endpoint availability check for Cancer Research and Management ACGT Master Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Cancer Research and Management ACGT Master Ontology took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Cancer Research and Management ACGT Master Ontology took 0.1801164150238037s
Reputation | Calculation of the PageRank for Cancer Research and Management ACGT Master Ontology took 0.022627592086791992s
Interlinking | Calculation of Degree of Connection for Cancer Research and Management ACGT Master Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Cancer Research and Management ACGT Master Ontology took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Cancer Research and Management ACGT Master Ontology took 0.0014946460723876953s
Believability | Calculation of trust value for Cancer Research and Management ACGT Master Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-acgt took 2.0005030632019043s
Availability | SPARQL endpoint availability check for Animal natural history and life history took 8.440017700195312e-05s
Availability | VoID file availability check for Animal natural history and life history took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Animal natural history and life history took 0.17365765571594238s
Reputation | Calculation of the PageRank for Animal natural history and life history took 0.020166397094726562s
Interlinking | Calculation of Degree of Connection for Animal natural history and life history took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Animal natural history and life history took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Animal natural history and life history took 0.00031256675720214844s
Believability | Calculation of trust value for Animal natural history and life history took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-adw took 1.9379563331604004s
Availability | SPARQL endpoint availability check for Anatomical Entity Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Anatomical Entity Ontology took 0.00023555755615234375s
Completeness | Calculation of interlinking completeness for Anatomical Entity Ontology took 0.18523764610290527s
Reputation | Calculation of the PageRank for Anatomical Entity Ontology took 0.02002882957458496s
Interlinking | Calculation of Degree of Connection for Anatomical Entity Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Anatomical Entity Ontology took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Anatomical Entity Ontology took 0.0004601478576660156s
Believability | Calculation of trust value for Anatomical Entity Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-aeo took 2.2725086212158203s
Availability | SPARQL endpoint availability check for Adverse Event Reporting ontology took 3.933906555175781e-05s
Availability | VoID file availability check for Adverse Event Reporting ontology took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Adverse Event Reporting ontology took 0.17563915252685547s
Reputation | Calculation of the PageRank for Adverse Event Reporting ontology took 0.021965742111206055s
Interlinking | Calculation of Degree of Connection for Adverse Event Reporting ontology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Adverse Event Reporting ontology took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Adverse Event Reporting ontology took 0.0010142326354980469s
Believability | Calculation of trust value for Adverse Event Reporting ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-aero took 1.9677801132202148s
Availability | SPARQL endpoint availability check for AI/RHEUM took 3.933906555175781e-05s
Availability | VoID file availability check for AI/RHEUM took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for AI/RHEUM took 0.17650794982910156s
Reputation | Calculation of the PageRank for AI/RHEUM took 0.020123720169067383s
Interlinking | Calculation of Degree of Connection for AI/RHEUM took 7.62939453125e-06s
Interlinking | Calculation of Centrality for AI/RHEUM took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for AI/RHEUM took 0.0003924369812011719s
Believability | Calculation of trust value for AI/RHEUM took 7.62939453125e-06s
INFO | --- Analysis for bioportal-air took 1.9944870471954346s
Availability | SPARQL endpoint availability check for Amino Acid took 4.0531158447265625e-05s
Availability | VoID file availability check for Amino Acid took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Amino Acid took 0.18002915382385254s
Reputation | Calculation of the PageRank for Amino Acid took 0.022090435028076172s
Interlinking | Calculation of Degree of Connection for Amino Acid took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Amino Acid took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Amino Acid took 0.0002880096435546875s
Believability | Calculation of trust value for Amino Acid took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-amino-acid took 1.9759643077850342s
Availability | SPARQL endpoint availability check for Ascomycete phenotype ontology took 9.34600830078125e-05s
Availability | VoID file availability check for Ascomycete phenotype ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Ascomycete phenotype ontology took 0.17791175842285156s
Reputation | Calculation of the PageRank for Ascomycete phenotype ontology took 0.020067453384399414s
Interlinking | Calculation of Degree of Connection for Ascomycete phenotype ontology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Ascomycete phenotype ontology took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Ascomycete phenotype ontology took 0.0002727508544921875s
Believability | Calculation of trust value for Ascomycete phenotype ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-apo took 2.021372079849243s
Availability | SPARQL endpoint availability check for African Traditional Medicine took 0.00011205673217773438s
Availability | VoID file availability check for African Traditional Medicine took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for African Traditional Medicine took 0.17427444458007812s
Reputation | Calculation of the PageRank for African Traditional Medicine took 0.020386934280395508s
Interlinking | Calculation of Degree of Connection for African Traditional Medicine took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for African Traditional Medicine took 0.0009276866912841797s
Interlinking | Calculation of Clustering coefficient for African Traditional Medicine took 0.00030112266540527344s
Believability | Calculation of trust value for African Traditional Medicine took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-atmo took 1.9908030033111572s
Availability | SPARQL endpoint availability check for Amphibian taxonomy took 8.368492126464844e-05s
Availability | VoID file availability check for Amphibian taxonomy took 0.0003833770751953125s
Completeness | Calculation of interlinking completeness for Amphibian taxonomy took 0.17405939102172852s
Reputation | Calculation of the PageRank for Amphibian taxonomy took 0.0219571590423584s
Interlinking | Calculation of Degree of Connection for Amphibian taxonomy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Amphibian taxonomy took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Amphibian taxonomy took 8.296966552734375e-05s
Believability | Calculation of trust value for Amphibian taxonomy took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ato took 2.011014938354492s
Availability | SPARQL endpoint availability check for BioAssay Ontology took 0.00010251998901367188s
Availability | VoID file availability check for BioAssay Ontology took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for BioAssay Ontology took 0.18154191970825195s
Reputation | Calculation of the PageRank for BioAssay Ontology took 0.020234107971191406s
Interlinking | Calculation of Degree of Connection for BioAssay Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for BioAssay Ontology took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for BioAssay Ontology took 0.0012903213500976562s
Believability | Calculation of trust value for BioAssay Ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-bao took 1.9986190795898438s
Availability | SPARQL endpoint availability check for Basic Vertebrate Anatomy took 3.981590270996094e-05s
Availability | VoID file availability check for Basic Vertebrate Anatomy took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Basic Vertebrate Anatomy took 0.16954565048217773s
Reputation | Calculation of the PageRank for Basic Vertebrate Anatomy took 0.021778345108032227s
Interlinking | Calculation of Degree of Connection for Basic Vertebrate Anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Basic Vertebrate Anatomy took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Basic Vertebrate Anatomy took 0.00036597251892089844s
Believability | Calculation of trust value for Basic Vertebrate Anatomy took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-basic-vertebrate-gross-anatomy took 1.9810326099395752s
Availability | SPARQL endpoint availability check for Breast Cancer Grading Ontology took 9.512901306152344e-05s
Availability | VoID file availability check for Breast Cancer Grading Ontology took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for Breast Cancer Grading Ontology took 0.18356609344482422s
Reputation | Calculation of the PageRank for Breast Cancer Grading Ontology took 0.020597457885742188s
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.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Breast Cancer Grading Ontology took 0.0003352165222167969s
Believability | Calculation of trust value for Breast Cancer Grading Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-bcgo took 1.983328104019165s
Availability | SPARQL endpoint availability check for Bone Dysplasia Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Bone Dysplasia Ontology took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Bone Dysplasia Ontology took 0.20770049095153809s
Reputation | Calculation of the PageRank for Bone Dysplasia Ontology took 0.020940303802490234s
Interlinking | Calculation of Degree of Connection for Bone Dysplasia Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Bone Dysplasia Ontology took 0.0006821155548095703s
Interlinking | Calculation of Clustering coefficient for Bone Dysplasia Ontology took 0.0014050006866455078s
Believability | Calculation of trust value for Bone Dysplasia Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-bdo took 2.0000338554382324s
Availability | SPARQL endpoint availability check for Basic Formal Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for Basic Formal Ontology took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for Basic Formal Ontology took 0.1862039566040039s
Reputation | Calculation of the PageRank for Basic Formal Ontology took 0.020007610321044922s
Interlinking | Calculation of Degree of Connection for Basic Formal Ontology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Basic Formal Ontology took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Basic Formal Ontology took 0.0004870891571044922s
Believability | Calculation of trust value for Basic Formal Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-bfo took 1.9822931289672852s
Availability | SPARQL endpoint availability check for Bleeding History Phenotype took 8.869171142578125e-05s
Availability | VoID file availability check for Bleeding History Phenotype took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Bleeding History Phenotype took 0.1828911304473877s
Reputation | Calculation of the PageRank for Bleeding History Phenotype took 0.020041942596435547s
Interlinking | Calculation of Degree of Connection for Bleeding History Phenotype took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bleeding History Phenotype took 0.0007879734039306641s
Interlinking | Calculation of Clustering coefficient for Bleeding History Phenotype took 0.0007243156433105469s
Believability | Calculation of trust value for Bleeding History Phenotype took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-bho took 2.0004451274871826s
Availability | SPARQL endpoint availability check for Bilateria anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Bilateria anatomy took 0.00024318695068359375s
Completeness | Calculation of interlinking completeness for Bilateria anatomy took 0.1821141242980957s
Reputation | Calculation of the PageRank for Bilateria anatomy took 0.019829511642456055s
Interlinking | Calculation of Degree of Connection for Bilateria anatomy took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Bilateria anatomy took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bilateria anatomy took 0.00042724609375s
Believability | Calculation of trust value for Bilateria anatomy took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-bila took 2.0189712047576904s
Availability | SPARQL endpoint availability check for BIRNLex took 5.173683166503906e-05s
Availability | VoID file availability check for BIRNLex took 0.0002620220184326172s
Completeness | Calculation of interlinking completeness for BIRNLex took 0.18231844902038574s
Reputation | Calculation of the PageRank for BIRNLex took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for BIRNLex took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for BIRNLex took 0.0006802082061767578s
Interlinking | Calculation of Clustering coefficient for BIRNLex took 0.001476287841796875s
Believability | Calculation of trust value for BIRNLex took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-birnlex took 1.9895827770233154s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.00024127960205078125s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.17469286918640137s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.02013373374938965s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007450580596923828s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-bootstrep took 1.942542552947998s
Availability | SPARQL endpoint availability check for BioPAX took 7.009506225585938e-05s
Availability | VoID file availability check for BioPAX took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for BioPAX took 0.17440533638000488s
Reputation | Calculation of the PageRank for BioPAX took 0.020757675170898438s
Interlinking | Calculation of Degree of Connection for BioPAX took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for BioPAX took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for BioPAX took 9.298324584960938e-05s
Believability | Calculation of trust value for BioPAX took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-bp took 2.009321689605713s
Availability | SPARQL endpoint availability check for Biomedical Resource Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Biomedical Resource Ontology took 0.00052642822265625s
Completeness | Calculation of interlinking completeness for Biomedical Resource Ontology took 0.18900585174560547s
Reputation | Calculation of the PageRank for Biomedical Resource Ontology took 0.020313501358032227s
Interlinking | Calculation of Degree of Connection for Biomedical Resource Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Biomedical Resource Ontology took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Biomedical Resource Ontology took 0.00033855438232421875s
Believability | Calculation of trust value for Biomedical Resource Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-bro_x1 took 1.961378574371338s
Availability | SPARQL endpoint availability check for Spatial Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Spatial Ontology took 0.0005259513854980469s
Completeness | Calculation of interlinking completeness for Spatial Ontology took 0.1878361701965332s
Reputation | Calculation of the PageRank for Spatial Ontology took 0.019895553588867188s
Interlinking | Calculation of Degree of Connection for Spatial Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Spatial Ontology took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Spatial Ontology took 0.0002009868621826172s
Believability | Calculation of trust value for Spatial Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-bspo took 1.9956798553466797s
Availability | SPARQL endpoint availability check for BioTop took 8.726119995117188e-05s
Availability | VoID file availability check for BioTop took 0.0002701282501220703s
Completeness | Calculation of interlinking completeness for BioTop took 0.17415833473205566s
Reputation | Calculation of the PageRank for BioTop took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for BioTop took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for BioTop took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for BioTop took 0.0006530284881591797s
Believability | Calculation of trust value for BioTop took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-bt took 2.020700693130493s
Availability | SPARQL endpoint availability check for BRENDA tissue / enzyme source took 8.702278137207031e-05s
Availability | VoID file availability check for BRENDA tissue / enzyme source took 0.0002422332763671875s
Completeness | Calculation of interlinking completeness for BRENDA tissue / enzyme source took 0.1729438304901123s
Reputation | Calculation of the PageRank for BRENDA tissue / enzyme source took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for BRENDA tissue / enzyme source took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for BRENDA tissue / enzyme source took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for BRENDA tissue / enzyme source took 0.0008988380432128906s
Believability | Calculation of trust value for BRENDA tissue / enzyme source took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-bto took 1.9780921936035156s
Availability | SPARQL endpoint availability check for Cancer Chemoprevention Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Cancer Chemoprevention Ontology took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Cancer Chemoprevention Ontology took 0.17385339736938477s
Reputation | Calculation of the PageRank for Cancer Chemoprevention Ontology took 0.020166635513305664s
Interlinking | Calculation of Degree of Connection for Cancer Chemoprevention Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cancer Chemoprevention Ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Cancer Chemoprevention Ontology took 0.0018687248229980469s
Believability | Calculation of trust value for Cancer Chemoprevention Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-canco took 1.9557580947875977s
Availability | SPARQL endpoint availability check for CAO took 8.511543273925781e-05s
Availability | VoID file availability check for CAO took 0.0005555152893066406s
Completeness | Calculation of interlinking completeness for CAO took 0.17308831214904785s
Reputation | Calculation of the PageRank for CAO took 0.02010321617126465s
Interlinking | Calculation of Degree of Connection for CAO took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for CAO took 0.0009455680847167969s
Interlinking | Calculation of Clustering coefficient for CAO took 0.0006601810455322266s
Believability | Calculation of trust value for CAO took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-cao took 1.973332405090332s
Availability | SPARQL endpoint availability check for CareLex took 4.100799560546875e-05s
Availability | VoID file availability check for CareLex took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for CareLex took 0.17432212829589844s
Reputation | Calculation of the PageRank for CareLex took 0.020295143127441406s
Interlinking | Calculation of Degree of Connection for CareLex took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for CareLex took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for CareLex took 4.696846008300781e-05s
Believability | Calculation of trust value for CareLex took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-carelex took 2.036904811859131s
Availability | SPARQL endpoint availability check for Cell Cycle Ontology took 0.0001163482666015625s
Availability | VoID file availability check for Cell Cycle Ontology took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Cell Cycle Ontology took 0.18057680130004883s
Reputation | Calculation of the PageRank for Cell Cycle Ontology took 0.020103931427001953s
Interlinking | Calculation of Degree of Connection for Cell Cycle Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Cell Cycle Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Cell Cycle Ontology took 0.0007843971252441406s
Believability | Calculation of trust value for Cell Cycle Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cco took 1.981438159942627s
Availability | SPARQL endpoint availability check for Comparative Data Analysis Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Comparative Data Analysis Ontology took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Comparative Data Analysis Ontology took 0.18668055534362793s
Reputation | Calculation of the PageRank for Comparative Data Analysis Ontology took 0.020051956176757812s
Interlinking | Calculation of Degree of Connection for Comparative Data Analysis Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Comparative Data Analysis Ontology took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Comparative Data Analysis Ontology took 0.0002486705780029297s
Believability | Calculation of trust value for Comparative Data Analysis Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-cdao took 1.9875550270080566s
Availability | SPARQL endpoint availability check for Chemical entities of biological interest took 8.7738037109375e-05s
Availability | VoID file availability check for Chemical entities of biological interest took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Chemical entities of biological interest took 0.17702054977416992s
Reputation | Calculation of the PageRank for Chemical entities of biological interest took 0.020317554473876953s
Interlinking | Calculation of Degree of Connection for Chemical entities of biological interest took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Chemical entities of biological interest took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Chemical entities of biological interest took 0.0007860660552978516s
Believability | Calculation of trust value for Chemical entities of biological interest took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-chebi took 1.9706473350524902s
Availability | SPARQL endpoint availability check for Systems Chemical Biology/Chemogenomics took 8.606910705566406e-05s
Availability | VoID file availability check for Systems Chemical Biology/Chemogenomics took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Systems Chemical Biology/Chemogenomics took 0.18686318397521973s
Reputation | Calculation of the PageRank for Systems Chemical Biology/Chemogenomics took 0.02011895179748535s
Interlinking | Calculation of Degree of Connection for Systems Chemical Biology/Chemogenomics took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Systems Chemical Biology/Chemogenomics took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Systems Chemical Biology/Chemogenomics took 0.0002586841583251953s
Believability | Calculation of trust value for Systems Chemical Biology/Chemogenomics took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-chem2bio2owl took 2.021346092224121s
Availability | SPARQL endpoint availability check for Chemical Information Ontology took 8.106231689453125e-05s
Availability | VoID file availability check for Chemical Information Ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Chemical Information Ontology took 0.19420719146728516s
Reputation | Calculation of the PageRank for Chemical Information Ontology took 0.019862890243530273s
Interlinking | Calculation of Degree of Connection for Chemical Information Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chemical Information Ontology took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Chemical Information Ontology took 0.0007462501525878906s
Believability | Calculation of trust value for Chemical Information Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-cheminf took 1.9650354385375977s
Availability | SPARQL endpoint availability check for Cell type took 4.100799560546875e-05s
Availability | VoID file availability check for Cell type took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for Cell type took 0.1883232593536377s
Reputation | Calculation of the PageRank for Cell type took 0.019960880279541016s
Interlinking | Calculation of Degree of Connection for Cell type took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell type took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Cell type took 0.00037026405334472656s
Believability | Calculation of trust value for Cell type took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-cl took 2.013306140899658s
Availability | SPARQL endpoint availability check for Cell Line Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Cell Line Ontology took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Cell Line Ontology took 0.1772470474243164s
Reputation | Calculation of the PageRank for Cell Line Ontology took 0.02019476890563965s
Interlinking | Calculation of Degree of Connection for Cell Line Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Cell Line Ontology took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Cell Line Ontology took 0.0008053779602050781s
Believability | Calculation of trust value for Cell Line Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-clo took 2.000192642211914s
Availability | SPARQL endpoint availability check for Clinical Measurement Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Clinical Measurement Ontology took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Clinical Measurement Ontology took 0.18208765983581543s
Reputation | Calculation of the PageRank for Clinical Measurement Ontology took 0.020087242126464844s
Interlinking | Calculation of Degree of Connection for Clinical Measurement Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Clinical Measurement Ontology took 0.0007503032684326172s
Interlinking | Calculation of Clustering coefficient for Clinical Measurement Ontology took 0.00017070770263671875s
Believability | Calculation of trust value for Clinical Measurement Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-cmo took 2.06846284866333s
Availability | SPARQL endpoint availability check for Computational Neuroscience Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Computational Neuroscience Ontology took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Computational Neuroscience Ontology took 0.18178606033325195s
Reputation | Calculation of the PageRank for Computational Neuroscience Ontology took 0.020021915435791016s
Interlinking | Calculation of Degree of Connection for Computational Neuroscience Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Computational Neuroscience Ontology took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Computational Neuroscience Ontology took 0.00021600723266601562s
Believability | Calculation of trust value for Computational Neuroscience Ontology took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-cno took 1.9704887866973877s
Availability | SPARQL endpoint availability check for Wheat trait took 4.100799560546875e-05s
Availability | VoID file availability check for Wheat trait took 0.0005257129669189453s
Completeness | Calculation of interlinking completeness for Wheat trait took 0.17861461639404297s
Reputation | Calculation of the PageRank for Wheat trait took 0.019971132278442383s
Interlinking | Calculation of Degree of Connection for Wheat trait took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Wheat trait took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Wheat trait took 4.982948303222656e-05s
Believability | Calculation of trust value for Wheat trait took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-co_wheat took 2.0188863277435303s
Availability | SPARQL endpoint availability check for Cognitive Atlas took 3.981590270996094e-05s
Availability | VoID file availability check for Cognitive Atlas took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Cognitive Atlas took 0.18218064308166504s
Reputation | Calculation of the PageRank for Cognitive Atlas took 0.019902706146240234s
Interlinking | Calculation of Degree of Connection for Cognitive Atlas took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Cognitive Atlas took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Cognitive Atlas took 0.0003399848937988281s
Believability | Calculation of trust value for Cognitive Atlas took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-cogat took 2.000706195831299s
Availability | SPARQL endpoint availability check for Cognitive Paradigm Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Cognitive Paradigm Ontology took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Cognitive Paradigm Ontology took 0.18865060806274414s
Reputation | Calculation of the PageRank for Cognitive Paradigm Ontology took 0.020081520080566406s
Interlinking | Calculation of Degree of Connection for Cognitive Paradigm Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cognitive Paradigm Ontology took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Cognitive Paradigm Ontology took 0.0007455348968505859s
Believability | Calculation of trust value for Cognitive Paradigm Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-cogpo took 1.965991735458374s
Availability | SPARQL endpoint availability check for Current Procedural Terminology took 8.392333984375e-05s
Availability | VoID file availability check for Current Procedural Terminology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Current Procedural Terminology took 0.18611717224121094s
Reputation | Calculation of the PageRank for Current Procedural Terminology took 0.01996636390686035s
Interlinking | Calculation of Degree of Connection for Current Procedural Terminology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Current Procedural Terminology took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Current Procedural Terminology took 0.0004086494445800781s
Believability | Calculation of trust value for Current Procedural Terminology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-cpt took 1.9635803699493408s
Availability | SPARQL endpoint availability check for CRISP Thesaurus, 2006 took 8.893013000488281e-05s
Availability | VoID file availability check for CRISP Thesaurus, 2006 took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for CRISP Thesaurus, 2006 took 0.18273115158081055s
Reputation | Calculation of the PageRank for CRISP Thesaurus, 2006 took 0.02031111717224121s
Interlinking | Calculation of Degree of Connection for CRISP Thesaurus, 2006 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CRISP Thesaurus, 2006 took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for CRISP Thesaurus, 2006 took 0.0017981529235839844s
Believability | Calculation of trust value for CRISP Thesaurus, 2006 took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-csp took 1.9997830390930176s
Availability | SPARQL endpoint availability check for COSTART took 8.678436279296875e-05s
Availability | VoID file availability check for COSTART took 0.0002498626708984375s
Completeness | Calculation of interlinking completeness for COSTART took 0.175614595413208s
Reputation | Calculation of the PageRank for COSTART took 0.019987821578979492s
Interlinking | Calculation of Degree of Connection for COSTART took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for COSTART took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for COSTART took 0.0009622573852539062s
Believability | Calculation of trust value for COSTART took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-cst took 2.074580192565918s
Availability | SPARQL endpoint availability check for Common Terminology Criteria for Adverse Events took 8.487701416015625e-05s
Availability | VoID file availability check for Common Terminology Criteria for Adverse Events took 0.0005085468292236328s
Completeness | Calculation of interlinking completeness for Common Terminology Criteria for Adverse Events took 0.18330788612365723s
Reputation | Calculation of the PageRank for Common Terminology Criteria for Adverse Events took 0.020307540893554688s
Interlinking | Calculation of Degree of Connection for Common Terminology Criteria for Adverse Events took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Common Terminology Criteria for Adverse Events took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Common Terminology Criteria for Adverse Events took 0.0004987716674804688s
Believability | Calculation of trust value for Common Terminology Criteria for Adverse Events took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ctcae took 2.001408338546753s
Availability | SPARQL endpoint availability check for Cerebrotendinous xanthomatosis took 4.0531158447265625e-05s
Availability | VoID file availability check for Cerebrotendinous xanthomatosis took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Cerebrotendinous xanthomatosis took 0.1773064136505127s
Reputation | Calculation of the PageRank for Cerebrotendinous xanthomatosis took 0.022505998611450195s
Interlinking | Calculation of Degree of Connection for Cerebrotendinous xanthomatosis took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cerebrotendinous xanthomatosis took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for Cerebrotendinous xanthomatosis took 0.0004448890686035156s
Believability | Calculation of trust value for Cerebrotendinous xanthomatosis took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ctx took 2.0187125205993652s
Availability | SPARQL endpoint availability check for Dendritic cell took 8.368492126464844e-05s
Availability | VoID file availability check for Dendritic cell took 0.0006084442138671875s
Completeness | Calculation of interlinking completeness for Dendritic cell took 0.1752772331237793s
Reputation | Calculation of the PageRank for Dendritic cell took 0.020267248153686523s
Interlinking | Calculation of Degree of Connection for Dendritic cell took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Dendritic cell took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Dendritic cell took 0.00031113624572753906s
Believability | Calculation of trust value for Dendritic cell took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-dc_cl took 2.007070779800415s
Availability | SPARQL endpoint availability check for Dictyostelium discoideum anatomy took 8.58306884765625e-05s
Availability | VoID file availability check for Dictyostelium discoideum anatomy took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Dictyostelium discoideum anatomy took 0.17366790771484375s
Reputation | Calculation of the PageRank for Dictyostelium discoideum anatomy took 0.020532608032226562s
Interlinking | Calculation of Degree of Connection for Dictyostelium discoideum anatomy took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Dictyostelium discoideum anatomy took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for Dictyostelium discoideum anatomy took 8.296966552734375e-05s
Believability | Calculation of trust value for Dictyostelium discoideum anatomy took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ddanat took 2.01082181930542s
Availability | SPARQL endpoint availability check for Ontology for Drug Discovery Investigations took 0.00010132789611816406s
Availability | VoID file availability check for Ontology for Drug Discovery Investigations took 0.0005292892456054688s
Completeness | Calculation of interlinking completeness for Ontology for Drug Discovery Investigations took 0.18752479553222656s
Reputation | Calculation of the PageRank for Ontology for Drug Discovery Investigations took 0.020374298095703125s
Interlinking | Calculation of Degree of Connection for Ontology for Drug Discovery Investigations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for Drug Discovery Investigations took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for Ontology for Drug Discovery Investigations took 0.0009212493896484375s
Believability | Calculation of trust value for Ontology for Drug Discovery Investigations took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ddi took 2.007571220397949s
Availability | SPARQL endpoint availability check for Diagnostic Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Diagnostic Ontology took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Diagnostic Ontology took 0.17858409881591797s
Reputation | Calculation of the PageRank for Diagnostic Ontology took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for Diagnostic Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Diagnostic Ontology took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Diagnostic Ontology took 8.249282836914062e-05s
Believability | Calculation of trust value for Diagnostic Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-diagnosticont took 1.9958240985870361s
Availability | SPARQL endpoint availability check for DIKB-Evidence-Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for DIKB-Evidence-Ontology took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for DIKB-Evidence-Ontology took 0.17970514297485352s
Reputation | Calculation of the PageRank for DIKB-Evidence-Ontology took 0.01997828483581543s
Interlinking | Calculation of Degree of Connection for DIKB-Evidence-Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DIKB-Evidence-Ontology took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for DIKB-Evidence-Ontology took 0.0001556873321533203s
Believability | Calculation of trust value for DIKB-Evidence-Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-dikb-evidence took 2.0023016929626465s
Availability | SPARQL endpoint availability check for Human disease ontology took 5.2928924560546875e-05s
Availability | VoID file availability check for Human disease ontology took 0.0005114078521728516s
Completeness | Calculation of interlinking completeness for Human disease ontology took 0.17686963081359863s
Reputation | Calculation of the PageRank for Human disease ontology took 0.01999950408935547s
Interlinking | Calculation of Degree of Connection for Human disease ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Human disease ontology took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Human disease ontology took 0.0006487369537353516s
Believability | Calculation of trust value for Human disease ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-doid took 2.0333080291748047s
Availability | SPARQL endpoint availability check for Electrocardiography Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Electrocardiography Ontology took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Electrocardiography Ontology took 0.18282508850097656s
Reputation | Calculation of the PageRank for Electrocardiography Ontology took 0.020133256912231445s
Interlinking | Calculation of Degree of Connection for Electrocardiography Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Electrocardiography Ontology took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Electrocardiography Ontology took 0.0008075237274169922s
Believability | Calculation of trust value for Electrocardiography Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-ecg took 2.022430896759033s
Availability | SPARQL endpoint availability check for Evidence codes took 0.00011086463928222656s
Availability | VoID file availability check for Evidence codes took 0.0005550384521484375s
Completeness | Calculation of interlinking completeness for Evidence codes took 0.18107867240905762s
Reputation | Calculation of the PageRank for Evidence codes took 0.021607398986816406s
Interlinking | Calculation of Degree of Connection for Evidence codes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Evidence codes took 0.0007750988006591797s
Interlinking | Calculation of Clustering coefficient for Evidence codes took 3.1948089599609375e-05s
Believability | Calculation of trust value for Evidence codes took 1.4066696166992188e-05s
INFO | --- Analysis for bioportal-eco took 2.0378615856170654s
Availability | SPARQL endpoint availability check for Experimental Factor Ontology took 4.124641418457031e-05s
Availability | VoID file availability check for Experimental Factor Ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Experimental Factor Ontology took 0.18107342720031738s
Reputation | Calculation of the PageRank for Experimental Factor Ontology took 0.021301746368408203s
Interlinking | Calculation of Degree of Connection for Experimental Factor Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Experimental Factor Ontology took 0.0007424354553222656s
Interlinking | Calculation of Clustering coefficient for Experimental Factor Ontology took 0.0017518997192382812s
Believability | Calculation of trust value for Experimental Factor Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-efo took 2.018604040145874s
Availability | SPARQL endpoint availability check for Human developmental anatomy, timed version took 8.7738037109375e-05s
Availability | VoID file availability check for Human developmental anatomy, timed version took 0.0005228519439697266s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, timed version took 0.18937253952026367s
Reputation | Calculation of the PageRank for Human developmental anatomy, timed version took 0.023996829986572266s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, timed version took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Human developmental anatomy, timed version took 0.0009233951568603516s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, timed version took 0.0015566349029541016s
Believability | Calculation of trust value for Human developmental anatomy, timed version took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ehda took 2.006742238998413s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version took 8.559226989746094e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version took 0.0005543231964111328s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version took 0.18099427223205566s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version took 0.02088308334350586s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version took 0.0007445812225341797s
Believability | Calculation of trust value for Human developmental anatomy, abstract version took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ehdaa took 2.0621755123138428s
Availability | SPARQL endpoint availability check for Human developmental anatomy, abstract version, v2 took 4.220008850097656e-05s
Availability | VoID file availability check for Human developmental anatomy, abstract version, v2 took 0.0005009174346923828s
Completeness | Calculation of interlinking completeness for Human developmental anatomy, abstract version, v2 took 0.17887353897094727s
Reputation | Calculation of the PageRank for Human developmental anatomy, abstract version, v2 took 0.019967079162597656s
Interlinking | Calculation of Degree of Connection for Human developmental anatomy, abstract version, v2 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Human developmental anatomy, abstract version, v2 took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Human developmental anatomy, abstract version, v2 took 0.0005283355712890625s
Believability | Calculation of trust value for Human developmental anatomy, abstract version, v2 took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ehdaa2 took 2.0498368740081787s
Availability | SPARQL endpoint availability check for Mouse gross anatomy and development took 4.0531158447265625e-05s
Availability | VoID file availability check for Mouse gross anatomy and development took 0.0006127357482910156s
Completeness | Calculation of interlinking completeness for Mouse gross anatomy and development took 0.18200373649597168s
Reputation | Calculation of the PageRank for Mouse gross anatomy and development took 0.02017354965209961s
Interlinking | Calculation of Degree of Connection for Mouse gross anatomy and development took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Mouse gross anatomy and development took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Mouse gross anatomy and development took 3.0040740966796875e-05s
Believability | Calculation of trust value for Mouse gross anatomy and development took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-emap took 1.9750785827636719s
Availability | SPARQL endpoint availability check for Environment Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for Environment Ontology took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for Environment Ontology took 0.1864469051361084s
Reputation | Calculation of the PageRank for Environment Ontology took 0.02003026008605957s
Interlinking | Calculation of Degree of Connection for Environment Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Environment Ontology took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Environment Ontology took 0.0003898143768310547s
Believability | Calculation of trust value for Environment Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-envo took 1.9639089107513428s
Availability | SPARQL endpoint availability check for Plant environmental conditions took 0.0001342296600341797s
Availability | VoID file availability check for Plant environmental conditions took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Plant environmental conditions took 0.18450236320495605s
Reputation | Calculation of the PageRank for Plant environmental conditions took 0.020235776901245117s
Interlinking | Calculation of Degree of Connection for Plant environmental conditions took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Plant environmental conditions took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Plant environmental conditions took 0.00028634071350097656s
Believability | Calculation of trust value for Plant environmental conditions took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-eo took 1.9732730388641357s
Availability | SPARQL endpoint availability check for Cardiac Electrophysiology Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Cardiac Electrophysiology Ontology took 0.0005512237548828125s
Completeness | Calculation of interlinking completeness for Cardiac Electrophysiology Ontology took 0.18560457229614258s
Reputation | Calculation of the PageRank for Cardiac Electrophysiology Ontology took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Cardiac Electrophysiology Ontology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Cardiac Electrophysiology Ontology took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Cardiac Electrophysiology Ontology took 0.00119781494140625s
Believability | Calculation of trust value for Cardiac Electrophysiology Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ep took 2.013115167617798s
Availability | SPARQL endpoint availability check for Epilepsy took 4.100799560546875e-05s
Availability | VoID file availability check for Epilepsy took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Epilepsy took 0.17595601081848145s
Reputation | Calculation of the PageRank for Epilepsy took 0.020516157150268555s
Interlinking | Calculation of Degree of Connection for Epilepsy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Epilepsy took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Epilepsy took 0.0001285076141357422s
Believability | Calculation of trust value for Epilepsy took 7.62939453125e-06s
INFO | --- Analysis for bioportal-epileponto took 2.001528739929199s
Availability | SPARQL endpoint availability check for eagle-i research resource ontology took 4.172325134277344e-05s
Availability | VoID file availability check for eagle-i research resource ontology took 0.000518798828125s
Completeness | Calculation of interlinking completeness for eagle-i research resource ontology took 0.17392230033874512s
Reputation | Calculation of the PageRank for eagle-i research resource ontology took 0.02015209197998047s
Interlinking | Calculation of Degree of Connection for eagle-i research resource ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i research resource ontology took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for eagle-i research resource ontology took 0.0011548995971679688s
Believability | Calculation of trust value for eagle-i research resource ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-ero took 1.9665932655334473s
Availability | SPARQL endpoint availability check for eVOC (Expressed Sequence Annotation for Humans) took 9.012222290039062e-05s
Availability | VoID file availability check for eVOC (Expressed Sequence Annotation for Humans) took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for eVOC (Expressed Sequence Annotation for Humans) took 0.17796921730041504s
Reputation | Calculation of the PageRank for eVOC (Expressed Sequence Annotation for Humans) took 0.02227020263671875s
Interlinking | Calculation of Degree of Connection for eVOC (Expressed Sequence Annotation for Humans) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for eVOC (Expressed Sequence Annotation for Humans) took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for eVOC (Expressed Sequence Annotation for Humans) took 0.0011055469512939453s
Believability | Calculation of trust value for eVOC (Expressed Sequence Annotation for Humans) took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ev took 1.9710149765014648s
Availability | SPARQL endpoint availability check for ExO took 8.487701416015625e-05s
Availability | VoID file availability check for ExO took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for ExO took 0.17502379417419434s
Reputation | Calculation of the PageRank for ExO took 0.020146608352661133s
Interlinking | Calculation of Degree of Connection for ExO took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for ExO took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for ExO took 0.00023698806762695312s
Believability | Calculation of trust value for ExO took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-exo took 2.080519914627075s
Availability | SPARQL endpoint availability check for Fungal gross anatomy took 8.58306884765625e-05s
Availability | VoID file availability check for Fungal gross anatomy took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Fungal gross anatomy took 0.1759018898010254s
Reputation | Calculation of the PageRank for Fungal gross anatomy took 0.020896434783935547s
Interlinking | Calculation of Degree of Connection for Fungal gross anatomy took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Fungal gross anatomy took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Fungal gross anatomy took 0.00010895729064941406s
Believability | Calculation of trust value for Fungal gross anatomy took 8.344650268554688e-06s
INFO | --- Analysis for bioportal-fao took 1.9747214317321777s
Availability | SPARQL endpoint availability check for Biological imaging methods took 4.482269287109375e-05s
Availability | VoID file availability check for Biological imaging methods took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Biological imaging methods took 0.18406033515930176s
Reputation | Calculation of the PageRank for Biological imaging methods took 0.020853757858276367s
Interlinking | Calculation of Degree of Connection for Biological imaging methods took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Biological imaging methods took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Biological imaging methods took 0.00019979476928710938s
Believability | Calculation of trust value for Biological imaging methods took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-fbbi took 1.9997637271881104s
Availability | SPARQL endpoint availability check for Drosophila gross anatomy took 8.106231689453125e-05s
Availability | VoID file availability check for Drosophila gross anatomy took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Drosophila gross anatomy took 0.18529009819030762s
Reputation | Calculation of the PageRank for Drosophila gross anatomy took 0.021465778350830078s
Interlinking | Calculation of Degree of Connection for Drosophila gross anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Drosophila gross anatomy took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Drosophila gross anatomy took 0.0006167888641357422s
Believability | Calculation of trust value for Drosophila gross anatomy took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-fbbt took 2.0408408641815186s
Availability | SPARQL endpoint availability check for FlyBase Controlled Vocabulary took 8.273124694824219e-05s
Availability | VoID file availability check for FlyBase Controlled Vocabulary took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for FlyBase Controlled Vocabulary took 0.1908714771270752s
Reputation | Calculation of the PageRank for FlyBase Controlled Vocabulary took 0.020326852798461914s
Interlinking | Calculation of Degree of Connection for FlyBase Controlled Vocabulary took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for FlyBase Controlled Vocabulary took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for FlyBase Controlled Vocabulary took 0.0004019737243652344s
Believability | Calculation of trust value for FlyBase Controlled Vocabulary took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-fbcv took 1.9811935424804688s
Availability | SPARQL endpoint availability check for Drosophila development took 8.082389831542969e-05s
Availability | VoID file availability check for Drosophila development took 0.00020933151245117188s
Completeness | Calculation of interlinking completeness for Drosophila development took 0.18024086952209473s
Reputation | Calculation of the PageRank for Drosophila development took 0.02134418487548828s
Interlinking | Calculation of Degree of Connection for Drosophila development took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Drosophila development took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for Drosophila development took 4.506111145019531e-05s
Believability | Calculation of trust value for Drosophila development took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-fbdv took 1.979271650314331s
Availability | SPARQL endpoint availability check for Fly taxonomy took 4.172325134277344e-05s
Availability | VoID file availability check for Fly taxonomy took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Fly taxonomy took 0.18207907676696777s
Reputation | Calculation of the PageRank for Fly taxonomy took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for Fly taxonomy took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fly taxonomy took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Fly taxonomy took 0.0003571510314941406s
Believability | Calculation of trust value for Fly taxonomy took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-fbsp took 1.9823558330535889s
Availability | SPARQL endpoint availability check for FDA Medical Devices (2010) took 8.392333984375e-05s
Availability | VoID file availability check for FDA Medical Devices (2010) took 0.00020599365234375s
Completeness | Calculation of interlinking completeness for FDA Medical Devices (2010) took 0.17949533462524414s
Reputation | Calculation of the PageRank for FDA Medical Devices (2010) took 0.021288394927978516s
Interlinking | Calculation of Degree of Connection for FDA Medical Devices (2010) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FDA Medical Devices (2010) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for FDA Medical Devices (2010) took 0.00021505355834960938s
Believability | Calculation of trust value for FDA Medical Devices (2010) took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-fda-meddevice took 1.9987499713897705s
Availability | SPARQL endpoint availability check for Family Health History Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Family Health History Ontology took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Family Health History Ontology took 0.17702865600585938s
Reputation | Calculation of the PageRank for Family Health History Ontology took 0.021603822708129883s
Interlinking | Calculation of Degree of Connection for Family Health History Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Family Health History Ontology took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Family Health History Ontology took 0.0004019737243652344s
Believability | Calculation of trust value for Family Health History Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-fhho took 1.9655933380126953s
Availability | SPARQL endpoint availability check for Influenza Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Influenza Ontology took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Influenza Ontology took 0.1868431568145752s
Reputation | Calculation of the PageRank for Influenza Ontology took 0.020140647888183594s
Interlinking | Calculation of Degree of Connection for Influenza Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Influenza Ontology took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Influenza Ontology took 0.0009992122650146484s
Believability | Calculation of trust value for Influenza Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-flu took 2.015120267868042s
Availability | SPARQL endpoint availability check for Foundational Model of Anatomy took 8.20159912109375e-05s
Availability | VoID file availability check for Foundational Model of Anatomy took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Foundational Model of Anatomy took 0.18143749237060547s
Reputation | Calculation of the PageRank for Foundational Model of Anatomy took 0.02008199691772461s
Interlinking | Calculation of Degree of Connection for Foundational Model of Anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Foundational Model of Anatomy took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Foundational Model of Anatomy took 6.0558319091796875e-05s
Believability | Calculation of trust value for Foundational Model of Anatomy took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-fma took 1.9701499938964844s
Availability | SPARQL endpoint availability check for Fission Yeast Phenotype Ontology took 8.0108642578125e-05s
Availability | VoID file availability check for Fission Yeast Phenotype Ontology took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Fission Yeast Phenotype Ontology took 0.1786515712738037s
Reputation | Calculation of the PageRank for Fission Yeast Phenotype Ontology took 0.020249128341674805s
Interlinking | Calculation of Degree of Connection for Fission Yeast Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Fission Yeast Phenotype Ontology took 0.0006873607635498047s
Interlinking | Calculation of Clustering coefficient for Fission Yeast Phenotype Ontology took 0.00012540817260742188s
Believability | Calculation of trust value for Fission Yeast Phenotype Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-fypo took 1.988069772720337s
Availability | SPARQL endpoint availability check for GeoSpecies Ontology took 8.130073547363281e-05s
Availability | VoID file availability check for GeoSpecies Ontology took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for GeoSpecies Ontology took 0.18424224853515625s
Reputation | Calculation of the PageRank for GeoSpecies Ontology took 0.0202939510345459s
Interlinking | Calculation of Degree of Connection for GeoSpecies Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for GeoSpecies Ontology took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Ontology took 8.654594421386719e-05s
Believability | Calculation of trust value for GeoSpecies Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-geospecies took 1.969860315322876s
Availability | SPARQL endpoint availability check for General Formal Ontology took 5.7697296142578125e-05s
Availability | VoID file availability check for General Formal Ontology took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for General Formal Ontology took 0.17522120475769043s
Reputation | Calculation of the PageRank for General Formal Ontology took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for General Formal Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for General Formal Ontology took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology took 0.0001857280731201172s
Believability | Calculation of trust value for General Formal Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-gfo took 1.9646828174591064s
Availability | SPARQL endpoint availability check for General Formal Ontology: Biology took 3.8623809814453125e-05s
Availability | VoID file availability check for General Formal Ontology: Biology took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for General Formal Ontology: Biology took 0.16797542572021484s
Reputation | Calculation of the PageRank for General Formal Ontology: Biology took 0.020382404327392578s
Interlinking | Calculation of Degree of Connection for General Formal Ontology: Biology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for General Formal Ontology: Biology took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for General Formal Ontology: Biology took 0.000579833984375s
Believability | Calculation of trust value for General Formal Ontology: Biology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-gfo-bio took 1.977402925491333s
Availability | SPARQL endpoint availability check for Gene Ontology Extension took 8.249282836914062e-05s
Availability | VoID file availability check for Gene Ontology Extension took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Gene Ontology Extension took 0.17985749244689941s
Reputation | Calculation of the PageRank for Gene Ontology Extension took 0.022415637969970703s
Interlinking | Calculation of Degree of Connection for Gene Ontology Extension took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Ontology Extension took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Gene Ontology Extension took 0.0008611679077148438s
Believability | Calculation of trust value for Gene Ontology Extension took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-go_x1 took 1.9817447662353516s
Availability | SPARQL endpoint availability check for Gene Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Gene Ontology took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Gene Ontology took 0.1870737075805664s
Reputation | Calculation of the PageRank for Gene Ontology took 0.021402597427368164s
Interlinking | Calculation of Degree of Connection for Gene Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Gene Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Gene Ontology took 0.0008513927459716797s
Believability | Calculation of trust value for Gene Ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-go_x2 took 1.9665093421936035s
Availability | SPARQL endpoint availability check for Cereal Plant Development took 8.416175842285156e-05s
Availability | VoID file availability check for Cereal Plant Development took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Cereal Plant Development took 0.18227124214172363s
Reputation | Calculation of the PageRank for Cereal Plant Development took 0.021309852600097656s
Interlinking | Calculation of Degree of Connection for Cereal Plant Development took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Cereal Plant Development took 0.0009679794311523438s
Interlinking | Calculation of Clustering coefficient for Cereal Plant Development took 3.838539123535156e-05s
Believability | Calculation of trust value for Cereal Plant Development took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-gro took 1.9809925556182861s
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.00020575523376464844s
Completeness | Calculation of interlinking completeness for Cereal plant gross anatomy took 0.17952227592468262s
Reputation | Calculation of the PageRank for Cereal plant gross anatomy took 0.02113032341003418s
Interlinking | Calculation of Degree of Connection for Cereal plant gross anatomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cereal plant gross anatomy took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Cereal plant gross anatomy took 0.00042939186096191406s
Believability | Calculation of trust value for Cereal plant gross anatomy took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-gro_x1 took 1.9603261947631836s
Availability | SPARQL endpoint availability check for Gene Regulation Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Gene Regulation Ontology took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Gene Regulation Ontology took 0.17897772789001465s
Reputation | Calculation of the PageRank for Gene Regulation Ontology took 0.020274639129638672s
Interlinking | Calculation of Degree of Connection for Gene Regulation Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gene Regulation Ontology took 0.0008194446563720703s
Interlinking | Calculation of Clustering coefficient for Gene Regulation Ontology took 0.0007975101470947266s
Believability | Calculation of trust value for Gene Regulation Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-gro_x2 took 1.9612505435943604s
Availability | SPARQL endpoint availability check for Hymenoptera Anatomy Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Hymenoptera Anatomy Ontology took 0.00020122528076171875s
Completeness | Calculation of interlinking completeness for Hymenoptera Anatomy Ontology took 0.17783665657043457s
Reputation | Calculation of the PageRank for Hymenoptera Anatomy Ontology took 0.02009105682373047s
Interlinking | Calculation of Degree of Connection for Hymenoptera Anatomy Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Hymenoptera Anatomy Ontology took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Hymenoptera Anatomy Ontology took 0.0005841255187988281s
Believability | Calculation of trust value for Hymenoptera Anatomy Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-hao took 1.9691779613494873s
Availability | SPARQL endpoint availability check for HCPCS took 8.153915405273438e-05s
Availability | VoID file availability check for HCPCS took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for HCPCS took 0.1820240020751953s
Reputation | Calculation of the PageRank for HCPCS took 0.0213623046875s
Interlinking | Calculation of Degree of Connection for HCPCS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for HCPCS took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for HCPCS took 0.00021600723266601562s
Believability | Calculation of trust value for HCPCS took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-hcpcs took 1.9614522457122803s
Availability | SPARQL endpoint availability check for Health Level Seven took 8.273124694824219e-05s
Availability | VoID file availability check for Health Level Seven took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Health Level Seven took 0.1885523796081543s
Reputation | Calculation of the PageRank for Health Level Seven took 0.020278453826904297s
Interlinking | Calculation of Degree of Connection for Health Level Seven took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Health Level Seven took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Health Level Seven took 0.0012555122375488281s
Believability | Calculation of trust value for Health Level Seven took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-hl7 took 1.9671449661254883s
Availability | SPARQL endpoint availability check for HEALTH_INDICATORS took 8.153915405273438e-05s
Availability | VoID file availability check for HEALTH_INDICATORS took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for HEALTH_INDICATORS took 0.17699384689331055s
Reputation | Calculation of the PageRank for HEALTH_INDICATORS took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for HEALTH_INDICATORS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HEALTH_INDICATORS took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for HEALTH_INDICATORS took 0.0003380775451660156s
Believability | Calculation of trust value for HEALTH_INDICATORS took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-hlth_indics took 1.9845435619354248s
Availability | SPARQL endpoint availability check for Ontology of homology and related concepts in biology took 3.981590270996094e-05s
Availability | VoID file availability check for Ontology of homology and related concepts in biology took 0.0005333423614501953s
Completeness | Calculation of interlinking completeness for Ontology of homology and related concepts in biology took 0.19028687477111816s
Reputation | Calculation of the PageRank for Ontology of homology and related concepts in biology took 0.02142930030822754s
Interlinking | Calculation of Degree of Connection for Ontology of homology and related concepts in biology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology of homology and related concepts in biology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Ontology of homology and related concepts in biology took 3.123283386230469e-05s
Believability | Calculation of trust value for Ontology of homology and related concepts in biology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-hom took 1.9617385864257812s
Availability | SPARQL endpoint availability check for HOM-HARVARD took 8.106231689453125e-05s
Availability | VoID file availability check for HOM-HARVARD took 0.00020813941955566406s
Completeness | Calculation of interlinking completeness for HOM-HARVARD took 0.17675280570983887s
Reputation | Calculation of the PageRank for HOM-HARVARD took 0.02141857147216797s
Interlinking | Calculation of Degree of Connection for HOM-HARVARD took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HOM-HARVARD took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for HOM-HARVARD took 3.218650817871094e-05s
Believability | Calculation of trust value for HOM-HARVARD took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-hom_harvard took 1.991335391998291s
Availability | SPARQL endpoint availability check for Human Phenotype Ontology took 8.082389831542969e-05s
Availability | VoID file availability check for Human Phenotype Ontology took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Human Phenotype Ontology took 0.18172407150268555s
Reputation | Calculation of the PageRank for Human Phenotype Ontology took 0.022174358367919922s
Interlinking | Calculation of Degree of Connection for Human Phenotype Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Human Phenotype Ontology took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Human Phenotype Ontology took 0.0006361007690429688s
Believability | Calculation of trust value for Human Phenotype Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hp_x1 took 1.9791266918182373s
Availability | SPARQL endpoint availability check for Host Pathogen Interactions Ontology took 5.8650970458984375e-05s
Availability | VoID file availability check for Host Pathogen Interactions Ontology took 0.0003840923309326172s
Completeness | Calculation of interlinking completeness for Host Pathogen Interactions Ontology took 0.1705312728881836s
Reputation | Calculation of the PageRank for Host Pathogen Interactions Ontology took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for Host Pathogen Interactions Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Host Pathogen Interactions Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Host Pathogen Interactions Ontology took 0.0010380744934082031s
Believability | Calculation of trust value for Host Pathogen Interactions Ontology took 6.4373016357421875e-06s
INFO | --- Analysis for bioportal-hpio took 1.9868440628051758s
Availability | SPARQL endpoint availability check for HUGO took 3.981590270996094e-05s
Availability | VoID file availability check for HUGO took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for HUGO took 0.1995849609375s
Reputation | Calculation of the PageRank for HUGO took 0.022236108779907227s
Interlinking | Calculation of Degree of Connection for HUGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HUGO took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for HUGO took 7.62939453125e-05s
Believability | Calculation of trust value for HUGO took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-hugo took 2.007382869720459s
Availability | SPARQL endpoint availability check for Information Artifact Ontology took 8.344650268554688e-05s
Availability | VoID file availability check for Information Artifact Ontology took 0.0005230903625488281s
Completeness | Calculation of interlinking completeness for Information Artifact Ontology took 0.18778610229492188s
Reputation | Calculation of the PageRank for Information Artifact Ontology took 0.02210402488708496s
Interlinking | Calculation of Degree of Connection for Information Artifact Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Information Artifact Ontology took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Information Artifact Ontology took 0.0006277561187744141s
Believability | Calculation of trust value for Information Artifact Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-iao took 1.99113130569458s
Availability | SPARQL endpoint availability check for ICD10 took 8.559226989746094e-05s
Availability | VoID file availability check for ICD10 took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for ICD10 took 0.1840808391571045s
Reputation | Calculation of the PageRank for ICD10 took 0.020353078842163086s
Interlinking | Calculation of Degree of Connection for ICD10 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICD10 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for ICD10 took 0.0007944107055664062s
Believability | Calculation of trust value for ICD10 took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-icd10 took 1.985172986984253s
Availability | SPARQL endpoint availability check for ICD10CM took 8.320808410644531e-05s
Availability | VoID file availability check for ICD10CM took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for ICD10CM took 0.18508195877075195s
Reputation | Calculation of the PageRank for ICD10CM took 0.021239519119262695s
Interlinking | Calculation of Degree of Connection for ICD10CM took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ICD10CM took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for ICD10CM took 0.0006120204925537109s
Believability | Calculation of trust value for ICD10CM took 1.4543533325195312e-05s
INFO | --- Analysis for bioportal-icd10cm took 2.000248908996582s
Availability | SPARQL endpoint availability check for ICD-10-PCS took 4.3392181396484375e-05s
Availability | VoID file availability check for ICD-10-PCS took 0.0010623931884765625s
Completeness | Calculation of interlinking completeness for ICD-10-PCS took 0.17866921424865723s
Reputation | Calculation of the PageRank for ICD-10-PCS took 0.022845983505249023s
Interlinking | Calculation of Degree of Connection for ICD-10-PCS took 1.52587890625e-05s
Interlinking | Calculation of Centrality for ICD-10-PCS took 0.0007779598236083984s
Interlinking | Calculation of Clustering coefficient for ICD-10-PCS took 0.00018548965454101562s
Believability | Calculation of trust value for ICD-10-PCS took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-icd10pcs took 2.159752607345581s
Availability | SPARQL endpoint availability check for International Classification of Diseases took 8.749961853027344e-05s
Availability | VoID file availability check for International Classification of Diseases took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for International Classification of Diseases took 0.17433404922485352s
Reputation | Calculation of the PageRank for International Classification of Diseases took 0.020136117935180664s
Interlinking | Calculation of Degree of Connection for International Classification of Diseases took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for International Classification of Diseases took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for International Classification of Diseases took 0.0006554126739501953s
Believability | Calculation of trust value for International Classification of Diseases took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-icd9cm took 1.9872026443481445s
Availability | SPARQL endpoint availability check for International Classification of Functioning, Disability and Health (ICF) took 8.344650268554688e-05s
Availability | VoID file availability check for International Classification of Functioning, Disability and Health (ICF) took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for International Classification of Functioning, Disability and Health (ICF) took 0.18257808685302734s
Reputation | Calculation of the PageRank for International Classification of Functioning, Disability and Health (ICF) took 0.019989490509033203s
Interlinking | Calculation of Degree of Connection for International Classification of Functioning, Disability and Health (ICF) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for International Classification of Functioning, Disability and Health (ICF) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for International Classification of Functioning, Disability and Health (ICF) took 0.0004436969757080078s
Believability | Calculation of trust value for International Classification of Functioning, Disability and Health (ICF) took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-icf_x1 took 2.020918369293213s
Availability | SPARQL endpoint availability check for International Classification for Nursing Practice took 5.125999450683594e-05s
Availability | VoID file availability check for International Classification for Nursing Practice took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for International Classification for Nursing Practice took 0.17577600479125977s
Reputation | Calculation of the PageRank for International Classification for Nursing Practice took 0.020254850387573242s
Interlinking | Calculation of Degree of Connection for International Classification for Nursing Practice took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for International Classification for Nursing Practice took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for International Classification for Nursing Practice took 0.0012402534484863281s
Believability | Calculation of trust value for International Classification for Nursing Practice took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-icnp took 1.9824423789978027s
Availability | SPARQL endpoint availability check for International Classification of Primary Care took 8.082389831542969e-05s
Availability | VoID file availability check for International Classification of Primary Care took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for International Classification of Primary Care took 0.18260455131530762s
Reputation | Calculation of the PageRank for International Classification of Primary Care took 0.020152807235717773s
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.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for International Classification of Primary Care took 0.00043773651123046875s
Believability | Calculation of trust value for International Classification of Primary Care took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-icpc took 2.018923759460449s
Availability | SPARQL endpoint availability check for ICPC-2 PLUS took 4.00543212890625e-05s
Availability | VoID file availability check for ICPC-2 PLUS took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for ICPC-2 PLUS took 0.18190217018127441s
Reputation | Calculation of the PageRank for ICPC-2 PLUS took 0.020776748657226562s
Interlinking | Calculation of Degree of Connection for ICPC-2 PLUS took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for ICPC-2 PLUS took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for ICPC-2 PLUS took 0.0008633136749267578s
Believability | Calculation of trust value for ICPC-2 PLUS took 7.62939453125e-06s
INFO | --- Analysis for bioportal-icpc2p took 1.9964220523834229s
Availability | SPARQL endpoint availability check for ICPS Network took 4.029273986816406e-05s
Availability | VoID file availability check for ICPS Network took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for ICPS Network took 0.18413591384887695s
Reputation | Calculation of the PageRank for ICPS Network took 0.022516727447509766s
Interlinking | Calculation of Degree of Connection for ICPS Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ICPS Network took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for ICPS Network took 0.0002143383026123047s
Believability | Calculation of trust value for ICPS Network took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-icps took 1.9684364795684814s
Availability | SPARQL endpoint availability check for Infectious Disease Ontology took 8.392333984375e-05s
Availability | VoID file availability check for Infectious Disease Ontology took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Infectious Disease Ontology took 0.1804807186126709s
Reputation | Calculation of the PageRank for Infectious Disease Ontology took 0.022227764129638672s
Interlinking | Calculation of Degree of Connection for Infectious Disease Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Infectious Disease Ontology took 0.0008103847503662109s
Interlinking | Calculation of Clustering coefficient for Infectious Disease Ontology took 0.0009131431579589844s
Believability | Calculation of trust value for Infectious Disease Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-ido took 2.0413708686828613s
Availability | SPARQL endpoint availability check for Brucellosis Ontology took 3.981590270996094e-05s
Availability | VoID file availability check for Brucellosis Ontology took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Brucellosis Ontology took 0.18149566650390625s
Reputation | Calculation of the PageRank for Brucellosis Ontology took 0.021676301956176758s
Interlinking | Calculation of Degree of Connection for Brucellosis Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Brucellosis Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Brucellosis Ontology took 0.0011184215545654297s
Believability | Calculation of trust value for Brucellosis Ontology took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-idobru took 2.0095374584198s
Availability | SPARQL endpoint availability check for Malaria Ontology took 0.0002238750457763672s
Availability | VoID file availability check for Malaria Ontology took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Malaria Ontology took 0.17483043670654297s
Reputation | Calculation of the PageRank for Malaria Ontology took 0.022417306900024414s
Interlinking | Calculation of Degree of Connection for Malaria Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Malaria Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Malaria Ontology took 0.0012972354888916016s
Believability | Calculation of trust value for Malaria Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-idomal took 1.9743907451629639s
Availability | SPARQL endpoint availability check for Event (INOH pathway ontology) took 8.368492126464844e-05s
Availability | VoID file availability check for Event (INOH pathway ontology) took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Event (INOH pathway ontology) took 0.18440842628479004s
Reputation | Calculation of the PageRank for Event (INOH pathway ontology) took 0.02013421058654785s
Interlinking | Calculation of Degree of Connection for Event (INOH pathway ontology) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Event (INOH pathway ontology) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Event (INOH pathway ontology) took 0.0002925395965576172s
Believability | Calculation of trust value for Event (INOH pathway ontology) took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-iev took 2.016481876373291s
Availability | SPARQL endpoint availability check for IMGT-ONTOLOGY took 8.392333984375e-05s
Availability | VoID file availability check for IMGT-ONTOLOGY took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for IMGT-ONTOLOGY took 0.18220877647399902s
Reputation | Calculation of the PageRank for IMGT-ONTOLOGY took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for IMGT-ONTOLOGY took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for IMGT-ONTOLOGY took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for IMGT-ONTOLOGY took 0.00014638900756835938s
Believability | Calculation of trust value for IMGT-ONTOLOGY took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-imgt took 1.965142011642456s
Availability | SPARQL endpoint availability check for Molecule role (INOH Protein name/family name ontology) took 8.249282836914062e-05s
Availability | VoID file availability check for Molecule role (INOH Protein name/family name ontology) took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Molecule role (INOH Protein name/family name ontology) took 0.17305731773376465s
Reputation | Calculation of the PageRank for Molecule role (INOH Protein name/family name ontology) took 0.022459030151367188s
Interlinking | Calculation of Degree of Connection for Molecule role (INOH Protein name/family name ontology) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Molecule role (INOH Protein name/family name ontology) took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for Molecule role (INOH Protein name/family name ontology) took 0.0005161762237548828s
Believability | Calculation of trust value for Molecule role (INOH Protein name/family name ontology) took 5.0067901611328125e-06s
INFO | --- Analysis for bioportal-imr took 1.9809913635253906s
Availability | SPARQL endpoint availability check for Interaction Network Ontology took 4.792213439941406e-05s
Availability | VoID file availability check for Interaction Network Ontology took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Interaction Network Ontology took 0.18612027168273926s
Reputation | Calculation of the PageRank for Interaction Network Ontology took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Interaction Network Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Interaction Network Ontology took 0.0009324550628662109s
Interlinking | Calculation of Clustering coefficient for Interaction Network Ontology took 0.0008749961853027344s
Believability | Calculation of trust value for Interaction Network Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-ino took 1.9602680206298828s
Availability | SPARQL endpoint availability check for Hewan Invertebrata took 4.1484832763671875e-05s
Availability | VoID file availability check for Hewan Invertebrata took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Hewan Invertebrata took 0.18383574485778809s
Reputation | Calculation of the PageRank for Hewan Invertebrata took 0.021766185760498047s
Interlinking | Calculation of Degree of Connection for Hewan Invertebrata took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Hewan Invertebrata took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Hewan Invertebrata took 2.765655517578125e-05s
Believability | Calculation of trust value for Hewan Invertebrata took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-invertebrata took 1.9997491836547852s
Availability | SPARQL endpoint availability check for IxnO took 8.511543273925781e-05s
Availability | VoID file availability check for IxnO took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for IxnO took 0.17910337448120117s
Reputation | Calculation of the PageRank for IxnO took 0.02008843421936035s
Interlinking | Calculation of Degree of Connection for IxnO took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IxnO took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for IxnO took 0.0001842975616455078s
Believability | Calculation of trust value for IxnO took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ixno took 1.9993085861206055s
Availability | SPARQL endpoint availability check for SysMO-JERM took 8.678436279296875e-05s
Availability | VoID file availability check for SysMO-JERM took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for SysMO-JERM took 0.17585206031799316s
Reputation | Calculation of the PageRank for SysMO-JERM took 0.02016162872314453s
Interlinking | Calculation of Degree of Connection for SysMO-JERM took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SysMO-JERM took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for SysMO-JERM took 0.0004086494445800781s
Believability | Calculation of trust value for SysMO-JERM took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-jerm took 1.9646973609924316s
Availability | SPARQL endpoint availability check for Kinetic Simulation Algorithm Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Kinetic Simulation Algorithm Ontology took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Kinetic Simulation Algorithm Ontology took 0.18611574172973633s
Reputation | Calculation of the PageRank for Kinetic Simulation Algorithm Ontology took 0.02007889747619629s
Interlinking | Calculation of Degree of Connection for Kinetic Simulation Algorithm Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Kinetic Simulation Algorithm Ontology took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Kinetic Simulation Algorithm Ontology took 2.7894973754882812e-05s
Believability | Calculation of trust value for Kinetic Simulation Algorithm Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-kisao took 1.9978992938995361s
Availability | SPARQL endpoint availability check for Loggerhead nesting took 8.702278137207031e-05s
Availability | VoID file availability check for Loggerhead nesting took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Loggerhead nesting took 0.23046231269836426s
Reputation | Calculation of the PageRank for Loggerhead nesting took 0.02018880844116211s
Interlinking | Calculation of Degree of Connection for Loggerhead nesting took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Loggerhead nesting took 0.0009205341339111328s
Interlinking | Calculation of Clustering coefficient for Loggerhead nesting took 0.00024271011352539062s
Believability | Calculation of trust value for Loggerhead nesting took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-lhn took 2.045654773712158s
Availability | SPARQL endpoint availability check for Lipid Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Lipid Ontology took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Lipid Ontology took 0.19723820686340332s
Reputation | Calculation of the PageRank for Lipid Ontology took 0.0199429988861084s
Interlinking | Calculation of Degree of Connection for Lipid Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lipid Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Lipid Ontology took 0.00019931793212890625s
Believability | Calculation of trust value for Lipid Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-lipro took 1.9944133758544922s
Availability | SPARQL endpoint availability check for Logical Observation Identifier Names and Codes took 4.172325134277344e-05s
Availability | VoID file availability check for Logical Observation Identifier Names and Codes took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Logical Observation Identifier Names and Codes took 0.18184113502502441s
Reputation | Calculation of the PageRank for Logical Observation Identifier Names and Codes took 0.020126819610595703s
Interlinking | Calculation of Degree of Connection for Logical Observation Identifier Names and Codes took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Logical Observation Identifier Names and Codes took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Logical Observation Identifier Names and Codes took 0.0018475055694580078s
Believability | Calculation of trust value for Logical Observation Identifier Names and Codes took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-lnc took 1.9532670974731445s
Availability | SPARQL endpoint availability check for Mouse adult gross anatomy took 0.0001590251922607422s
Availability | VoID file availability check for Mouse adult gross anatomy took 0.0002493858337402344s
Completeness | Calculation of interlinking completeness for Mouse adult gross anatomy took 0.19080829620361328s
Reputation | Calculation of the PageRank for Mouse adult gross anatomy took 0.020049333572387695s
Interlinking | Calculation of Degree of Connection for Mouse adult gross anatomy took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Mouse adult gross anatomy took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Mouse adult gross anatomy took 0.0006747245788574219s
Believability | Calculation of trust value for Mouse adult gross anatomy took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-ma took 1.9967365264892578s
Availability | SPARQL endpoint availability check for Multiple alignment took 4.00543212890625e-05s
Availability | VoID file availability check for Multiple alignment took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Multiple alignment took 0.17553925514221191s
Reputation | Calculation of the PageRank for Multiple alignment took 0.021223068237304688s
Interlinking | Calculation of Degree of Connection for Multiple alignment took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Multiple alignment took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Multiple alignment took 0.00019049644470214844s
Believability | Calculation of trust value for Multiple alignment took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mao took 1.978630781173706s
Availability | SPARQL endpoint availability check for Minimal anatomical terminology took 8.440017700195312e-05s
Availability | VoID file availability check for Minimal anatomical terminology took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Minimal anatomical terminology took 0.2962362766265869s
Reputation | Calculation of the PageRank for Minimal anatomical terminology took 0.021269798278808594s
Interlinking | Calculation of Degree of Connection for Minimal anatomical terminology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Minimal anatomical terminology took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Minimal anatomical terminology took 0.0006723403930664062s
Believability | Calculation of trust value for Minimal anatomical terminology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mat took 2.147787570953369s
Availability | SPARQL endpoint availability check for Breast tissue cell lines took 8.463859558105469e-05s
Availability | VoID file availability check for Breast tissue cell lines took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Breast tissue cell lines took 0.1826343536376953s
Reputation | Calculation of the PageRank for Breast tissue cell lines took 0.02018594741821289s
Interlinking | Calculation of Degree of Connection for Breast tissue cell lines took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Breast tissue cell lines took 0.0009684562683105469s
Interlinking | Calculation of Clustering coefficient for Breast tissue cell lines took 0.0004944801330566406s
Believability | Calculation of trust value for Breast tissue cell lines took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mcbcc took 1.971573829650879s
Availability | SPARQL endpoint availability check for Cell line ontology took 9.107589721679688e-05s
Availability | VoID file availability check for Cell line ontology took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.18609309196472168s
Reputation | Calculation of the PageRank for Cell line ontology took 0.01985311508178711s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.000732421875s
Believability | Calculation of trust value for Cell line ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mccl took 2.0254392623901367s
Availability | SPARQL endpoint availability check for Cell line ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Cell line ontology took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Cell line ontology took 0.17529964447021484s
Reputation | Calculation of the PageRank for Cell line ontology took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Cell line ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cell line ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Cell line ontology took 0.0014314651489257812s
Believability | Calculation of trust value for Cell line ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-mccl_x1 took 1.9868638515472412s
Availability | SPARQL endpoint availability check for MIxS Controlled Vocabularies took 8.559226989746094e-05s
Availability | VoID file availability check for MIxS Controlled Vocabularies took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for MIxS Controlled Vocabularies took 0.1867387294769287s
Reputation | Calculation of the PageRank for MIxS Controlled Vocabularies took 0.02020406723022461s
Interlinking | Calculation of Degree of Connection for MIxS Controlled Vocabularies took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MIxS Controlled Vocabularies took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for MIxS Controlled Vocabularies took 0.00022745132446289062s
Believability | Calculation of trust value for MIxS Controlled Vocabularies took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-mcv took 2.047877788543701s
Availability | SPARQL endpoint availability check for Master Drug Data Base took 9.036064147949219e-05s
Availability | VoID file availability check for Master Drug Data Base took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Master Drug Data Base took 0.1960601806640625s
Reputation | Calculation of the PageRank for Master Drug Data Base took 0.020129680633544922s
Interlinking | Calculation of Degree of Connection for Master Drug Data Base took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Master Drug Data Base took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Master Drug Data Base took 0.0001697540283203125s
Believability | Calculation of trust value for Master Drug Data Base took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mddb took 2.0091116428375244s
Availability | SPARQL endpoint availability check for MedDRA took 0.00010609626770019531s
Availability | VoID file availability check for MedDRA took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for MedDRA took 0.1733863353729248s
Reputation | Calculation of the PageRank for MedDRA took 0.020096540451049805s
Interlinking | Calculation of Degree of Connection for MedDRA took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MedDRA took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for MedDRA took 0.0011506080627441406s
Believability | Calculation of trust value for MedDRA took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-mdr took 1.992152214050293s
Availability | SPARQL endpoint availability check for MedlinePlus Health Topics took 4.076957702636719e-05s
Availability | VoID file availability check for MedlinePlus Health Topics took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for MedlinePlus Health Topics took 0.17510509490966797s
Reputation | Calculation of the PageRank for MedlinePlus Health Topics took 0.019989967346191406s
Interlinking | Calculation of Degree of Connection for MedlinePlus Health Topics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MedlinePlus Health Topics took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for MedlinePlus Health Topics took 0.0008959770202636719s
Believability | Calculation of trust value for MedlinePlus Health Topics took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-medlineplus took 1.97859525680542s
Availability | SPARQL endpoint availability check for MeGO took 4.076957702636719e-05s
Availability | VoID file availability check for MeGO took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for MeGO took 0.17577242851257324s
Reputation | Calculation of the PageRank for MeGO took 0.02012944221496582s
Interlinking | Calculation of Degree of Connection for MeGO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MeGO took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for MeGO took 0.000141143798828125s
Believability | Calculation of trust value for MeGO took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mego took 1.9782757759094238s
Availability | SPARQL endpoint availability check for MESH Thesaurus (OWL version) took 8.20159912109375e-05s
Availability | VoID file availability check for MESH Thesaurus (OWL version) took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for MESH Thesaurus (OWL version) took 0.17708539962768555s
Reputation | Calculation of the PageRank for MESH Thesaurus (OWL version) took 0.022376060485839844s
Interlinking | Calculation of Degree of Connection for MESH Thesaurus (OWL version) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MESH Thesaurus (OWL version) took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for MESH Thesaurus (OWL version) took 0.0018429756164550781s
Believability | Calculation of trust value for MESH Thesaurus (OWL version) took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-mesh-owl took 1.9958429336547852s
Availability | SPARQL endpoint availability check for Mental Functioning Ontology took 4.1961669921875e-05s
Availability | VoID file availability check for Mental Functioning Ontology took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Mental Functioning Ontology took 0.18402767181396484s
Reputation | Calculation of the PageRank for Mental Functioning Ontology took 0.022305011749267578s
Interlinking | Calculation of Degree of Connection for Mental Functioning Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mental Functioning Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Mental Functioning Ontology took 0.0006115436553955078s
Believability | Calculation of trust value for Mental Functioning Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mf took 1.9785022735595703s
Availability | SPARQL endpoint availability check for Medaka fish anatomy and development took 8.726119995117188e-05s
Availability | VoID file availability check for Medaka fish anatomy and development took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for Medaka fish anatomy and development took 0.1812291145324707s
Reputation | Calculation of the PageRank for Medaka fish anatomy and development took 0.019992828369140625s
Interlinking | Calculation of Degree of Connection for Medaka fish anatomy and development took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Medaka fish anatomy and development took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Medaka fish anatomy and development took 0.0005478858947753906s
Believability | Calculation of trust value for Medaka fish anatomy and development took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-mfo took 2.0166125297546387s
Availability | SPARQL endpoint availability check for Emotion Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Emotion Ontology took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Emotion Ontology took 0.2046372890472412s
Reputation | Calculation of the PageRank for Emotion Ontology took 0.02148890495300293s
Interlinking | Calculation of Degree of Connection for Emotion Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Emotion Ontology took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Emotion Ontology took 0.0007719993591308594s
Believability | Calculation of trust value for Emotion Ontology took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-mfoem took 2.0718894004821777s
Availability | SPARQL endpoint availability check for MaHCO - An MHC Ontology took 8.654594421386719e-05s
Availability | VoID file availability check for MaHCO - An MHC Ontology took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for MaHCO - An MHC Ontology took 0.18633365631103516s
Reputation | Calculation of the PageRank for MaHCO - An MHC Ontology took 0.022547245025634766s
Interlinking | Calculation of Degree of Connection for MaHCO - An MHC Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for MaHCO - An MHC Ontology took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for MaHCO - An MHC Ontology took 0.00010061264038085938s
Believability | Calculation of trust value for MaHCO - An MHC Ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mhc took 1.9715163707733154s
Availability | SPARQL endpoint availability check for Protein-protein interaction took 8.797645568847656e-05s
Availability | VoID file availability check for Protein-protein interaction took 0.0005300045013427734s
Completeness | Calculation of interlinking completeness for Protein-protein interaction took 0.18114709854125977s
Reputation | Calculation of the PageRank for Protein-protein interaction took 0.022613048553466797s
Interlinking | Calculation of Degree of Connection for Protein-protein interaction took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Protein-protein interaction took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Protein-protein interaction took 0.0006787776947021484s
Believability | Calculation of trust value for Protein-protein interaction took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mi took 1.994065523147583s
Availability | SPARQL endpoint availability check for Mosquito insecticide resistance took 9.226799011230469e-05s
Availability | VoID file availability check for Mosquito insecticide resistance took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Mosquito insecticide resistance took 0.17548871040344238s
Reputation | Calculation of the PageRank for Mosquito insecticide resistance took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for Mosquito insecticide resistance took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mosquito insecticide resistance took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Mosquito insecticide resistance took 0.0008046627044677734s
Believability | Calculation of trust value for Mosquito insecticide resistance took 7.152557373046875e-06s
INFO | --- Analysis for bioportal-miro took 1.9669299125671387s
Availability | SPARQL endpoint availability check for Measurement Method Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Measurement Method Ontology took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Measurement Method Ontology took 0.17632603645324707s
Reputation | Calculation of the PageRank for Measurement Method Ontology took 0.01992177963256836s
Interlinking | Calculation of Degree of Connection for Measurement Method Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Measurement Method Ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Measurement Method Ontology took 0.00013136863708496094s
Believability | Calculation of trust value for Measurement Method Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-mmo took 2.025535821914673s
Availability | SPARQL endpoint availability check for MGED Ontology took 8.487701416015625e-05s
Availability | VoID file availability check for MGED Ontology took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for MGED Ontology took 0.18967247009277344s
Reputation | Calculation of the PageRank for MGED Ontology took 0.020115137100219727s
Interlinking | Calculation of Degree of Connection for MGED Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MGED Ontology took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for MGED Ontology took 0.0003745555877685547s
Believability | Calculation of trust value for MGED Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-mo took 2.0135157108306885s
Availability | SPARQL endpoint availability check for Protein modification took 5.030632019042969e-05s
Availability | VoID file availability check for Protein modification took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Protein modification took 0.17306280136108398s
Reputation | Calculation of the PageRank for Protein modification took 0.02070927619934082s
Interlinking | Calculation of Degree of Connection for Protein modification took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Protein modification took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Protein modification took 0.00022864341735839844s
Believability | Calculation of trust value for Protein modification took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-mod took 2.036280632019043s
Availability | SPARQL endpoint availability check for Mammalian phenotype took 3.981590270996094e-05s
Availability | VoID file availability check for Mammalian phenotype took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for Mammalian phenotype took 0.17787766456604004s
Reputation | Calculation of the PageRank for Mammalian phenotype took 0.020352602005004883s
Interlinking | Calculation of Degree of Connection for Mammalian phenotype took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mammalian phenotype took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Mammalian phenotype took 0.0006482601165771484s
Believability | Calculation of trust value for Mammalian phenotype took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-mp took 1.988551378250122s
Availability | SPARQL endpoint availability check for Mouse pathology took 5.245208740234375e-05s
Availability | VoID file availability check for Mouse pathology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Mouse pathology took 0.17864012718200684s
Reputation | Calculation of the PageRank for Mouse pathology took 0.01995253562927246s
Interlinking | Calculation of Degree of Connection for Mouse pathology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Mouse pathology took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Mouse pathology took 0.00047206878662109375s
Believability | Calculation of trust value for Mouse pathology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mpath took 1.9814872741699219s
Availability | SPARQL endpoint availability check for Mass spectrometry took 4.100799560546875e-05s
Availability | VoID file availability check for Mass spectrometry took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Mass spectrometry took 0.17600345611572266s
Reputation | Calculation of the PageRank for Mass spectrometry took 0.01998281478881836s
Interlinking | Calculation of Degree of Connection for Mass spectrometry took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Mass spectrometry took 0.0009298324584960938s
Interlinking | Calculation of Clustering coefficient for Mass spectrometry took 0.00040984153747558594s
Believability | Calculation of trust value for Mass spectrometry took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-ms took 1.9479713439941406s
Availability | SPARQL endpoint availability check for Medical Subject Headings took 6.0558319091796875e-05s
Availability | VoID file availability check for Medical Subject Headings took 0.0005192756652832031s
Completeness | Calculation of interlinking completeness for Medical Subject Headings took 0.1748824119567871s
Reputation | Calculation of the PageRank for Medical Subject Headings took 0.022727489471435547s
Interlinking | Calculation of Degree of Connection for Medical Subject Headings took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Medical Subject Headings took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for Medical Subject Headings took 0.001977682113647461s
Believability | Calculation of trust value for Medical Subject Headings took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-msh took 2.0191726684570312s
Availability | SPARQL endpoint availability check for Metathesaurus CPT Hierarchical Terms took 4.124641418457031e-05s
Availability | VoID file availability check for Metathesaurus CPT Hierarchical Terms took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Metathesaurus CPT Hierarchical Terms took 0.1834733486175537s
Reputation | Calculation of the PageRank for Metathesaurus CPT Hierarchical Terms took 0.02139902114868164s
Interlinking | Calculation of Degree of Connection for Metathesaurus CPT Hierarchical Terms took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Metathesaurus CPT Hierarchical Terms took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Metathesaurus CPT Hierarchical Terms took 0.00017642974853515625s
Believability | Calculation of trust value for Metathesaurus CPT Hierarchical Terms took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-mthch took 2.0155677795410156s
Availability | SPARQL endpoint availability check for Natural Products Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Natural Products Ontology took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Natural Products Ontology took 0.1822676658630371s
Reputation | Calculation of the PageRank for Natural Products Ontology took 0.020397186279296875s
Interlinking | Calculation of Degree of Connection for Natural Products Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Natural Products Ontology took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Natural Products Ontology took 0.0007870197296142578s
Believability | Calculation of trust value for Natural Products Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-natpro took 1.9965531826019287s
Availability | SPARQL endpoint availability check for NCBI organismal classification took 8.7738037109375e-05s
Availability | VoID file availability check for NCBI organismal classification took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for NCBI organismal classification took 0.18010449409484863s
Reputation | Calculation of the PageRank for NCBI organismal classification took 0.020060062408447266s
Interlinking | Calculation of Degree of Connection for NCBI organismal classification took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for NCBI organismal classification took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for NCBI organismal classification took 0.0008039474487304688s
Believability | Calculation of trust value for NCBI organismal classification took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ncbitaxon took 1.9898815155029297s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.654594421386719e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.17368793487548828s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.02016282081604004s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0008788108825683594s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 0.002138853073120117s
Believability | Calculation of trust value for NCI Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ncit took 2.006389617919922s
Availability | SPARQL endpoint availability check for National Drug Data File took 8.320808410644531e-05s
Availability | VoID file availability check for National Drug Data File took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for National Drug Data File took 0.17367219924926758s
Reputation | Calculation of the PageRank for National Drug Data File took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for National Drug Data File took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for National Drug Data File took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for National Drug Data File took 0.0006256103515625s
Believability | Calculation of trust value for National Drug Data File took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-nddf took 2.000131130218506s
Availability | SPARQL endpoint availability check for National Drug File took 8.392333984375e-05s
Availability | VoID file availability check for National Drug File took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for National Drug File took 0.18093323707580566s
Reputation | Calculation of the PageRank for National Drug File took 0.020326614379882812s
Interlinking | Calculation of Degree of Connection for National Drug File took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for National Drug File took 0.0009119510650634766s
Interlinking | Calculation of Clustering coefficient for National Drug File took 0.001397848129272461s
Believability | Calculation of trust value for National Drug File took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ndfrt took 1.9815008640289307s
Availability | SPARQL endpoint availability check for Neural ElectroMagnetic Ontologies took 3.886222839355469e-05s
Availability | VoID file availability check for Neural ElectroMagnetic Ontologies took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for Neural ElectroMagnetic Ontologies took 0.1813068389892578s
Reputation | Calculation of the PageRank for Neural ElectroMagnetic Ontologies took 0.02005767822265625s
Interlinking | Calculation of Degree of Connection for Neural ElectroMagnetic Ontologies took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Neural ElectroMagnetic Ontologies took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Neural ElectroMagnetic Ontologies took 0.0011546611785888672s
Believability | Calculation of trust value for Neural ElectroMagnetic Ontologies took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-nemo_x1 took 1.9686846733093262s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Neomark Oral Cancer Ontology took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer Ontology took 0.1749262809753418s
Reputation | Calculation of the PageRank for Neomark Oral Cancer Ontology took 0.02008342742919922s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer Ontology took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer Ontology took 0.0006499290466308594s
Believability | Calculation of trust value for Neomark Oral Cancer Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-neomark took 1.975088119506836s
Availability | SPARQL endpoint availability check for Neomark Oral Cancer-Centred Ontology took 8.320808410644531e-05s
Availability | VoID file availability check for Neomark Oral Cancer-Centred Ontology took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Neomark Oral Cancer-Centred Ontology took 0.19597554206848145s
Reputation | Calculation of the PageRank for Neomark Oral Cancer-Centred Ontology took 0.020109176635742188s
Interlinking | Calculation of Degree of Connection for Neomark Oral Cancer-Centred Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Neomark Oral Cancer-Centred Ontology took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Neomark Oral Cancer-Centred Ontology took 0.00011539459228515625s
Believability | Calculation of trust value for Neomark Oral Cancer-Centred Ontology took 7.3909759521484375e-06s
INFO | --- Analysis for bioportal-neomarkontology took 2.001617431640625s
Availability | SPARQL endpoint availability check for NIFSTD took 4.0531158447265625e-05s
Availability | VoID file availability check for NIFSTD took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for NIFSTD took 0.18250322341918945s
Reputation | Calculation of the PageRank for NIFSTD took 0.022416353225708008s
Interlinking | Calculation of Degree of Connection for NIFSTD took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for NIFSTD took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for NIFSTD took 0.0018954277038574219s
Believability | Calculation of trust value for NIFSTD took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-nif took 2.0015060901641846s
Availability | SPARQL endpoint availability check for NIF Cell took 4.029273986816406e-05s
Availability | VoID file availability check for NIF Cell took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for NIF Cell took 0.18892860412597656s
Reputation | Calculation of the PageRank for NIF Cell took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for NIF Cell took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for NIF Cell took 0.0006859302520751953s
Interlinking | Calculation of Clustering coefficient for NIF Cell took 0.001348733901977539s
Believability | Calculation of trust value for NIF Cell took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-nif_cell took 2.0202362537384033s
Availability | SPARQL endpoint availability check for NIF Dysfunction took 8.177757263183594e-05s
Availability | VoID file availability check for NIF Dysfunction took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for NIF Dysfunction took 0.1816542148590088s
Reputation | Calculation of the PageRank for NIF Dysfunction took 0.020996570587158203s
Interlinking | Calculation of Degree of Connection for NIF Dysfunction took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for NIF Dysfunction took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for NIF Dysfunction took 0.0013742446899414062s
Believability | Calculation of trust value for NIF Dysfunction took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-nif_dysfunction took 2.031614065170288s
Availability | SPARQL endpoint availability check for Neural-Immune Gene Ontology took 4.00543212890625e-05s
Availability | VoID file availability check for Neural-Immune Gene Ontology took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Neural-Immune Gene Ontology took 0.17865490913391113s
Reputation | Calculation of the PageRank for Neural-Immune Gene Ontology took 0.02042531967163086s
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.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Neural-Immune Gene Ontology took 0.0005974769592285156s
Believability | Calculation of trust value for Neural-Immune Gene Ontology took 1.52587890625e-05s
INFO | --- Analysis for bioportal-nigo took 1.9691271781921387s
Availability | SPARQL endpoint availability check for NMR-instrument specific component of metabolomics investigations took 8.606910705566406e-05s
Availability | VoID file availability check for NMR-instrument specific component of metabolomics investigations took 0.000255584716796875s
Completeness | Calculation of interlinking completeness for NMR-instrument specific component of metabolomics investigations took 0.1774296760559082s
Reputation | Calculation of the PageRank for NMR-instrument specific component of metabolomics investigations took 0.020064353942871094s
Interlinking | Calculation of Degree of Connection for NMR-instrument specific component of metabolomics investigations took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for NMR-instrument specific component of metabolomics investigations took 0.0009002685546875s
Interlinking | Calculation of Clustering coefficient for NMR-instrument specific component of metabolomics investigations took 0.0006089210510253906s
Believability | Calculation of trust value for NMR-instrument specific component of metabolomics investigations took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-nmr took 1.9849748611450195s
Availability | SPARQL endpoint availability check for Non Randomized Controlled Trials Ontology took 7.915496826171875e-05s
Availability | VoID file availability check for Non Randomized Controlled Trials Ontology took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Non Randomized Controlled Trials Ontology took 0.18341755867004395s
Reputation | Calculation of the PageRank for Non Randomized Controlled Trials Ontology took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for Non Randomized Controlled Trials Ontology took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Non Randomized Controlled Trials Ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Non Randomized Controlled Trials Ontology took 0.00010395050048828125s
Believability | Calculation of trust value for Non Randomized Controlled Trials Ontology took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-nonrctontology took 1.9822890758514404s
Availability | SPARQL endpoint availability check for NanoParticle Ontology took 3.910064697265625e-05s
Availability | VoID file availability check for NanoParticle Ontology took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for NanoParticle Ontology took 0.18454194068908691s
Reputation | Calculation of the PageRank for NanoParticle Ontology took 0.020887136459350586s
Interlinking | Calculation of Degree of Connection for NanoParticle Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for NanoParticle Ontology took 0.000797271728515625s
Interlinking | Calculation of Clustering coefficient for NanoParticle Ontology took 0.0011649131774902344s
Believability | Calculation of trust value for NanoParticle Ontology took 1.0251998901367188e-05s
INFO | --- Analysis for bioportal-npo took 1.9915478229522705s
Availability | SPARQL endpoint availability check for Ontology of Adverse Events (OAE) took 5.9604644775390625e-05s
Availability | VoID file availability check for Ontology of Adverse Events (OAE) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Ontology of Adverse Events (OAE) took 0.1825253963470459s
Reputation | Calculation of the PageRank for Ontology of Adverse Events (OAE) took 0.02130413055419922s
Interlinking | Calculation of Degree of Connection for Ontology of Adverse Events (OAE) took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ontology of Adverse Events (OAE) took 0.001055002212524414s
Interlinking | Calculation of Clustering coefficient for Ontology of Adverse Events (OAE) took 0.0008497238159179688s
Believability | Calculation of trust value for Ontology of Adverse Events (OAE) took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-oae took 1.9882564544677734s
Availability | SPARQL endpoint availability check for Ontology for Biomedical Investigations took 6.461143493652344e-05s
Availability | VoID file availability check for Ontology for Biomedical Investigations took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for Ontology for Biomedical Investigations took 0.17528748512268066s
Reputation | Calculation of the PageRank for Ontology for Biomedical Investigations took 0.01995539665222168s
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.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for Ontology for Biomedical Investigations took 0.0014400482177734375s
Believability | Calculation of trust value for Ontology for Biomedical Investigations took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-obi took 1.987607479095459s
Availability | SPARQL endpoint availability check for OBOE took 3.933906555175781e-05s
Availability | VoID file availability check for OBOE took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for OBOE took 0.18236589431762695s
Reputation | Calculation of the PageRank for OBOE took 0.020072460174560547s
Interlinking | Calculation of Degree of Connection for OBOE took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for OBOE took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for OBOE took 0.0001049041748046875s
Believability | Calculation of trust value for OBOE took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-oboe took 1.9740009307861328s
Availability | SPARQL endpoint availability check for OBOE SBC took 8.487701416015625e-05s
Availability | VoID file availability check for OBOE SBC took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for OBOE SBC took 0.20583438873291016s
Reputation | Calculation of the PageRank for OBOE SBC took 0.020763874053955078s
Interlinking | Calculation of Degree of Connection for OBOE SBC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OBOE SBC took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for OBOE SBC took 0.0008206367492675781s
Believability | Calculation of trust value for OBOE SBC took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-oboe-sbc took 2.005908250808716s
Availability | SPARQL endpoint availability check for Ontology of Clinical Research (OCRe) took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology of Clinical Research (OCRe) took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Ontology of Clinical Research (OCRe) took 0.17441940307617188s
Reputation | Calculation of the PageRank for Ontology of Clinical Research (OCRe) took 0.02007126808166504s
Interlinking | Calculation of Degree of Connection for Ontology of Clinical Research (OCRe) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Ontology of Clinical Research (OCRe) took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for Ontology of Clinical Research (OCRe) took 0.0005576610565185547s
Believability | Calculation of trust value for Ontology of Clinical Research (OCRe) took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-ocre took 2.000997304916382s
Availability | SPARQL endpoint availability check for Ontology for disease genetic investigation took 0.00010514259338378906s
Availability | VoID file availability check for Ontology for disease genetic investigation took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Ontology for disease genetic investigation took 0.1888141632080078s
Reputation | Calculation of the PageRank for Ontology for disease genetic investigation took 0.02013683319091797s
Interlinking | Calculation of Degree of Connection for Ontology for disease genetic investigation took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology for disease genetic investigation took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Ontology for disease genetic investigation took 0.0008614063262939453s
Believability | Calculation of trust value for Ontology for disease genetic investigation took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-odgi took 2.0166187286376953s
Availability | SPARQL endpoint availability check for Ontology for Genetic Interval took 8.58306884765625e-05s
Availability | VoID file availability check for Ontology for Genetic Interval took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Ontology for Genetic Interval took 0.186936616897583s
Reputation | Calculation of the PageRank for Ontology for Genetic Interval took 0.02023482322692871s
Interlinking | Calculation of Degree of Connection for Ontology for Genetic Interval took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Ontology for Genetic Interval took 0.0009417533874511719s
Interlinking | Calculation of Clustering coefficient for Ontology for Genetic Interval took 0.0009701251983642578s
Believability | Calculation of trust value for Ontology for Genetic Interval took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ogi took 1.9846067428588867s
Availability | SPARQL endpoint availability check for Ontology of Glucose Metabolism Disorder took 8.726119995117188e-05s
Availability | VoID file availability check for Ontology of Glucose Metabolism Disorder took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Ontology of Glucose Metabolism Disorder took 0.17610502243041992s
Reputation | Calculation of the PageRank for Ontology of Glucose Metabolism Disorder took 0.020108461380004883s
Interlinking | Calculation of Degree of Connection for Ontology of Glucose Metabolism Disorder took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Ontology of Glucose Metabolism Disorder took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Ontology of Glucose Metabolism Disorder took 0.00027751922607421875s
Believability | Calculation of trust value for Ontology of Glucose Metabolism Disorder took 6.508827209472656e-05s
INFO | --- Analysis for bioportal-ogmd took 1.9951071739196777s
Availability | SPARQL endpoint availability check for Ontology for General Medical Science took 8.58306884765625e-05s
Availability | VoID file availability check for Ontology for General Medical Science took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Ontology for General Medical Science took 0.18194293975830078s
Reputation | Calculation of the PageRank for Ontology for General Medical Science took 0.022281169891357422s
Interlinking | Calculation of Degree of Connection for Ontology for General Medical Science took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology for General Medical Science took 0.0007493495941162109s
Interlinking | Calculation of Clustering coefficient for Ontology for General Medical Science took 0.0006926059722900391s
Believability | Calculation of trust value for Ontology for General Medical Science took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-ogms took 1.9861316680908203s
Availability | SPARQL endpoint availability check for Online Mendelian Inheritance in Man took 8.440017700195312e-05s
Availability | VoID file availability check for Online Mendelian Inheritance in Man took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Online Mendelian Inheritance in Man took 0.18146967887878418s
Reputation | Calculation of the PageRank for Online Mendelian Inheritance in Man took 0.020154714584350586s
Interlinking | Calculation of Degree of Connection for Online Mendelian Inheritance in Man took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Online Mendelian Inheritance in Man took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Online Mendelian Inheritance in Man took 0.001138925552368164s
Believability | Calculation of trust value for Online Mendelian Inheritance in Man took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-omim took 1.977532148361206s
Availability | SPARQL endpoint availability check for Ontology for MicroRNA Target Prediction took 4.124641418457031e-05s
Availability | VoID file availability check for Ontology for MicroRNA Target Prediction took 0.0005190372467041016s
Completeness | Calculation of interlinking completeness for Ontology for MicroRNA Target Prediction took 0.18721938133239746s
Reputation | Calculation of the PageRank for Ontology for MicroRNA Target Prediction took 0.020561695098876953s
Interlinking | Calculation of Degree of Connection for Ontology for MicroRNA Target Prediction took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Ontology for MicroRNA Target Prediction took 0.0006842613220214844s
Interlinking | Calculation of Clustering coefficient for Ontology for MicroRNA Target Prediction took 0.00036644935607910156s
Believability | Calculation of trust value for Ontology for MicroRNA Target Prediction took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-omit took 2.0072004795074463s
Availability | SPARQL endpoint availability check for Ontology of Medically Related Social Entities took 8.273124694824219e-05s
Availability | VoID file availability check for Ontology of Medically Related Social Entities took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for Ontology of Medically Related Social Entities took 0.17787742614746094s
Reputation | Calculation of the PageRank for Ontology of Medically Related Social Entities took 0.02102208137512207s
Interlinking | Calculation of Degree of Connection for Ontology of Medically Related Social Entities took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Ontology of Medically Related Social Entities took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Ontology of Medically Related Social Entities took 0.0005750656127929688s
Believability | Calculation of trust value for Ontology of Medically Related Social Entities took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-omrse took 1.9782524108886719s
Availability | SPARQL endpoint availability check for Ontology of Data Mining took 4.00543212890625e-05s
Availability | VoID file availability check for Ontology of Data Mining took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for Ontology of Data Mining took 0.1836702823638916s
Reputation | Calculation of the PageRank for Ontology of Data Mining took 0.02157759666442871s
Interlinking | Calculation of Degree of Connection for Ontology of Data Mining took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Ontology of Data Mining took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Ontology of Data Mining took 0.0007486343383789062s
Believability | Calculation of trust value for Ontology of Data Mining took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-ontodm took 1.9864590167999268s
Availability | SPARQL endpoint availability check for Ontology of General Purpose Datatypes took 8.511543273925781e-05s
Availability | VoID file availability check for Ontology of General Purpose Datatypes took 0.0005486011505126953s
Completeness | Calculation of interlinking completeness for Ontology of General Purpose Datatypes took 0.17612385749816895s
Reputation | Calculation of the PageRank for Ontology of General Purpose Datatypes took 0.0216524600982666s
Interlinking | Calculation of Degree of Connection for Ontology of General Purpose Datatypes took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Ontology of General Purpose Datatypes took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Ontology of General Purpose Datatypes took 0.00023436546325683594s
Believability | Calculation of trust value for Ontology of General Purpose Datatypes took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-ontodt took 1.9590091705322266s
Availability | SPARQL endpoint availability check for Orphanet Ontology of Rare Diseases took 0.0001068115234375s
Availability | VoID file availability check for Orphanet Ontology of Rare Diseases took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Orphanet Ontology of Rare Diseases took 0.17307209968566895s
Reputation | Calculation of the PageRank for Orphanet Ontology of Rare Diseases took 0.020264625549316406s
Interlinking | Calculation of Degree of Connection for Orphanet Ontology of Rare Diseases took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Orphanet Ontology of Rare Diseases took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for Orphanet Ontology of Rare Diseases took 0.0005888938903808594s
Believability | Calculation of trust value for Orphanet Ontology of Rare Diseases took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-ontoorpha took 2.0093679428100586s
Availability | SPARQL endpoint availability check for Ontology for Parasite LifeCycle took 3.981590270996094e-05s
Availability | VoID file availability check for Ontology for Parasite LifeCycle took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for Ontology for Parasite LifeCycle took 0.1826035976409912s
Reputation | Calculation of the PageRank for Ontology for Parasite LifeCycle took 0.019978046417236328s
Interlinking | Calculation of Degree of Connection for Ontology for Parasite LifeCycle took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Ontology for Parasite LifeCycle took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Ontology for Parasite LifeCycle took 0.0009303092956542969s
Believability | Calculation of trust value for Ontology for Parasite LifeCycle took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-opl took 1.984853744506836s
Availability | SPARQL endpoint availability check for Phenotypic quality took 8.511543273925781e-05s
Availability | VoID file availability check for Phenotypic quality took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for Phenotypic quality took 0.17618942260742188s
Reputation | Calculation of the PageRank for Phenotypic quality took 0.020201444625854492s
Interlinking | Calculation of Degree of Connection for Phenotypic quality took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Phenotypic quality took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Phenotypic quality took 0.0008478164672851562s
Believability | Calculation of trust value for Phenotypic quality took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-pato took 1.9695918560028076s
Availability | SPARQL endpoint availability check for Physician Data Query took 8.320808410644531e-05s
Availability | VoID file availability check for Physician Data Query took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for Physician Data Query took 0.18125700950622559s
Reputation | Calculation of the PageRank for Physician Data Query took 0.020183801651000977s
Interlinking | Calculation of Degree of Connection for Physician Data Query took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Physician Data Query took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Physician Data Query took 0.0007812976837158203s
Believability | Calculation of trust value for Physician Data Query took 1.0967254638671875e-05s
INFO | --- Analysis for bioportal-pdq took 1.9865789413452148s
Availability | SPARQL endpoint availability check for Pediatric Terminology took 3.981590270996094e-05s
Availability | VoID file availability check for Pediatric Terminology took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Pediatric Terminology took 0.18108487129211426s
Reputation | Calculation of the PageRank for Pediatric Terminology took 0.021483898162841797s
Interlinking | Calculation of Degree of Connection for Pediatric Terminology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Pediatric Terminology took 0.0006890296936035156s
Interlinking | Calculation of Clustering coefficient for Pediatric Terminology took 0.0007805824279785156s
Believability | Calculation of trust value for Pediatric Terminology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-pedterm took 1.998495101928711s
Availability | SPARQL endpoint availability check for Parasite Experiment Ontology took 8.559226989746094e-05s
Availability | VoID file availability check for Parasite Experiment Ontology took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for Parasite Experiment Ontology took 0.18227291107177734s
Reputation | Calculation of the PageRank for Parasite Experiment Ontology took 0.021862030029296875s
Interlinking | Calculation of Degree of Connection for Parasite Experiment Ontology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Parasite Experiment Ontology took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Parasite Experiment Ontology took 0.000186920166015625s
Believability | Calculation of trust value for Parasite Experiment Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-peo took 1.9722423553466797s
Availability | SPARQL endpoint availability check for PHARE took 8.273124694824219e-05s
Availability | VoID file availability check for PHARE took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for PHARE took 0.17865824699401855s
Reputation | Calculation of the PageRank for PHARE took 0.021084070205688477s
Interlinking | Calculation of Degree of Connection for PHARE took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for PHARE took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for PHARE took 0.0006186962127685547s
Believability | Calculation of trust value for PHARE took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-phare took 1.995591402053833s
Availability | SPARQL endpoint availability check for PKO_Re took 9.34600830078125e-05s
Availability | VoID file availability check for PKO_Re took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for PKO_Re took 0.17351436614990234s
Reputation | Calculation of the PageRank for PKO_Re took 0.020923376083374023s
Interlinking | Calculation of Degree of Connection for PKO_Re took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PKO_Re took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for PKO_Re took 0.00016307830810546875s
Believability | Calculation of trust value for PKO_Re took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-pko took 1.9560978412628174s
Availability | SPARQL endpoint availability check for PMA 2010 took 8.559226989746094e-05s
Availability | VoID file availability check for PMA 2010 took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for PMA 2010 took 0.18050503730773926s
Reputation | Calculation of the PageRank for PMA 2010 took 0.02003645896911621s
Interlinking | Calculation of Degree of Connection for PMA 2010 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for PMA 2010 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for PMA 2010 took 0.0008847713470458984s
Believability | Calculation of trust value for PMA 2010 took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-pma took 2.010345458984375s
Availability | SPARQL endpoint availability check for Physical Medicine and Rehabilitation took 8.869171142578125e-05s
Availability | VoID file availability check for Physical Medicine and Rehabilitation took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Physical Medicine and Rehabilitation took 0.17693614959716797s
Reputation | Calculation of the PageRank for Physical Medicine and Rehabilitation took 0.020511627197265625s
Interlinking | Calculation of Degree of Connection for Physical Medicine and Rehabilitation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Physical Medicine and Rehabilitation took 0.0009543895721435547s
Interlinking | Calculation of Clustering coefficient for Physical Medicine and Rehabilitation took 0.00020265579223632812s
Believability | Calculation of trust value for Physical Medicine and Rehabilitation took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-pmr took 1.9901978969573975s
Availability | SPARQL endpoint availability check for Plant Anatomy took 8.344650268554688e-05s
Availability | VoID file availability check for Plant Anatomy took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Plant Anatomy took 0.17333054542541504s
Reputation | Calculation of the PageRank for Plant Anatomy took 0.0204775333404541s
Interlinking | Calculation of Degree of Connection for Plant Anatomy took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Plant Anatomy took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Plant Anatomy took 0.00038504600524902344s
Believability | Calculation of trust value for Plant Anatomy took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-po took 1.9723560810089111s
Availability | SPARQL endpoint availability check for Plant Growth and Development Stage took 8.559226989746094e-05s
Availability | VoID file availability check for Plant Growth and Development Stage took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Plant Growth and Development Stage took 0.17387723922729492s
Reputation | Calculation of the PageRank for Plant Growth and Development Stage took 0.021326303482055664s
Interlinking | Calculation of Degree of Connection for Plant Growth and Development Stage took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Plant Growth and Development Stage took 0.0008246898651123047s
Interlinking | Calculation of Clustering coefficient for Plant Growth and Development Stage took 0.00010180473327636719s
Believability | Calculation of trust value for Plant Growth and Development Stage took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-po_x1 took 2.0392251014709473s
Availability | SPARQL endpoint availability check for Plant Ontology took 4.649162292480469e-05s
Availability | VoID file availability check for Plant Ontology took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Plant Ontology took 0.1741316318511963s
Reputation | Calculation of the PageRank for Plant Ontology took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Plant Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Plant Ontology took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Plant Ontology took 0.0004277229309082031s
Believability | Calculation of trust value for Plant Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-po_x2 took 1.9798355102539062s
Availability | SPARQL endpoint availability check for PRotein Ontology (PRO) took 8.487701416015625e-05s
Availability | VoID file availability check for PRotein Ontology (PRO) took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for PRotein Ontology (PRO) took 0.17450904846191406s
Reputation | Calculation of the PageRank for PRotein Ontology (PRO) took 0.0239865779876709s
Interlinking | Calculation of Degree of Connection for PRotein Ontology (PRO) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PRotein Ontology (PRO) took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for PRotein Ontology (PRO) took 0.0006659030914306641s
Believability | Calculation of trust value for PRotein Ontology (PRO) took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-pr took 2.003981351852417s
Availability | SPARQL endpoint availability check for Proteomics data and process provenance took 4.076957702636719e-05s
Availability | VoID file availability check for Proteomics data and process provenance took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for Proteomics data and process provenance took 0.17401719093322754s
Reputation | Calculation of the PageRank for Proteomics data and process provenance took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for Proteomics data and process provenance took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Proteomics data and process provenance took 0.0008947849273681641s
Interlinking | Calculation of Clustering coefficient for Proteomics data and process provenance took 0.0003120899200439453s
Believability | Calculation of trust value for Proteomics data and process provenance took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-propreo took 1.989980936050415s
Availability | SPARQL endpoint availability check for Pathway ontology took 8.749961853027344e-05s
Availability | VoID file availability check for Pathway ontology took 0.0005321502685546875s
Completeness | Calculation of interlinking completeness for Pathway ontology took 0.1908421516418457s
Reputation | Calculation of the PageRank for Pathway ontology took 0.020420551300048828s
Interlinking | Calculation of Degree of Connection for Pathway ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Pathway ontology took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Pathway ontology took 0.00013136863708496094s
Believability | Calculation of trust value for Pathway ontology took 1.3589859008789062e-05s
INFO | --- Analysis for bioportal-pw took 2.004192352294922s
Availability | SPARQL endpoint availability check for Quantitative Imaging Biomarker Ontology took 8.463859558105469e-05s
Availability | VoID file availability check for Quantitative Imaging Biomarker Ontology took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Quantitative Imaging Biomarker Ontology took 0.17451977729797363s
Reputation | Calculation of the PageRank for Quantitative Imaging Biomarker Ontology took 0.021011829376220703s
Interlinking | Calculation of Degree of Connection for Quantitative Imaging Biomarker Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Quantitative Imaging Biomarker Ontology took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Quantitative Imaging Biomarker Ontology took 3.0517578125e-05s
Believability | Calculation of trust value for Quantitative Imaging Biomarker Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-qibo took 1.9955394268035889s
Availability | SPARQL endpoint availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 4.100799560546875e-05s
Availability | VoID file availability check for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for Read Codes, Clinical Terms Version 3 (CTV3) took 0.17564654350280762s
Reputation | Calculation of the PageRank for Read Codes, Clinical Terms Version 3 (CTV3) took 0.022008657455444336s
Interlinking | Calculation of Degree of Connection for Read Codes, Clinical Terms Version 3 (CTV3) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Read Codes, Clinical Terms Version 3 (CTV3) took 0.0017824172973632812s
Believability | Calculation of trust value for Read Codes, Clinical Terms Version 3 (CTV3) took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-rcd took 2.0018670558929443s
Availability | SPARQL endpoint availability check for Randomized Controlled Trials (RCT) Ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Randomized Controlled Trials (RCT) Ontology took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Randomized Controlled Trials (RCT) Ontology took 0.1916351318359375s
Reputation | Calculation of the PageRank for Randomized Controlled Trials (RCT) Ontology took 0.020018339157104492s
Interlinking | Calculation of Degree of Connection for Randomized Controlled Trials (RCT) Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Randomized Controlled Trials (RCT) Ontology took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Randomized Controlled Trials (RCT) Ontology took 0.0001201629638671875s
Believability | Calculation of trust value for Randomized Controlled Trials (RCT) Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-rctontology took 2.0319910049438477s
Availability | SPARQL endpoint availability check for Reproductive trait and phenotype ontology took 4.076957702636719e-05s
Availability | VoID file availability check for Reproductive trait and phenotype ontology took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Reproductive trait and phenotype ontology took 0.1803276538848877s
Reputation | Calculation of the PageRank for Reproductive trait and phenotype ontology took 0.020133256912231445s
Interlinking | Calculation of Degree of Connection for Reproductive trait and phenotype ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Reproductive trait and phenotype ontology took 0.0008838176727294922s
Interlinking | Calculation of Clustering coefficient for Reproductive trait and phenotype ontology took 0.00011157989501953125s
Believability | Calculation of trust value for Reproductive trait and phenotype ontology took 1.33514404296875e-05s
INFO | --- Analysis for bioportal-repo took 2.010089635848999s
Availability | SPARQL endpoint availability check for Physico-chemical process took 8.463859558105469e-05s
Availability | VoID file availability check for Physico-chemical process took 0.0005884170532226562s
Completeness | Calculation of interlinking completeness for Physico-chemical process took 0.18058061599731445s
Reputation | Calculation of the PageRank for Physico-chemical process took 0.020184040069580078s
Interlinking | Calculation of Degree of Connection for Physico-chemical process took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Physico-chemical process took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Physico-chemical process took 0.000186920166015625s
Believability | Calculation of trust value for Physico-chemical process took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-rex took 1.9669945240020752s
Availability | SPARQL endpoint availability check for RadLex took 8.320808410644531e-05s
Availability | VoID file availability check for RadLex took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for RadLex took 0.18836045265197754s
Reputation | Calculation of the PageRank for RadLex took 0.01992964744567871s
Interlinking | Calculation of Degree of Connection for RadLex took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for RadLex took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for RadLex took 0.0015170574188232422s
Believability | Calculation of trust value for RadLex took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-rid took 2.03940749168396s
Availability | SPARQL endpoint availability check for RNA ontology took 8.320808410644531e-05s
Availability | VoID file availability check for RNA ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for RNA ontology took 0.17941999435424805s
Reputation | Calculation of the PageRank for RNA ontology took 0.019922256469726562s
Interlinking | Calculation of Degree of Connection for RNA ontology took 7.62939453125e-06s
Interlinking | Calculation of Centrality for RNA ontology took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for RNA ontology took 0.0005335807800292969s
Believability | Calculation of trust value for RNA ontology took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-rnao took 1.9757440090179443s
Availability | SPARQL endpoint availability check for Role Ontology took 8.082389831542969e-05s
Availability | VoID file availability check for Role Ontology took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Role Ontology took 0.18597745895385742s
Reputation | Calculation of the PageRank for Role Ontology took 0.02000117301940918s
Interlinking | Calculation of Degree of Connection for Role Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Role Ontology took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Role Ontology took 0.00018906593322753906s
Believability | Calculation of trust value for Role Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-roleo took 1.9816646575927734s
Availability | SPARQL endpoint availability check for Rat Strain Ontology took 8.106231689453125e-05s
Availability | VoID file availability check for Rat Strain Ontology took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for Rat Strain Ontology took 0.1837756633758545s
Reputation | Calculation of the PageRank for Rat Strain Ontology took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for Rat Strain Ontology took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Rat Strain Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Rat Strain Ontology took 0.0001919269561767578s
Believability | Calculation of trust value for Rat Strain Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-rs took 1.996633529663086s
Availability | SPARQL endpoint availability check for RxNORM took 8.845329284667969e-05s
Availability | VoID file availability check for RxNORM took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for RxNORM took 0.1905498504638672s
Reputation | Calculation of the PageRank for RxNORM took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for RxNORM took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for RxNORM took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for RxNORM took 0.0006062984466552734s
Believability | Calculation of trust value for RxNORM took 1.430511474609375e-05s
INFO | --- Analysis for bioportal-rxnorm took 1.9997649192810059s
Availability | SPARQL endpoint availability check for Subcellular Anatomy Ontology (SAO) took 3.910064697265625e-05s
Availability | VoID file availability check for Subcellular Anatomy Ontology (SAO) took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for Subcellular Anatomy Ontology (SAO) took 0.17611122131347656s
Reputation | Calculation of the PageRank for Subcellular Anatomy Ontology (SAO) took 0.021909713745117188s
Interlinking | Calculation of Degree of Connection for Subcellular Anatomy Ontology (SAO) took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Subcellular Anatomy Ontology (SAO) took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Subcellular Anatomy Ontology (SAO) took 0.0010225772857666016s
Believability | Calculation of trust value for Subcellular Anatomy Ontology (SAO) took 3.0517578125e-05s
INFO | --- Analysis for bioportal-sao took 2.063915967941284s
Availability | SPARQL endpoint availability check for Systems Biology took 4.00543212890625e-05s
Availability | VoID file availability check for Systems Biology took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Systems Biology took 0.1802058219909668s
Reputation | Calculation of the PageRank for Systems Biology took 0.019991636276245117s
Interlinking | Calculation of Degree of Connection for Systems Biology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Systems Biology took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Systems Biology took 0.0004439353942871094s
Believability | Calculation of trust value for Systems Biology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-sbo took 1.982433557510376s
Availability | SPARQL endpoint availability check for Smoking Behavior Risk Ontology took 0.00012755393981933594s
Availability | VoID file availability check for Smoking Behavior Risk Ontology took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Smoking Behavior Risk Ontology took 0.17774081230163574s
Reputation | Calculation of the PageRank for Smoking Behavior Risk Ontology took 0.02019333839416504s
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.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Smoking Behavior Risk Ontology took 0.00010347366333007812s
Believability | Calculation of trust value for Smoking Behavior Risk Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-sbro took 1.9913196563720703s
Availability | SPARQL endpoint availability check for Sleep Domain Ontology took 8.511543273925781e-05s
Availability | VoID file availability check for Sleep Domain Ontology took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for Sleep Domain Ontology took 0.1748034954071045s
Reputation | Calculation of the PageRank for Sleep Domain Ontology took 0.020145893096923828s
Interlinking | Calculation of Degree of Connection for Sleep Domain Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Sleep Domain Ontology took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Sleep Domain Ontology took 0.001316070556640625s
Believability | Calculation of trust value for Sleep Domain Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-sdo took 1.9939730167388916s
Availability | SPARQL endpoint availability check for Sample processing and separation techniques took 9.059906005859375e-05s
Availability | VoID file availability check for Sample processing and separation techniques took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Sample processing and separation techniques took 0.17501449584960938s
Reputation | Calculation of the PageRank for Sample processing and separation techniques took 0.02009129524230957s
Interlinking | Calculation of Degree of Connection for Sample processing and separation techniques took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sample processing and separation techniques took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Sample processing and separation techniques took 0.0003592967987060547s
Believability | Calculation of trust value for Sample processing and separation techniques took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-sep took 1.976562261581421s
Availability | SPARQL endpoint availability check for Student Health Record took 8.440017700195312e-05s
Availability | VoID file availability check for Student Health Record took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Student Health Record took 0.17947602272033691s
Reputation | Calculation of the PageRank for Student Health Record took 0.020133495330810547s
Interlinking | Calculation of Degree of Connection for Student Health Record took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Student Health Record took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Student Health Record took 0.0004410743713378906s
Believability | Calculation of trust value for Student Health Record took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-shr took 1.972130298614502s
Availability | SPARQL endpoint availability check for SemanticScience Integrated Ontology took 8.749961853027344e-05s
Availability | VoID file availability check for SemanticScience Integrated Ontology took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for SemanticScience Integrated Ontology took 0.1778271198272705s
Reputation | Calculation of the PageRank for SemanticScience Integrated Ontology took 0.02051258087158203s
Interlinking | Calculation of Degree of Connection for SemanticScience Integrated Ontology took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SemanticScience Integrated Ontology took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for SemanticScience Integrated Ontology took 0.0012660026550292969s
Believability | Calculation of trust value for SemanticScience Integrated Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-sio took 1.9919004440307617s
Availability | SPARQL endpoint availability check for Situation-Based Access Control took 8.392333984375e-05s
Availability | VoID file availability check for Situation-Based Access Control took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Situation-Based Access Control took 0.19313764572143555s
Reputation | Calculation of the PageRank for Situation-Based Access Control took 0.0200040340423584s
Interlinking | Calculation of Degree of Connection for Situation-Based Access Control took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Situation-Based Access Control took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Situation-Based Access Control took 0.00019407272338867188s
Believability | Calculation of trust value for Situation-Based Access Control took 7.62939453125e-06s
INFO | --- Analysis for bioportal-sitbac took 2.0284059047698975s
Availability | SPARQL endpoint availability check for SNOMED Clinical Terms took 0.00010704994201660156s
Availability | VoID file availability check for SNOMED Clinical Terms took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for SNOMED Clinical Terms took 0.17922639846801758s
Reputation | Calculation of the PageRank for SNOMED Clinical Terms took 0.020067214965820312s
Interlinking | Calculation of Degree of Connection for SNOMED Clinical Terms took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SNOMED Clinical Terms took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for SNOMED Clinical Terms took 0.0019567012786865234s
Believability | Calculation of trust value for SNOMED Clinical Terms took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-snomedct took 1.9724266529083252s
Availability | SPARQL endpoint availability check for SNP-Ontology took 9.608268737792969e-05s
Availability | VoID file availability check for SNP-Ontology took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for SNP-Ontology took 0.17550063133239746s
Reputation | Calculation of the PageRank for SNP-Ontology took 0.01999521255493164s
Interlinking | Calculation of Degree of Connection for SNP-Ontology took 7.62939453125e-06s
Interlinking | Calculation of Centrality for SNP-Ontology took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for SNP-Ontology took 0.0006656646728515625s
Believability | Calculation of trust value for SNP-Ontology took 6.9141387939453125e-06s
INFO | --- Analysis for bioportal-snpo took 1.9513816833496094s
Availability | SPARQL endpoint availability check for Sequence types and features took 4.100799560546875e-05s
Availability | VoID file availability check for Sequence types and features took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Sequence types and features took 0.1846311092376709s
Reputation | Calculation of the PageRank for Sequence types and features took 0.020002126693725586s
Interlinking | Calculation of Degree of Connection for Sequence types and features took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Sequence types and features took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Sequence types and features took 0.0005660057067871094s
Believability | Calculation of trust value for Sequence types and features took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-so_x1 took 2.0017359256744385s
Availability | SPARQL endpoint availability check for Suggested Ontology for Pharmacogenomics took 4.029273986816406e-05s
Availability | VoID file availability check for Suggested Ontology for Pharmacogenomics took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Suggested Ontology for Pharmacogenomics took 0.18309903144836426s
Reputation | Calculation of the PageRank for Suggested Ontology for Pharmacogenomics took 0.019999980926513672s
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.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Suggested Ontology for Pharmacogenomics took 0.0015499591827392578s
Believability | Calculation of trust value for Suggested Ontology for Pharmacogenomics took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-sopharm took 1.9740846157073975s
Availability | SPARQL endpoint availability check for SoyOntology took 4.00543212890625e-05s
Availability | VoID file availability check for SoyOntology took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for SoyOntology took 0.17525982856750488s
Reputation | Calculation of the PageRank for SoyOntology took 0.02030777931213379s
Interlinking | Calculation of Degree of Connection for SoyOntology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SoyOntology took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for SoyOntology took 0.0001251697540283203s
Believability | Calculation of trust value for SoyOntology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-soy took 1.9815130233764648s
Availability | SPARQL endpoint availability check for Spider Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for Spider Ontology took 0.00024199485778808594s
Completeness | Calculation of interlinking completeness for Spider Ontology took 0.172377347946167s
Reputation | Calculation of the PageRank for Spider Ontology took 0.02154684066772461s
Interlinking | Calculation of Degree of Connection for Spider Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Spider Ontology took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Spider Ontology took 0.00035572052001953125s
Believability | Calculation of trust value for Spider Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-spd took 1.950566053390503s
Availability | SPARQL endpoint availability check for Solanaceae Phenotype Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Solanaceae Phenotype Ontology took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for Solanaceae Phenotype Ontology took 0.17319798469543457s
Reputation | Calculation of the PageRank for Solanaceae Phenotype Ontology took 0.020279884338378906s
Interlinking | Calculation of Degree of Connection for Solanaceae Phenotype Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Solanaceae Phenotype Ontology took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Solanaceae Phenotype Ontology took 0.00026607513427734375s
Believability | Calculation of trust value for Solanaceae Phenotype Ontology took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-spto took 1.975128412246704s
Availability | SPARQL endpoint availability check for Syndromic Surveillance Ontology took 8.797645568847656e-05s
Availability | VoID file availability check for Syndromic Surveillance Ontology took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Syndromic Surveillance Ontology took 0.17375636100769043s
Reputation | Calculation of the PageRank for Syndromic Surveillance Ontology took 0.019953250885009766s
Interlinking | Calculation of Degree of Connection for Syndromic Surveillance Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Syndromic Surveillance Ontology took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Syndromic Surveillance Ontology took 0.0004284381866455078s
Believability | Calculation of trust value for Syndromic Surveillance Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for bioportal-sso took 2.0045387744903564s
Availability | SPARQL endpoint availability check for Software Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Software Ontology took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Software Ontology took 0.17437982559204102s
Reputation | Calculation of the PageRank for Software Ontology took 0.020137548446655273s
Interlinking | Calculation of Degree of Connection for Software Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Software Ontology took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Software Ontology took 0.00040149688720703125s
Believability | Calculation of trust value for Software Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-swo took 1.9806716442108154s
Availability | SPARQL endpoint availability check for Tick gross anatomy took 8.320808410644531e-05s
Availability | VoID file availability check for Tick gross anatomy took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for Tick gross anatomy took 0.18231558799743652s
Reputation | Calculation of the PageRank for Tick gross anatomy took 0.021968603134155273s
Interlinking | Calculation of Degree of Connection for Tick gross anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Tick gross anatomy took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Tick gross anatomy took 0.00023555755615234375s
Believability | Calculation of trust value for Tick gross anatomy took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-tads took 1.962519884109497s
Availability | SPARQL endpoint availability check for Teleost Anatomy Ontology took 7.987022399902344e-05s
Availability | VoID file availability check for Teleost Anatomy Ontology took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Teleost Anatomy Ontology took 0.17912817001342773s
Reputation | Calculation of the PageRank for Teleost Anatomy Ontology took 0.021883487701416016s
Interlinking | Calculation of Degree of Connection for Teleost Anatomy Ontology took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Teleost Anatomy Ontology took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Teleost Anatomy Ontology took 0.0008764266967773438s
Believability | Calculation of trust value for Teleost Anatomy Ontology took 7.867813110351562e-06s
INFO | --- Analysis for bioportal-tao took 1.9989898204803467s
Availability | SPARQL endpoint availability check for Taxonomic rank vocabulary took 4.0531158447265625e-05s
Availability | VoID file availability check for Taxonomic rank vocabulary took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for Taxonomic rank vocabulary took 0.17984771728515625s
Reputation | Calculation of the PageRank for Taxonomic rank vocabulary took 0.019945621490478516s
Interlinking | Calculation of Degree of Connection for Taxonomic rank vocabulary took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Taxonomic rank vocabulary took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Taxonomic rank vocabulary took 8.320808410644531e-05s
Believability | Calculation of trust value for Taxonomic rank vocabulary took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-taxrank took 2.009768486022949s
Availability | SPARQL endpoint availability check for Terminology for the Description of Dynamics took 8.296966552734375e-05s
Availability | VoID file availability check for Terminology for the Description of Dynamics took 0.0002338886260986328s
Completeness | Calculation of interlinking completeness for Terminology for the Description of Dynamics took 0.17835664749145508s
Reputation | Calculation of the PageRank for Terminology for the Description of Dynamics took 0.022341489791870117s
Interlinking | Calculation of Degree of Connection for Terminology for the Description of Dynamics took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Terminology for the Description of Dynamics took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Terminology for the Description of Dynamics took 7.009506225585938e-05s
Believability | Calculation of trust value for Terminology for the Description of Dynamics took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-teddy took 1.9825255870819092s
Availability | SPARQL endpoint availability check for Time Event Ontology took 4.0531158447265625e-05s
Availability | VoID file availability check for Time Event Ontology took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for Time Event Ontology took 0.17471909523010254s
Reputation | Calculation of the PageRank for Time Event Ontology took 0.0200197696685791s
Interlinking | Calculation of Degree of Connection for Time Event Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Time Event Ontology took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Time Event Ontology took 0.0007874965667724609s
Believability | Calculation of trust value for Time Event Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-teo took 1.9637033939361572s
Availability | SPARQL endpoint availability check for Mosquito gross anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for Mosquito gross anatomy took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Mosquito gross anatomy took 0.18129444122314453s
Reputation | Calculation of the PageRank for Mosquito gross anatomy took 0.022472858428955078s
Interlinking | Calculation of Degree of Connection for Mosquito gross anatomy took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mosquito gross anatomy took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Mosquito gross anatomy took 0.00037932395935058594s
Believability | Calculation of trust value for Mosquito gross anatomy took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-tgma took 2.0127594470977783s
Availability | SPARQL endpoint availability check for thesaurus took 4.291534423828125e-05s
Availability | VoID file availability check for thesaurus took 0.0004911422729492188s
Completeness | Calculation of interlinking completeness for thesaurus took 0.18006348609924316s
Reputation | Calculation of the PageRank for thesaurus took 0.019926786422729492s
Interlinking | Calculation of Degree of Connection for thesaurus took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for thesaurus took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for thesaurus took 6.651878356933594e-05s
Believability | Calculation of trust value for thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for bioportal-thesaurus took 1.9851171970367432s
Availability | SPARQL endpoint availability check for Traditional Medicine Signs and Symptoms Value Set took 8.845329284667969e-05s
Availability | VoID file availability check for Traditional Medicine Signs and Symptoms Value Set took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for Traditional Medicine Signs and Symptoms Value Set took 0.18473601341247559s
Reputation | Calculation of the PageRank for Traditional Medicine Signs and Symptoms Value Set took 0.02006816864013672s
Interlinking | Calculation of Degree of Connection for Traditional Medicine Signs and Symptoms Value Set took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Traditional Medicine Signs and Symptoms Value Set took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Traditional Medicine Signs and Symptoms Value Set took 0.0003464221954345703s
Believability | Calculation of trust value for Traditional Medicine Signs and Symptoms Value Set took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-tm-signs-and-sympts took 2.0522589683532715s
Availability | SPARQL endpoint availability check for Translational Medicine Ontology took 8.153915405273438e-05s
Availability | VoID file availability check for Translational Medicine Ontology took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Translational Medicine Ontology took 0.1703500747680664s
Reputation | Calculation of the PageRank for Translational Medicine Ontology took 0.021128177642822266s
Interlinking | Calculation of Degree of Connection for Translational Medicine Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Translational Medicine Ontology took 0.0007371902465820312s
Interlinking | Calculation of Clustering coefficient for Translational Medicine Ontology took 0.0008265972137451172s
Believability | Calculation of trust value for Translational Medicine Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-tmo took 1.9708490371704102s
Availability | SPARQL endpoint availability check for Plant Trait Ontology took 8.368492126464844e-05s
Availability | VoID file availability check for Plant Trait Ontology took 0.0002562999725341797s
Completeness | Calculation of interlinking completeness for Plant Trait Ontology took 0.1886453628540039s
Reputation | Calculation of the PageRank for Plant Trait Ontology took 0.021727800369262695s
Interlinking | Calculation of Degree of Connection for Plant Trait Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Plant Trait Ontology took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Plant Trait Ontology took 0.00015783309936523438s
Believability | Calculation of trust value for Plant Trait Ontology took 7.62939453125e-06s
INFO | --- Analysis for bioportal-to took 2.013918876647949s
Availability | SPARQL endpoint availability check for TOK_Ontology took 8.678436279296875e-05s
Availability | VoID file availability check for TOK_Ontology took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for TOK_Ontology took 0.18439745903015137s
Reputation | Calculation of the PageRank for TOK_Ontology took 0.020029067993164062s
Interlinking | Calculation of Degree of Connection for TOK_Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for TOK_Ontology took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for TOK_Ontology took 0.00018596649169921875s
Believability | Calculation of trust value for TOK_Ontology took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-tok took 1.9811737537384033s
Availability | SPARQL endpoint availability check for Teleost taxonomy took 4.0531158447265625e-05s
Availability | VoID file availability check for Teleost taxonomy took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Teleost taxonomy took 0.1754167079925537s
Reputation | Calculation of the PageRank for Teleost taxonomy took 0.020296096801757812s
Interlinking | Calculation of Degree of Connection for Teleost taxonomy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Teleost taxonomy took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Teleost taxonomy took 0.00019168853759765625s
Believability | Calculation of trust value for Teleost taxonomy took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-tto took 1.9796502590179443s
Availability | SPARQL endpoint availability check for Uber anatomy ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Uber anatomy ontology took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Uber anatomy ontology took 0.17881178855895996s
Reputation | Calculation of the PageRank for Uber anatomy ontology took 0.019884586334228516s
Interlinking | Calculation of Degree of Connection for Uber anatomy ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Uber anatomy ontology took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Uber anatomy ontology took 0.0010294914245605469s
Believability | Calculation of trust value for Uber anatomy ontology took 1.2159347534179688e-05s
INFO | --- Analysis for bioportal-uberon took 1.962784767150879s
Availability | SPARQL endpoint availability check for Units Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Units Ontology took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Units Ontology took 0.174119234085083s
Reputation | Calculation of the PageRank for Units Ontology took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for Units Ontology took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Units Ontology took 0.0009281635284423828s
Interlinking | Calculation of Clustering coefficient for Units Ontology took 0.00026106834411621094s
Believability | Calculation of trust value for Units Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-unitsontology took 1.98294997215271s
Availability | SPARQL endpoint availability check for Units of measurement took 4.100799560546875e-05s
Availability | VoID file availability check for Units of measurement took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Units of measurement took 0.17169570922851562s
Reputation | Calculation of the PageRank for Units of measurement took 0.020500898361206055s
Interlinking | Calculation of Degree of Connection for Units of measurement took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Units of measurement took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Units of measurement took 0.00028324127197265625s
Believability | Calculation of trust value for Units of measurement took 1.2636184692382812e-05s
INFO | --- Analysis for bioportal-uo took 1.9764454364776611s
Availability | SPARQL endpoint availability check for VANDF took 8.463859558105469e-05s
Availability | VoID file availability check for VANDF took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for VANDF took 0.17988252639770508s
Reputation | Calculation of the PageRank for VANDF took 0.020215749740600586s
Interlinking | Calculation of Degree of Connection for VANDF took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for VANDF took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for VANDF took 0.0006806850433349609s
Believability | Calculation of trust value for VANDF took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-vandf took 1.9946644306182861s
Availability | SPARQL endpoint availability check for Vertebrate Anatomy Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Vertebrate Anatomy Ontology took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for Vertebrate Anatomy Ontology took 0.1949629783630371s
Reputation | Calculation of the PageRank for Vertebrate Anatomy Ontology took 0.020017147064208984s
Interlinking | Calculation of Degree of Connection for Vertebrate Anatomy Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Vertebrate Anatomy Ontology took 0.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for Vertebrate Anatomy Ontology took 0.0004215240478515625s
Believability | Calculation of trust value for Vertebrate Anatomy Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-vao took 2.017348051071167s
Availability | SPARQL endpoint availability check for vertebrate Homologous Organ Groups took 8.249282836914062e-05s
Availability | VoID file availability check for vertebrate Homologous Organ Groups took 0.0004975795745849609s
Completeness | Calculation of interlinking completeness for vertebrate Homologous Organ Groups took 0.17324495315551758s
Reputation | Calculation of the PageRank for vertebrate Homologous Organ Groups took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for vertebrate Homologous Organ Groups took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for vertebrate Homologous Organ Groups took 0.0009052753448486328s
Interlinking | Calculation of Clustering coefficient for vertebrate Homologous Organ Groups took 0.0006902217864990234s
Believability | Calculation of trust value for vertebrate Homologous Organ Groups took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-vhog took 1.9706242084503174s
Availability | SPARQL endpoint availability check for VIVO took 3.933906555175781e-05s
Availability | VoID file availability check for VIVO took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for VIVO took 0.18042254447937012s
Reputation | Calculation of the PageRank for VIVO took 0.020664215087890625s
Interlinking | Calculation of Degree of Connection for VIVO took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for VIVO took 0.0003428459167480469s
Believability | Calculation of trust value for VIVO took 1.1444091796875e-05s
INFO | --- Analysis for bioportal-vivo took 1.9703264236450195s
Availability | SPARQL endpoint availability check for Vaccine Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Vaccine Ontology took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Vaccine Ontology took 0.1904914379119873s
Reputation | Calculation of the PageRank for Vaccine Ontology took 0.020004987716674805s
Interlinking | Calculation of Degree of Connection for Vaccine Ontology took 7.3909759521484375e-06s
Interlinking | Calculation of Centrality for Vaccine Ontology took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Vaccine Ontology took 0.0012226104736328125s
Believability | Calculation of trust value for Vaccine Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for bioportal-vo took 1.9812986850738525s
Availability | SPARQL endpoint availability check for Vertebrate Trait Ontology took 8.273124694824219e-05s
Availability | VoID file availability check for Vertebrate Trait Ontology took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Vertebrate Trait Ontology took 0.17614507675170898s
Reputation | Calculation of the PageRank for Vertebrate Trait Ontology took 0.02006673812866211s
Interlinking | Calculation of Degree of Connection for Vertebrate Trait Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vertebrate Trait Ontology took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Vertebrate Trait Ontology took 0.0002014636993408203s
Believability | Calculation of trust value for Vertebrate Trait Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-vt took 1.966254711151123s
Availability | SPARQL endpoint availability check for C. elegans gross anatomy took 4.029273986816406e-05s
Availability | VoID file availability check for C. elegans gross anatomy took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for C. elegans gross anatomy took 0.18445348739624023s
Reputation | Calculation of the PageRank for C. elegans gross anatomy took 0.02019786834716797s
Interlinking | Calculation of Degree of Connection for C. elegans gross anatomy took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for C. elegans gross anatomy took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for C. elegans gross anatomy took 0.00048661231994628906s
Believability | Calculation of trust value for C. elegans gross anatomy took 1.1682510375976562e-05s
INFO | --- Analysis for bioportal-wbbt took 2.0085623264312744s
Availability | SPARQL endpoint availability check for C. elegans development took 4.029273986816406e-05s
Availability | VoID file availability check for C. elegans development took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for C. elegans development took 0.17210602760314941s
Reputation | Calculation of the PageRank for C. elegans development took 0.022977828979492188s
Interlinking | Calculation of Degree of Connection for C. elegans development took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for C. elegans development took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for C. elegans development took 4.267692565917969e-05s
Believability | Calculation of trust value for C. elegans development took 1.2874603271484375e-05s
INFO | --- Analysis for bioportal-wbls took 1.9818549156188965s
Availability | SPARQL endpoint availability check for C. elegans phenotype took 4.2438507080078125e-05s
Availability | VoID file availability check for C. elegans phenotype took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for C. elegans phenotype took 0.17548131942749023s
Reputation | Calculation of the PageRank for C. elegans phenotype took 0.02125382423400879s
Interlinking | Calculation of Degree of Connection for C. elegans phenotype took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for C. elegans phenotype took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for C. elegans phenotype took 8.630752563476562e-05s
Believability | Calculation of trust value for C. elegans phenotype took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-wbphenotype took 2.0082545280456543s
Availability | SPARQL endpoint availability check for WHO Adverse Reaction Terminology took 8.916854858398438e-05s
Availability | VoID file availability check for WHO Adverse Reaction Terminology took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for WHO Adverse Reaction Terminology took 0.18749713897705078s
Reputation | Calculation of the PageRank for WHO Adverse Reaction Terminology took 0.022067785263061523s
Interlinking | Calculation of Degree of Connection for WHO Adverse Reaction Terminology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for WHO Adverse Reaction Terminology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for WHO Adverse Reaction Terminology took 0.0005705356597900391s
Believability | Calculation of trust value for WHO Adverse Reaction Terminology took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-who took 2.0284690856933594s
Availability | SPARQL endpoint availability check for Xenopus anatomy and development took 5.078315734863281e-05s
Availability | VoID file availability check for Xenopus anatomy and development took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for Xenopus anatomy and development took 0.18613600730895996s
Reputation | Calculation of the PageRank for Xenopus anatomy and development took 0.02228069305419922s
Interlinking | Calculation of Degree of Connection for Xenopus anatomy and development took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Xenopus anatomy and development took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Xenopus anatomy and development took 0.0006711483001708984s
Believability | Calculation of trust value for Xenopus anatomy and development took 8.106231689453125e-06s
INFO | --- Analysis for bioportal-xao took 1.9857192039489746s
Availability | SPARQL endpoint availability check for Experimental Conditions Ontology took 9.560585021972656e-05s
Availability | VoID file availability check for Experimental Conditions Ontology took 0.0005164146423339844s
Completeness | Calculation of interlinking completeness for Experimental Conditions Ontology took 0.17259550094604492s
Reputation | Calculation of the PageRank for Experimental Conditions Ontology took 0.02210712432861328s
Interlinking | Calculation of Degree of Connection for Experimental Conditions Ontology took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Experimental Conditions Ontology took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Experimental Conditions Ontology took 0.00023818016052246094s
Believability | Calculation of trust value for Experimental Conditions Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for bioportal-xco took 1.9671523571014404s
Availability | SPARQL endpoint availability check for Yeast phenotypes took 8.249282836914062e-05s
Availability | VoID file availability check for Yeast phenotypes took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Yeast phenotypes took 0.17296314239501953s
Reputation | Calculation of the PageRank for Yeast phenotypes took 0.020065784454345703s
Interlinking | Calculation of Degree of Connection for Yeast phenotypes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Yeast phenotypes took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Yeast phenotypes took 0.0002579689025878906s
Believability | Calculation of trust value for Yeast phenotypes took 1.049041748046875e-05s
INFO | --- Analysis for bioportal-ypo took 1.9753258228302002s
Availability | SPARQL endpoint availability check for Zebrafish anatomy and development took 8.130073547363281e-05s
Availability | VoID file availability check for Zebrafish anatomy and development took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for Zebrafish anatomy and development took 0.18211960792541504s
Reputation | Calculation of the PageRank for Zebrafish anatomy and development took 0.021404743194580078s
Interlinking | Calculation of Degree of Connection for Zebrafish anatomy and development took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Zebrafish anatomy and development took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Zebrafish anatomy and development took 0.0007722377777099609s
Believability | Calculation of trust value for Zebrafish anatomy and development took 1.1920928955078125e-05s
INFO | --- Analysis for bioportal-zfa took 1.9949002265930176s
Availability | SPARQL endpoint availability check for Indian Terrorism Ontology (InTO) took 9.632110595703125e-05s
Availability | VoID file availability check for Indian Terrorism Ontology (InTO) took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Indian Terrorism Ontology (InTO) took 0.17513084411621094s
Reputation | Calculation of the PageRank for Indian Terrorism Ontology (InTO) took 0.020238876342773438s
Interlinking | Calculation of Degree of Connection for Indian Terrorism Ontology (InTO) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Indian Terrorism Ontology (InTO) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Indian Terrorism Ontology (InTO) took 2.7179718017578125e-05s
Believability | Calculation of trust value for Indian Terrorism Ontology (InTO) took 1.1205673217773438e-05s
INFO | --- Analysis for Bioportal_link took 1.983041763305664s
Availability | SPARQL endpoint availability check for BioSamples RDF took 8.225440979003906e-05s
Availability | VoID file availability check for BioSamples RDF took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for BioSamples RDF took 0.18723464012145996s
Reputation | Calculation of the PageRank for BioSamples RDF took 0.020761966705322266s
Interlinking | Calculation of Degree of Connection for BioSamples RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BioSamples RDF took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for BioSamples RDF took 3.314018249511719e-05s
Believability | Calculation of trust value for BioSamples RDF took 1.239776611328125e-05s
INFO | --- Analysis for biosamples-rdf took 1.9920814037322998s
Availability | SPARQL endpoint availability check for Bank for International Settlements (BIS) Linked Data took 8.273124694824219e-05s
Availability | VoID file availability check for Bank for International Settlements (BIS) Linked Data took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for Bank for International Settlements (BIS) Linked Data took 0.17094850540161133s
Reputation | Calculation of the PageRank for Bank for International Settlements (BIS) Linked Data took 0.029132604598999023s
Interlinking | Calculation of Degree of Connection for Bank for International Settlements (BIS) Linked Data took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Bank for International Settlements (BIS) Linked Data took 0.0015368461608886719s
Interlinking | Calculation of Clustering coefficient for Bank for International Settlements (BIS) Linked Data took 0.00016355514526367188s
Believability | Calculation of trust value for Bank for International Settlements (BIS) Linked Data took 9.059906005859375e-06s
INFO | --- Analysis for bis-linked-data took 1.961787462234497s
Availability | SPARQL endpoint availability check for Bitzi took 9.036064147949219e-05s
Availability | VoID file availability check for Bitzi took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Bitzi took 0.17438840866088867s
Reputation | Calculation of the PageRank for Bitzi took 0.020071029663085938s
Interlinking | Calculation of Degree of Connection for Bitzi took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bitzi took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Bitzi took 2.8371810913085938e-05s
Believability | Calculation of trust value for Bitzi took 1.2636184692382812e-05s
INFO | --- Analysis for bitzi took 1.99395751953125s
Availability | SPARQL endpoint availability check for BizkaiSense took 8.487701416015625e-05s
Availability | VoID file availability check for BizkaiSense took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for BizkaiSense took 0.1815958023071289s
Reputation | Calculation of the PageRank for BizkaiSense took 0.02015519142150879s
Interlinking | Calculation of Degree of Connection for BizkaiSense took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BizkaiSense took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for BizkaiSense took 2.86102294921875e-05s
Believability | Calculation of trust value for BizkaiSense took 1.2636184692382812e-05s
INFO | --- Analysis for bizkaisense took 1.9832940101623535s
Availability | SPARQL endpoint availability check for blabla.itemlist took 3.933906555175781e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.17972588539123535s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.02002239227294922s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007474422454833984s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.86102294921875e-05s
Believability | Calculation of trust value for blabla.itemlist took 7.3909759521484375e-06s
INFO | --- Analysis for blabla-itemlist took 1.9933421611785889s
Availability | SPARQL endpoint availability check for blabla.itemlist took 9.417533874511719e-05s
Availability | VoID file availability check for blabla.itemlist took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for blabla.itemlist took 0.17923235893249512s
Reputation | Calculation of the PageRank for blabla.itemlist took 0.020165205001831055s
Interlinking | Calculation of Degree of Connection for blabla.itemlist took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for blabla.itemlist took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for blabla.itemlist took 2.765655517578125e-05s
Believability | Calculation of trust value for blabla.itemlist took 1.1444091796875e-05s
INFO | --- Analysis for blabla_itemlist took 1.951359510421753s
Availability | SPARQL endpoint availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.981590270996094e-05s
Availability | VoID file availability check for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.18104910850524902s
Reputation | Calculation of the PageRank for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.021385669708251953s
Interlinking | Calculation of Degree of Connection for Bibliography of Linguistic Literature (BLL) Thesaurus took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Bibliography of Linguistic Literature (BLL) Thesaurus took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Bibliography of Linguistic Literature (BLL) Thesaurus took 3.600120544433594e-05s
Believability | Calculation of trust value for Bibliography of Linguistic Literature (BLL) Thesaurus took 1.1205673217773438e-05s
INFO | --- Analysis for bll-thesaurus took 1.9686670303344727s
Availability | SPARQL endpoint availability check for British National Bibliography (BNB) - Linked Open Data took 1.8333063125610352s
Availability | VoID file availability check for British National Bibliography (BNB) - Linked Open Data took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for British National Bibliography (BNB) - Linked Open Data took 0.18105602264404297s
Reputation | Calculation of the PageRank for British National Bibliography (BNB) - Linked Open Data took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for British National Bibliography (BNB) - Linked Open Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for British National Bibliography (BNB) - Linked Open Data took 0.0006902217864990234s
Interlinking | Calculation of Clustering coefficient for British National Bibliography (BNB) - Linked Open Data took 6.222724914550781e-05s
Believability | Calculation of trust value for British National Bibliography (BNB) - Linked Open Data took 1.239776611328125e-05s
INFO | --- Analysis for bluk-bnb took 3.964733600616455s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 0.4043607711791992s
Availability | VoID file availability check for Thesaurus BNCF took 0.0005002021789550781s
Extra | Recovery of all triples for Thesaurus BNCF took 45.41922879219055s
Performance | Total latancy measurement for Thesaurus BNCF took 0.7284934520721436s
Amount of data | Number of triples check for Thesaurus BNCF took 0.694023847579956s
Interoperability | New terms check for Thesaurus BNCF took 1.5039772987365723s
Versatility | Languages check for Thesaurus BNCF took 6.5530312061309814s
Interpretability | Number of blank nodes check for Thesaurus BNCF took 0.891686201095581s
Security | Check HTTPS for Thesaurus BNCF took 0.1041109561920166s
Interpretability | RDF structures check for Thesaurus BNCF took 0.1419529914855957s
Versatility | Serialization formats check for Thesaurus BNCF took 0.1422715187072754s
Availability | RDF dump link check for Thesaurus BNCF took 0.1392662525177002s
License | MR license check for Thesaurus BNCF took 0.14311909675598145s
License | HR license check for Thesaurus BNCF took 0.2231431007385254s
Amount of data | Number of property check for Thesaurus BNCF took 0.14110088348388672s
Understandability | Number of label check for Thesaurus BNCF took 0.2785654067993164s
Understandability | URI regex check for Thesaurus BNCF took 0.27587199211120605s
Understandability | Vocabs check for Thesaurus BNCF took 0.1409313678741455s
Verifiability | Authors check for Thesaurus BNCF took 0.14170098304748535s
Verifiability | Publishers check for Thesaurus BNCF took 0.14106392860412598s
Performance | Throughput check for Thesaurus BNCF took 10.694360494613647s
Amount of data | Check the number of entities for Thesaurus BNCF took 7.200241088867188e-05s
Verifiability | Contribs. check for Thesaurus BNCF took 0.1452322006225586s
Interlinking | sameAs chians check for Thesaurus BNCF took 0.1437060832977295s
Interlinking | skos check for Thesaurus BNCF took 0.21719765663146973s
Interlinking | skos check for Thesaurus BNCF took 0.16854166984558105s
Timeliness | dataset update frequency check for Thesaurus BNCF took 0.14552712440490723s
Currency | Creation date check for Thesaurus BNCF took 0.31215357780456543s
Currency | Modification date check for Thesaurus BNCF took 0.28792333602905273s
Rep.Conc. | URIs length for Thesaurus BNCF took 24.86584210395813s
Interoperability | New vocabularies check for Thesaurus BNCF took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for Thesaurus BNCF took 0.1397705078125s
Accuracy | Check Functional Property for Thesaurus BNCF took 0.13754653930664062s
Accuracy | Check Inverse Functional Property for Thesaurus BNCF took 0.1869657039642334s
Accuracy | Check Empty annotation labels for Thesaurus BNCF took 11.576280355453491s
Accuracy | Check White space in annotation for Thesaurus BNCF took 0.4889676570892334s
Accuracy | Check Datatype consistency for Thesaurus BNCF took 3.7846620082855225s
Consistency | Disjoint class check for Thesaurus BNCF took 0.14062833786010742s
Consistency | Check Misplaced properties for Thesaurus BNCF took 0.9557068347930908s
Consistency | Misplaced classes for Thesaurus BNCF took 6.618060111999512s
Consistency | Check Ontology hijacking for Thesaurus BNCF took 7.260885715484619s
Consistency | Check Invalid usage of undefined classes for Thesaurus BNCF took 1.400102138519287s
Consistency | Check Invalid usage of undefined properties for Thesaurus BNCF took 2.2061398029327393s
Conciseness | Check Extensional conciseness for Thesaurus BNCF took 2.3663113117218018s
Security | Sign check for Thesaurus BNCF took 0.1401669979095459s
Availability | Check URIs Dereferenciability for Thesaurus BNCF took 21.720258474349976s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.19639348983764648s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.020040035247802734s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0006804466247558594s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 6.628036499023438e-05s
Interoperability | Check the re-using of existing vocabs for Thesaurus BNCF took 1.6689300537109375e-06s
Believability | Calculation of trust value for Thesaurus BNCF took 5.4836273193359375e-06s
INFO | --- Analysis for bncf-ns took 174.676331281662s
Availability | SPARQL endpoint availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.34600830078125e-05s
Availability | VoID file availability check for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.1856844425201416s
Reputation | Calculation of the PageRank for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.01978588104248047s
Interlinking | Calculation of Degree of Connection for BPR ? Bibliography of the Italian Parliament and electoral studies took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for BPR ? Bibliography of the Italian Parliament and electoral studies took 0.0006849765777587891s
Interlinking | Calculation of Clustering coefficient for BPR ? Bibliography of the Italian Parliament and electoral studies took 3.790855407714844e-05s
Believability | Calculation of trust value for BPR ? Bibliography of the Italian Parliament and electoral studies took 1.1205673217773438e-05s
INFO | --- Analysis for bpr took 1.9600398540496826s
Availability | SPARQL endpoint availability check for Brazilian Politicians took 4.00543212890625e-05s
Availability | VoID file availability check for Brazilian Politicians took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Brazilian Politicians took 0.18363666534423828s
Reputation | Calculation of the PageRank for Brazilian Politicians took 0.02244091033935547s
Interlinking | Calculation of Degree of Connection for Brazilian Politicians took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Brazilian Politicians took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Brazilian Politicians took 7.033348083496094e-05s
Believability | Calculation of trust value for Brazilian Politicians took 1.0728836059570312e-05s
INFO | --- Analysis for brazilian-politicians took 1.9810104370117188s
Availability | SPARQL endpoint availability check for BrazilianCities took 4.0531158447265625e-05s
Availability | VoID file availability check for BrazilianCities took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for BrazilianCities took 0.1817460060119629s
Reputation | Calculation of the PageRank for BrazilianCities took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for BrazilianCities took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for BrazilianCities took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for BrazilianCities took 2.9087066650390625e-05s
Believability | Calculation of trust value for BrazilianCities took 1.0251998901367188e-05s
INFO | --- Analysis for braziliancities took 1.9366247653961182s
Availability | SPARQL endpoint availability check for Bricklink took 3.886222839355469e-05s
Availability | VoID file availability check for Bricklink took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Bricklink took 0.17267727851867676s
Reputation | Calculation of the PageRank for Bricklink took 0.02051377296447754s
Interlinking | Calculation of Degree of Connection for Bricklink took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bricklink took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Bricklink took 6.365776062011719e-05s
Believability | Calculation of trust value for Bricklink took 9.5367431640625e-06s
INFO | --- Analysis for bricklink took 1.9420888423919678s
Availability | SPARQL endpoint availability check for British Museum Collection took 30.15750503540039s
Availability | VoID file availability check for British Museum Collection took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for British Museum Collection took 0.17414140701293945s
Reputation | Calculation of the PageRank for British Museum Collection took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for British Museum Collection took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for British Museum Collection took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for British Museum Collection took 2.8848648071289062e-05s
Believability | Calculation of trust value for British Museum Collection took 1.1682510375976562e-05s
INFO | --- Analysis for british-museum-collection took 62.30924201011658s
Availability | SPARQL endpoint availability check for Brown Corpus in RDF/NIF took 3.910064697265625e-05s
Availability | VoID file availability check for Brown Corpus in RDF/NIF took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Brown Corpus in RDF/NIF took 0.18396377563476562s
Reputation | Calculation of the PageRank for Brown Corpus in RDF/NIF took 0.020012378692626953s
Interlinking | Calculation of Degree of Connection for Brown Corpus in RDF/NIF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Brown Corpus in RDF/NIF took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Brown Corpus in RDF/NIF took 3.719329833984375e-05s
Believability | Calculation of trust value for Brown Corpus in RDF/NIF took 1.0251998901367188e-05s
INFO | --- Analysis for brown-corpus-in-rdf-nif took 2.017430067062378s
Availability | SPARQL endpoint availability check for French Plant Health Bulletins took 8.463859558105469e-05s
Availability | VoID file availability check for French Plant Health Bulletins took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for French Plant Health Bulletins took 0.17962002754211426s
Reputation | Calculation of the PageRank for French Plant Health Bulletins took 0.01997971534729004s
Interlinking | Calculation of Degree of Connection for French Plant Health Bulletins took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for French Plant Health Bulletins took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for French Plant Health Bulletins took 2.9087066650390625e-05s
Believability | Calculation of trust value for French Plant Health Bulletins took 1.0967254638671875e-05s
INFO | --- Analysis for bsv took 2.033060312271118s
Availability | SPARQL endpoint availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 7.319450378417969e-05s
Availability | VoID file availability check for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.19855046272277832s
Reputation | Calculation of the PageRank for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.020162105560302734s
Interlinking | Calculation of Degree of Connection for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.3113021850585938e-05s
Believability | Calculation of trust value for Bulgarian admissions to correctional facilities Jan 2018 - Nov 2024 took 1.0967254638671875e-05s
INFO | --- Analysis for bulgarian_admissions_to_correctional_facilities took 2.0615012645721436s
Availability | SPARQL endpoint availability check for Bund Offener Haushalt took 8.463859558105469e-05s
Availability | VoID file availability check for Bund Offener Haushalt took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Bund Offener Haushalt took 0.1831369400024414s
Reputation | Calculation of the PageRank for Bund Offener Haushalt took 0.019881010055541992s
Interlinking | Calculation of Degree of Connection for Bund Offener Haushalt took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Bund Offener Haushalt took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Bund Offener Haushalt took 2.9325485229492188e-05s
Believability | Calculation of trust value for Bund Offener Haushalt took 1.2874603271484375e-05s
INFO | --- Analysis for bund-offener-haushalt took 1.9928925037384033s
Availability | SPARQL endpoint availability check for BundestagNebeneinkuenfte took 8.130073547363281e-05s
Availability | VoID file availability check for BundestagNebeneinkuenfte took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for BundestagNebeneinkuenfte took 0.18063950538635254s
Reputation | Calculation of the PageRank for BundestagNebeneinkuenfte took 0.02217864990234375s
Interlinking | Calculation of Degree of Connection for BundestagNebeneinkuenfte took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for BundestagNebeneinkuenfte took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for BundestagNebeneinkuenfte took 3.24249267578125e-05s
Believability | Calculation of trust value for BundestagNebeneinkuenfte took 1.1682510375976562e-05s
INFO | --- Analysis for bundestagnebeneinkuenfte took 2.015653610229492s
Availability | SPARQL endpoint availability check for business.data.gov.uk took 4.076957702636719e-05s
Availability | VoID file availability check for business.data.gov.uk took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for business.data.gov.uk took 0.1740128993988037s
Reputation | Calculation of the PageRank for business.data.gov.uk took 0.022059202194213867s
Interlinking | Calculation of Degree of Connection for business.data.gov.uk took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for business.data.gov.uk took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for business.data.gov.uk took 4.601478576660156e-05s
Believability | Calculation of trust value for business.data.gov.uk took 1.1682510375976562e-05s
INFO | --- Analysis for business-data-gov-uk took 1.9891424179077148s
Availability | SPARQL endpoint availability check for Biblioteca Virtual Miguel de Cervantes took 0.4636039733886719s
Availability | VoID file availability check for Biblioteca Virtual Miguel de Cervantes took 0.0004723072052001953s
Extra | Recovery of all triples for Biblioteca Virtual Miguel de Cervantes took 2.34728741645813s
Performance | Total latancy measurement for Biblioteca Virtual Miguel de Cervantes took 1.4351747035980225s
Amount of data | Number of triples check for Biblioteca Virtual Miguel de Cervantes took 0.36263465881347656s
Interoperability | New terms check for Biblioteca Virtual Miguel de Cervantes took 1.66849684715271s
Versatility | Languages check for Biblioteca Virtual Miguel de Cervantes took 41.83017587661743s
Interpretability | Number of blank nodes check for Biblioteca Virtual Miguel de Cervantes took 0.3005208969116211s
Security | Check HTTPS for Biblioteca Virtual Miguel de Cervantes took 0.1865541934967041s
Interpretability | RDF structures check for Biblioteca Virtual Miguel de Cervantes took 0.5143084526062012s
Versatility | Serialization formats check for Biblioteca Virtual Miguel de Cervantes took 0.3018174171447754s
Availability | RDF dump link check for Biblioteca Virtual Miguel de Cervantes took 0.2902493476867676s
License | MR license check for Biblioteca Virtual Miguel de Cervantes took 0.29641032218933105s
License | HR license check for Biblioteca Virtual Miguel de Cervantes took 19.597326040267944s
Amount of data | Number of property check for Biblioteca Virtual Miguel de Cervantes took 0.3237173557281494s
Understandability | Number of label check for Biblioteca Virtual Miguel de Cervantes took 0.3213200569152832s
Understandability | URI regex check for Biblioteca Virtual Miguel de Cervantes took 0.579451322555542s
Understandability | Vocabs check for Biblioteca Virtual Miguel de Cervantes took 0.28720831871032715s
Verifiability | Authors check for Biblioteca Virtual Miguel de Cervantes took 0.2854583263397217s
Verifiability | Publishers check for Biblioteca Virtual Miguel de Cervantes took 0.29346299171447754s
Performance | Throughput check for Biblioteca Virtual Miguel de Cervantes took 11.513973712921143s
Amount of data | Check the number of entities for Biblioteca Virtual Miguel de Cervantes took 6.961822509765625e-05s
Verifiability | Contribs. check for Biblioteca Virtual Miguel de Cervantes took 0.2973916530609131s
Interlinking | sameAs chians check for Biblioteca Virtual Miguel de Cervantes took 0.33997297286987305s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.29750704765319824s
Interlinking | skos check for Biblioteca Virtual Miguel de Cervantes took 0.28440237045288086s
Timeliness | dataset update frequency check for Biblioteca Virtual Miguel de Cervantes took 0.2885580062866211s
Currency | Creation date check for Biblioteca Virtual Miguel de Cervantes took 0.5671408176422119s
Currency | Modification date check for Biblioteca Virtual Miguel de Cervantes took 0.5670363903045654s
Rep.Conc. | URIs length for Biblioteca Virtual Miguel de Cervantes took 4.318278551101685s
Interoperability | New vocabularies check for Biblioteca Virtual Miguel de Cervantes took 2.384185791015625e-06s
Consistency | Deprecated classes/propertiers check for Biblioteca Virtual Miguel de Cervantes took 0.29485249519348145s
Accuracy | Check Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.432889461517334s
Accuracy | Check Inverse Functional Property for Biblioteca Virtual Miguel de Cervantes took 0.4492199420928955s
Accuracy | Check Empty annotation labels for Biblioteca Virtual Miguel de Cervantes took 2.189326047897339s
Accuracy | Check White space in annotation for Biblioteca Virtual Miguel de Cervantes took 0.033386945724487305s
Accuracy | Check Datatype consistency for Biblioteca Virtual Miguel de Cervantes took 0.028427600860595703s
Consistency | Disjoint class check for Biblioteca Virtual Miguel de Cervantes took 0.35468530654907227s
Consistency | Check Misplaced properties for Biblioteca Virtual Miguel de Cervantes took 1.4062473773956299s
Consistency | Misplaced classes for Biblioteca Virtual Miguel de Cervantes took 0.3784604072570801s
Consistency | Check Ontology hijacking for Biblioteca Virtual Miguel de Cervantes took 2.6325883865356445s
Consistency | Check Invalid usage of undefined classes for Biblioteca Virtual Miguel de Cervantes took 1.284085750579834s
Consistency | Check Invalid usage of undefined properties for Biblioteca Virtual Miguel de Cervantes took 2.50571870803833s
Conciseness | Check Extensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.03464484214782715s
Conciseness | Check Intensional conciseness for Biblioteca Virtual Miguel de Cervantes took 0.29128289222717285s
Security | Sign check for Biblioteca Virtual Miguel de Cervantes took 0.2997746467590332s
Availability | Check URIs Dereferenciability for Biblioteca Virtual Miguel de Cervantes took 1337.6188032627106s
Completeness | Calculation of interlinking completeness for Biblioteca Virtual Miguel de Cervantes took 0.28371310234069824s
Reputation | Calculation of the PageRank for Biblioteca Virtual Miguel de Cervantes took 0.02113652229309082s
Interlinking | Calculation of Degree of Connection for Biblioteca Virtual Miguel de Cervantes took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Biblioteca Virtual Miguel de Cervantes took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Biblioteca Virtual Miguel de Cervantes took 0.0001380443572998047s
Interoperability | Check the re-using of existing vocabs for Biblioteca Virtual Miguel de Cervantes took 1.6689300537109375e-06s
Believability | Calculation of trust value for Biblioteca Virtual Miguel de Cervantes took 1.0013580322265625e-05s
INFO | --- Analysis for BVMC took 1471.253737449646s
Availability | SPARQL endpoint availability check for Price changes due to cabbage imports took 8.440017700195312e-05s
Availability | VoID file availability check for Price changes due to cabbage imports took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Price changes due to cabbage imports took 0.19612479209899902s
Reputation | Calculation of the PageRank for Price changes due to cabbage imports took 0.021284818649291992s
Interlinking | Calculation of Degree of Connection for Price changes due to cabbage imports took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for Price changes due to cabbage imports took 0.0010554790496826172s
Interlinking | Calculation of Clustering coefficient for Price changes due to cabbage imports took 4.124641418457031e-05s
Believability | Calculation of trust value for Price changes due to cabbage imports took 1.2636184692382812e-05s
INFO | --- Analysis for cabbage took 2.0231757164001465s
Availability | SPARQL endpoint availability check for cablegate took 8.416175842285156e-05s
Availability | VoID file availability check for cablegate took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for cablegate took 0.17342066764831543s
Reputation | Calculation of the PageRank for cablegate took 0.020600557327270508s
Interlinking | Calculation of Degree of Connection for cablegate took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for cablegate took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for cablegate took 6.580352783203125e-05s
Believability | Calculation of trust value for cablegate took 1.2159347534179688e-05s
INFO | --- Analysis for cablegate took 1.9758751392364502s
Availability | SPARQL endpoint availability check for Calames took 8.606910705566406e-05s
Availability | VoID file availability check for Calames took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Calames took 0.1814897060394287s
Reputation | Calculation of the PageRank for Calames took 0.02052021026611328s
Interlinking | Calculation of Degree of Connection for Calames took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Calames took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Calames took 3.7670135498046875e-05s
Believability | Calculation of trust value for Calames took 1.2636184692382812e-05s
INFO | --- Analysis for calames took 2.0172343254089355s
Availability | SPARQL endpoint availability check for CaLiGraph took 8.893013000488281e-05s
Availability | VoID file availability check for CaLiGraph took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.17723417282104492s
Reputation | Calculation of the PageRank for CaLiGraph took 0.02010631561279297s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 2.9802322387695312e-05s
Believability | Calculation of trust value for CaLiGraph took 1.239776611328125e-05s
INFO | --- Analysis for CaLiGraph took 1.984424352645874s
Availability | SPARQL endpoint availability check for CaLiGraph took 8.20159912109375e-05s
Availability | VoID file availability check for CaLiGraph took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for CaLiGraph took 0.1839430332183838s
Reputation | Calculation of the PageRank for CaLiGraph took 0.019962310791015625s
Interlinking | Calculation of Degree of Connection for CaLiGraph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CaLiGraph took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for CaLiGraph took 6.437301635742188e-05s
Believability | Calculation of trust value for CaLiGraph took 1.049041748046875e-05s
INFO | --- Analysis for caligraph took 1.9916985034942627s
Availability | SPARQL endpoint availability check for can-link took 8.368492126464844e-05s
Availability | VoID file availability check for can-link took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for can-link took 0.1853315830230713s
Reputation | Calculation of the PageRank for can-link took 0.020915985107421875s
Interlinking | Calculation of Degree of Connection for can-link took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for can-link took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for can-link took 2.8371810913085938e-05s
Believability | Calculation of trust value for can-link took 1.0251998901367188e-05s
INFO | --- Analysis for can-link took 1.9486570358276367s
Availability | SPARQL endpoint availability check for Postal codes Italy (LinkedOpenData.it) took 3.8623809814453125e-05s
Availability | VoID file availability check for Postal codes Italy (LinkedOpenData.it) took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Postal codes Italy (LinkedOpenData.it) took 0.19577598571777344s
Reputation | Calculation of the PageRank for Postal codes Italy (LinkedOpenData.it) took 0.019970417022705078s
Interlinking | Calculation of Degree of Connection for Postal codes Italy (LinkedOpenData.it) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Postal codes Italy (LinkedOpenData.it) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Postal codes Italy (LinkedOpenData.it) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Postal codes Italy (LinkedOpenData.it) took 6.4373016357421875e-06s
INFO | --- Analysis for cap-italy-rdf took 1.9740626811981201s
Availability | SPARQL endpoint availability check for person took 3.9577484130859375e-05s
Availability | VoID file availability check for person took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for person took 0.17958450317382812s
Reputation | Calculation of the PageRank for person took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for person took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for person took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for person took 2.8133392333984375e-05s
Believability | Calculation of trust value for person took 1.0967254638671875e-05s
INFO | --- Analysis for card took 1.9649245738983154s
Availability | SPARQL endpoint availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 4.792213439941406e-05s
Availability | VoID file availability check for Catalan EuroWordNet-lemon lexicon (3.0) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Catalan EuroWordNet-lemon lexicon (3.0) took 0.17360949516296387s
Reputation | Calculation of the PageRank for Catalan EuroWordNet-lemon lexicon (3.0) took 0.020227432250976562s
Interlinking | Calculation of Degree of Connection for Catalan EuroWordNet-lemon lexicon (3.0) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Catalan EuroWordNet-lemon lexicon (3.0) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Catalan EuroWordNet-lemon lexicon (3.0) took 3.910064697265625e-05s
Believability | Calculation of trust value for Catalan EuroWordNet-lemon lexicon (3.0) took 1.0728836059570312e-05s
INFO | --- Analysis for catalan-eurowordnet-lemon-lexicon-3-0 took 1.9540824890136719s
Availability | SPARQL endpoint availability check for Catalogus Professorum Lipsiensis took 8.106231689453125e-05s
Availability | VoID file availability check for Catalogus Professorum Lipsiensis took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for Catalogus Professorum Lipsiensis took 0.17403316497802734s
Reputation | Calculation of the PageRank for Catalogus Professorum Lipsiensis took 0.021611928939819336s
Interlinking | Calculation of Degree of Connection for Catalogus Professorum Lipsiensis took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Catalogus Professorum Lipsiensis took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Catalogus Professorum Lipsiensis took 3.1948089599609375e-05s
Believability | Calculation of trust value for Catalogus Professorum Lipsiensis took 1.1444091796875e-05s
INFO | --- Analysis for catalogus-professorum-lipsiensis took 1.9851419925689697s
Availability | SPARQL endpoint availability check for Norway catch records dataset @PSNC took 8.249282836914062e-05s
Availability | VoID file availability check for Norway catch records dataset @PSNC took 0.0006270408630371094s
Completeness | Calculation of interlinking completeness for Norway catch records dataset @PSNC took 0.17879796028137207s
Reputation | Calculation of the PageRank for Norway catch records dataset @PSNC took 0.02153754234313965s
Interlinking | Calculation of Degree of Connection for Norway catch records dataset @PSNC took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Norway catch records dataset @PSNC took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Norway catch records dataset @PSNC took 4.076957702636719e-05s
Believability | Calculation of trust value for Norway catch records dataset @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for Catch_Record_(2014-_2019) took 1.9842641353607178s
Availability | SPARQL endpoint availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 8.606910705566406e-05s
Availability | VoID file availability check for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.17941975593566895s
Reputation | Calculation of the PageRank for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.023214101791381836s
Interlinking | Calculation of Degree of Connection for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 0.00010037422180175781s
Believability | Calculation of trust value for CE4R Knowledge Centre Corporate Excellence – Centre for Reputation Leadership took 1.1920928955078125e-05s
INFO | --- Analysis for ce4r took 1.9564948081970215s
Availability | SPARQL endpoint availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5038611888885498s
Availability | VoID file availability check for Linked Data Cultural Heritage Agency of the Netherlands took 0.0005042552947998047s
Extra | Recovery of all triples for Linked Data Cultural Heritage Agency of the Netherlands took 1.1130609512329102s
Performance | Total latancy measurement for Linked Data Cultural Heritage Agency of the Netherlands took 0.8480472564697266s
Amount of data | Number of triples check for Linked Data Cultural Heritage Agency of the Netherlands took 0.5415153503417969s
Interoperability | New terms check for Linked Data Cultural Heritage Agency of the Netherlands took 1.7355728149414062s
Versatility | Languages check for Linked Data Cultural Heritage Agency of the Netherlands took 58.14542555809021s
Interpretability | Number of blank nodes check for Linked Data Cultural Heritage Agency of the Netherlands took 0.27068591117858887s
Interpretability | RDF structures check for Linked Data Cultural Heritage Agency of the Netherlands took 0.40924692153930664s
Versatility | Serialization formats check for Linked Data Cultural Heritage Agency of the Netherlands took 0.19284629821777344s
Availability | RDF dump link check for Linked Data Cultural Heritage Agency of the Netherlands took 0.2372303009033203s
License | MR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4622788429260254s
License | HR license check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4936690330505371s
Amount of data | Number of property check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16544198989868164s
Understandability | Number of label check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4502859115600586s
Understandability | URI regex check for Linked Data Cultural Heritage Agency of the Netherlands took 0.35529518127441406s
Understandability | Vocabs check for Linked Data Cultural Heritage Agency of the Netherlands took 0.21572661399841309s
Verifiability | Authors check for Linked Data Cultural Heritage Agency of the Netherlands took 0.23115801811218262s
Verifiability | Publishers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.4094417095184326s
Performance | Throughput check for Linked Data Cultural Heritage Agency of the Netherlands took 12.018003940582275s
Amount of data | Check the number of entities for Linked Data Cultural Heritage Agency of the Netherlands took 6.818771362304688e-05s
Verifiability | Contribs. check for Linked Data Cultural Heritage Agency of the Netherlands took 0.25798821449279785s
Interlinking | sameAs chians check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1775352954864502s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.9655721187591553s
Interlinking | skos check for Linked Data Cultural Heritage Agency of the Netherlands took 0.16356754302978516s
Timeliness | dataset update frequency check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1901402473449707s
Currency | Creation date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.678990364074707s
Currency | Modification date check for Linked Data Cultural Heritage Agency of the Netherlands took 0.48113274574279785s
Rep.Conc. | URIs length for Linked Data Cultural Heritage Agency of the Netherlands took 2.128469705581665s
Interoperability | New vocabularies check for Linked Data Cultural Heritage Agency of the Netherlands took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Linked Data Cultural Heritage Agency of the Netherlands took 0.17140483856201172s
Accuracy | Check Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.2979254722595215s
Accuracy | Check Inverse Functional Property for Linked Data Cultural Heritage Agency of the Netherlands took 0.335376501083374s
Accuracy | Check Empty annotation labels for Linked Data Cultural Heritage Agency of the Netherlands took 0.6358232498168945s
Accuracy | Check White space in annotation for Linked Data Cultural Heritage Agency of the Netherlands took 0.02831125259399414s
Accuracy | Check Datatype consistency for Linked Data Cultural Heritage Agency of the Netherlands took 0.02787327766418457s
Consistency | Disjoint class check for Linked Data Cultural Heritage Agency of the Netherlands took 0.40828776359558105s
Consistency | Check Misplaced properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.266085147857666s
Consistency | Check Ontology hijacking for Linked Data Cultural Heritage Agency of the Netherlands took 2.011336326599121s
Consistency | Check Invalid usage of undefined classes for Linked Data Cultural Heritage Agency of the Netherlands took 1.2819442749023438s
Consistency | Check Invalid usage of undefined properties for Linked Data Cultural Heritage Agency of the Netherlands took 1.4876430034637451s
Conciseness | Check Extensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.029963970184326172s
Conciseness | Check Intensional conciseness for Linked Data Cultural Heritage Agency of the Netherlands took 0.21431636810302734s
Security | Sign check for Linked Data Cultural Heritage Agency of the Netherlands took 0.1757650375366211s
Availability | Check URIs Dereferenciability for Linked Data Cultural Heritage Agency of the Netherlands took 4585.696073293686s
Completeness | Calculation of interlinking completeness for Linked Data Cultural Heritage Agency of the Netherlands took 0.5268039703369141s
Reputation | Calculation of the PageRank for Linked Data Cultural Heritage Agency of the Netherlands took 0.02111530303955078s
Interlinking | Calculation of Degree of Connection for Linked Data Cultural Heritage Agency of the Netherlands took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for Linked Data Cultural Heritage Agency of the Netherlands took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for Linked Data Cultural Heritage Agency of the Netherlands took 4.00543212890625e-05s
Interoperability | Check the re-using of existing vocabs for Linked Data Cultural Heritage Agency of the Netherlands took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Data Cultural Heritage Agency of the Netherlands took 1.1444091796875e-05s
INFO | --- Analysis for ceo took 4714.183765172958s
Availability | SPARQL endpoint availability check for Charging Stations took 8.106231689453125e-05s
Availability | VoID file availability check for Charging Stations took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Charging Stations took 0.1895444393157959s
Reputation | Calculation of the PageRank for Charging Stations took 0.020502567291259766s
Interlinking | Calculation of Degree of Connection for Charging Stations took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Charging Stations took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Charging Stations took 3.123283386230469e-05s
Believability | Calculation of trust value for Charging Stations took 1.1444091796875e-05s
INFO | --- Analysis for charging-stations took 1.9781298637390137s
Availability | SPARQL endpoint availability check for Chat Game corpus took 4.0531158447265625e-05s
Availability | VoID file availability check for Chat Game corpus took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Chat Game corpus took 0.17107272148132324s
Reputation | Calculation of the PageRank for Chat Game corpus took 0.021680593490600586s
Interlinking | Calculation of Degree of Connection for Chat Game corpus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Chat Game corpus took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Chat Game corpus took 3.337860107421875e-05s
Believability | Calculation of trust value for Chat Game corpus took 1.1920928955078125e-05s
INFO | --- Analysis for chat-game-corpus took 1.978062629699707s
Availability | SPARQL endpoint availability check for Chemical Entities of Biological Interest (ChEBI) took 6.318092346191406e-05s
Availability | VoID file availability check for Chemical Entities of Biological Interest (ChEBI) took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Chemical Entities of Biological Interest (ChEBI) took 0.18310165405273438s
Reputation | Calculation of the PageRank for Chemical Entities of Biological Interest (ChEBI) took 0.02285623550415039s
Interlinking | Calculation of Degree of Connection for Chemical Entities of Biological Interest (ChEBI) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Chemical Entities of Biological Interest (ChEBI) took 0.0006840229034423828s
Interlinking | Calculation of Clustering coefficient for Chemical Entities of Biological Interest (ChEBI) took 3.075599670410156e-05s
Believability | Calculation of trust value for Chemical Entities of Biological Interest (ChEBI) took 1.0967254638671875e-05s
INFO | --- Analysis for chebi took 1.9647948741912842s
Availability | SPARQL endpoint availability check for Chem2Bio2RDF took 8.559226989746094e-05s
Availability | VoID file availability check for Chem2Bio2RDF took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Chem2Bio2RDF took 0.1830284595489502s
Reputation | Calculation of the PageRank for Chem2Bio2RDF took 0.022890090942382812s
Interlinking | Calculation of Degree of Connection for Chem2Bio2RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Chem2Bio2RDF took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Chem2Bio2RDF took 5.936622619628906e-05s
Believability | Calculation of trust value for Chem2Bio2RDF took 1.4066696166992188e-05s
INFO | --- Analysis for chem2bio2rdf took 1.9737212657928467s
Availability | SPARQL endpoint availability check for ChEMBL RDF took 8.153915405273438e-05s
Availability | VoID file availability check for ChEMBL RDF took 0.000225067138671875s
Completeness | Calculation of interlinking completeness for ChEMBL RDF took 0.1842041015625s
Reputation | Calculation of the PageRank for ChEMBL RDF took 0.020366191864013672s
Interlinking | Calculation of Degree of Connection for ChEMBL RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ChEMBL RDF took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for ChEMBL RDF took 4.982948303222656e-05s
Believability | Calculation of trust value for ChEMBL RDF took 1.0967254638671875e-05s
INFO | --- Analysis for chembl-rdf took 2.122244119644165s
Availability | SPARQL endpoint availability check for chemdb  dataset took 8.273124694824219e-05s
Availability | VoID file availability check for chemdb  dataset took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for chemdb  dataset took 0.21242856979370117s
Reputation | Calculation of the PageRank for chemdb  dataset took 0.021784067153930664s
Interlinking | Calculation of Degree of Connection for chemdb  dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb  dataset took 0.0007770061492919922s
Interlinking | Calculation of Clustering coefficient for chemdb  dataset took 7.2479248046875e-05s
Believability | Calculation of trust value for chemdb  dataset took 1.1444091796875e-05s
INFO | --- Analysis for chemdb-basicInfo took 2.0279555320739746s
Availability | SPARQL endpoint availability check for chemdb estimated properties dataset took 8.320808410644531e-05s
Availability | VoID file availability check for chemdb estimated properties dataset took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for chemdb estimated properties dataset took 0.1813814640045166s
Reputation | Calculation of the PageRank for chemdb estimated properties dataset took 0.020395278930664062s
Interlinking | Calculation of Degree of Connection for chemdb estimated properties dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for chemdb estimated properties dataset took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for chemdb estimated properties dataset took 3.981590270996094e-05s
Believability | Calculation of trust value for chemdb estimated properties dataset took 1.239776611328125e-05s
INFO | --- Analysis for chemdb-estimatedProperties took 2.0235610008239746s
Availability | SPARQL endpoint availability check for chemdb phase transition dataset took 4.076957702636719e-05s
Availability | VoID file availability check for chemdb phase transition dataset took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for chemdb phase transition dataset took 0.17972588539123535s
Reputation | Calculation of the PageRank for chemdb phase transition dataset took 0.02037525177001953s
Interlinking | Calculation of Degree of Connection for chemdb phase transition dataset took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for chemdb phase transition dataset took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for chemdb phase transition dataset took 4.124641418457031e-05s
Believability | Calculation of trust value for chemdb phase transition dataset took 1.1682510375976562e-05s
INFO | --- Analysis for chemdb-phaseTransition took 1.9632086753845215s
Availability | SPARQL endpoint availability check for chemdb thermochemistry dataset took 4.100799560546875e-05s
Availability | VoID file availability check for chemdb thermochemistry dataset took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for chemdb thermochemistry dataset took 0.18468642234802246s
Reputation | Calculation of the PageRank for chemdb thermochemistry dataset took 0.021140575408935547s
Interlinking | Calculation of Degree of Connection for chemdb thermochemistry dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for chemdb thermochemistry dataset took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for chemdb thermochemistry dataset took 5.817413330078125e-05s
Believability | Calculation of trust value for chemdb thermochemistry dataset took 8.821487426757812e-06s
INFO | --- Analysis for chemdb-thermochemistry took 2.008103370666504s
Availability | SPARQL endpoint availability check for ChemPedia RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for ChemPedia RDF took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for ChemPedia RDF took 0.17779326438903809s
Reputation | Calculation of the PageRank for ChemPedia RDF took 0.020441055297851562s
Interlinking | Calculation of Degree of Connection for ChemPedia RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ChemPedia RDF took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for ChemPedia RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for ChemPedia RDF took 1.2874603271484375e-05s
INFO | --- Analysis for chempedia-rdf took 1.9716427326202393s
Availability | SPARQL endpoint availability check for Chiman Maru took 3.910064697265625e-05s
Availability | VoID file availability check for Chiman Maru took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for Chiman Maru took 0.1744980812072754s
Reputation | Calculation of the PageRank for Chiman Maru took 0.020565509796142578s
Interlinking | Calculation of Degree of Connection for Chiman Maru took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Chiman Maru took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Chiman Maru took 3.123283386230469e-05s
Believability | Calculation of trust value for Chiman Maru took 1.3113021850585938e-05s
INFO | --- Analysis for ChimanMaru_Entrepreneur took 1.9484312534332275s
Availability | SPARQL endpoint availability check for Chinese Red Song Linked Data Dataset took 391.9925925731659s
Availability | VoID file availability check for Chinese Red Song Linked Data Dataset took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for Chinese Red Song Linked Data Dataset took 0.1761331558227539s
Reputation | Calculation of the PageRank for Chinese Red Song Linked Data Dataset took 0.020737171173095703s
Interlinking | Calculation of Degree of Connection for Chinese Red Song Linked Data Dataset took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Chinese Red Song Linked Data Dataset took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Chinese Red Song Linked Data Dataset took 8.249282836914062e-05s
Believability | Calculation of trust value for Chinese Red Song Linked Data Dataset took 1.239776611328125e-05s
INFO | --- Analysis for Chinese_Red_Classic_Song_Linked_Data_Dataset took 664.7346940040588s
Availability | SPARQL endpoint availability check for Chronicling America took 8.368492126464844e-05s
Availability | VoID file availability check for Chronicling America took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Chronicling America took 0.18075251579284668s
Reputation | Calculation of the PageRank for Chronicling America took 0.02021646499633789s
Interlinking | Calculation of Degree of Connection for Chronicling America took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Chronicling America took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Chronicling America took 9.560585021972656e-05s
Believability | Calculation of trust value for Chronicling America took 6.198883056640625e-06s
INFO | --- Analysis for chronicling-america took 1.9822523593902588s
Availability | SPARQL endpoint availability check for Cultural Heritage Thesaurus took 0.5447514057159424s
Availability | VoID file availability check for Cultural Heritage Thesaurus took 0.0005218982696533203s
Extra | Recovery of all triples for Cultural Heritage Thesaurus took 82.58430933952332s
Performance | Total latancy measurement for Cultural Heritage Thesaurus took 1.4934844970703125s
Amount of data | Number of triples check for Cultural Heritage Thesaurus took 0.6467523574829102s
Interoperability | New terms check for Cultural Heritage Thesaurus took 2.034616470336914s
Versatility | Languages check for Cultural Heritage Thesaurus took 1.5377261638641357s
Interpretability | Number of blank nodes check for Cultural Heritage Thesaurus took 0.5435316562652588s
Interpretability | RDF structures check for Cultural Heritage Thesaurus took 0.30068159103393555s
Versatility | Serialization formats check for Cultural Heritage Thesaurus took 0.289003849029541s
Availability | RDF dump link check for Cultural Heritage Thesaurus took 10.698238849639893s
License | MR license check for Cultural Heritage Thesaurus took 0.37226152420043945s
License | HR license check for Cultural Heritage Thesaurus took 0.5414631366729736s
Amount of data | Number of property check for Cultural Heritage Thesaurus took 0.2903285026550293s
Understandability | Number of label check for Cultural Heritage Thesaurus took 0.32517170906066895s
Understandability | URI regex check for Cultural Heritage Thesaurus took 0.5918564796447754s
Understandability | Vocabs check for Cultural Heritage Thesaurus took 0.2765984535217285s
Verifiability | Authors check for Cultural Heritage Thesaurus took 0.2920212745666504s
Verifiability | Publishers check for Cultural Heritage Thesaurus took 0.28675222396850586s
Performance | Throughput check for Cultural Heritage Thesaurus took 11.619545698165894s
Amount of data | Check the number of entities for Cultural Heritage Thesaurus took 5.9604644775390625e-05s
Verifiability | Contribs. check for Cultural Heritage Thesaurus took 0.28743529319763184s
Interlinking | sameAs chians check for Cultural Heritage Thesaurus took 0.29242491722106934s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3045203685760498s
Interlinking | skos check for Cultural Heritage Thesaurus took 0.3278634548187256s
Timeliness | dataset update frequency check for Cultural Heritage Thesaurus took 0.29679369926452637s
Currency | Creation date check for Cultural Heritage Thesaurus took 0.5879297256469727s
Currency | Modification date check for Cultural Heritage Thesaurus took 0.5888197422027588s
Rep.Conc. | URIs length for Cultural Heritage Thesaurus took 29.252676725387573s
Interoperability | New vocabularies check for Cultural Heritage Thesaurus took 1.0510506629943848s
Consistency | Deprecated classes/propertiers check for Cultural Heritage Thesaurus took 0.2888307571411133s
Accuracy | Check Functional Property for Cultural Heritage Thesaurus took 0.30181145668029785s
Accuracy | Check Inverse Functional Property for Cultural Heritage Thesaurus took 0.28638315200805664s
Accuracy | Check Empty annotation labels for Cultural Heritage Thesaurus took 5.235805511474609s
Accuracy | Check White space in annotation for Cultural Heritage Thesaurus took 0.21970677375793457s
Consistency | Disjoint class check for Cultural Heritage Thesaurus took 0.2875082492828369s
Consistency | Check Misplaced properties for Cultural Heritage Thesaurus took 0.9693405628204346s
Consistency | Misplaced classes for Cultural Heritage Thesaurus took 0.28867459297180176s
Consistency | Check Ontology hijacking for Cultural Heritage Thesaurus took 6.3277506828308105s
Consistency | Check Invalid usage of undefined properties for Cultural Heritage Thesaurus took 2.076876640319824s
Conciseness | Check Extensional conciseness for Cultural Heritage Thesaurus took 0.0001494884490966797s
Security | Sign check for Cultural Heritage Thesaurus took 0.28557348251342773s
Availability | Check URIs Dereferenciability for Cultural Heritage Thesaurus took 262.7843029499054s
Completeness | Calculation of interlinking completeness for Cultural Heritage Thesaurus took 0.2538313865661621s
Reputation | Calculation of the PageRank for Cultural Heritage Thesaurus took 0.022836685180664062s
Interlinking | Calculation of Degree of Connection for Cultural Heritage Thesaurus took 1.8358230590820312e-05s
Interlinking | Calculation of Centrality for Cultural Heritage Thesaurus took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Cultural Heritage Thesaurus took 9.751319885253906e-05s
Interoperability | Check the re-using of existing vocabs for Cultural Heritage Thesaurus took 2.7470626831054688s
Believability | Calculation of trust value for Cultural Heritage Thesaurus took 1.2159347534179688e-05s
INFO | --- Analysis for cht took 451.86634635925293s
Availability | SPARQL endpoint availability check for ciard-ring took 8.273124694824219e-05s
Availability | VoID file availability check for ciard-ring took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for ciard-ring took 0.1765289306640625s
Reputation | Calculation of the PageRank for ciard-ring took 0.020571470260620117s
Interlinking | Calculation of Degree of Connection for ciard-ring took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ciard-ring took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ciard-ring took 4.7206878662109375e-05s
Believability | Calculation of trust value for ciard-ring took 1.0251998901367188e-05s
INFO | --- Analysis for ciard-ring took 1.9731335639953613s
Availability | SPARQL endpoint availability check for Cine Figure took 8.106231689453125e-05s
Availability | VoID file availability check for Cine Figure took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Cine Figure took 0.17595672607421875s
Reputation | Calculation of the PageRank for Cine Figure took 0.020367860794067383s
Interlinking | Calculation of Degree of Connection for Cine Figure took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Cine Figure took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Cine Figure took 4.4345855712890625e-05s
Believability | Calculation of trust value for Cine Figure took 1.0728836059570312e-05s
INFO | --- Analysis for Cine_Figure took 1.971998929977417s
Availability | SPARQL endpoint availability check for Cinémathèque québécoise Linked Open Data took 2.9348084926605225s
Availability | VoID file availability check for Cinémathèque québécoise Linked Open Data took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Cinémathèque québécoise Linked Open Data took 0.17565298080444336s
Reputation | Calculation of the PageRank for Cinémathèque québécoise Linked Open Data took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for Cinémathèque québécoise Linked Open Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Cinémathèque québécoise Linked Open Data took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Cinémathèque québécoise Linked Open Data took 4.5299530029296875e-05s
Believability | Calculation of trust value for Cinémathèque québécoise Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for cinematheque-quebecoise-linked-open-data took 6.745102167129517s
Availability | SPARQL endpoint availability check for CIPFA took 8.535385131835938e-05s
Availability | VoID file availability check for CIPFA took 0.0004851818084716797s
Completeness | Calculation of interlinking completeness for CIPFA took 0.17867374420166016s
Reputation | Calculation of the PageRank for CIPFA took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for CIPFA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CIPFA took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for CIPFA took 3.552436828613281e-05s
Believability | Calculation of trust value for CIPFA took 1.2636184692382812e-05s
INFO | --- Analysis for cipfa took 1.9631707668304443s
Availability | SPARQL endpoint availability check for Comprehensive Knowledge Archive Network took 0.00023221969604492188s
Availability | VoID file availability check for Comprehensive Knowledge Archive Network took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Comprehensive Knowledge Archive Network took 0.18153119087219238s
Reputation | Calculation of the PageRank for Comprehensive Knowledge Archive Network took 0.020251750946044922s
Interlinking | Calculation of Degree of Connection for Comprehensive Knowledge Archive Network took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comprehensive Knowledge Archive Network took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Comprehensive Knowledge Archive Network took 0.00039315223693847656s
Believability | Calculation of trust value for Comprehensive Knowledge Archive Network took 1.239776611328125e-05s
INFO | --- Analysis for ckan took 1.9957842826843262s
Availability | SPARQL endpoint availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.838539123535156e-05s
Availability | VoID file availability check for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0004203319549560547s
Completeness | Calculation of interlinking completeness for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.1815323829650879s
Reputation | Calculation of the PageRank for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.020090103149414062s
Interlinking | Calculation of Degree of Connection for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 3.4809112548828125e-05s
Believability | Calculation of trust value for Corpus for Latin Sociolinguistic Studies on Epigraphic textS (CLaSSES) in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for CLaSSES took 1.9815058708190918s
Availability | SPARQL endpoint availability check for Temples of the Classical World took 8.392333984375e-05s
Availability | VoID file availability check for Temples of the Classical World took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Temples of the Classical World took 0.17405056953430176s
Reputation | Calculation of the PageRank for Temples of the Classical World took 0.021205902099609375s
Interlinking | Calculation of Degree of Connection for Temples of the Classical World took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Temples of the Classical World took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Temples of the Classical World took 2.765655517578125e-05s
Believability | Calculation of trust value for Temples of the Classical World took 1.1920928955078125e-05s
INFO | --- Analysis for classical_temples took 2.0068209171295166s
Availability | SPARQL endpoint availability check for Linked Clean Energy Data (reegle.info) took 9.822845458984375e-05s
Availability | VoID file availability check for Linked Clean Energy Data (reegle.info) took 0.0005273818969726562s
Completeness | Calculation of interlinking completeness for Linked Clean Energy Data (reegle.info) took 0.1748809814453125s
Reputation | Calculation of the PageRank for Linked Clean Energy Data (reegle.info) took 0.020853042602539062s
Interlinking | Calculation of Degree of Connection for Linked Clean Energy Data (reegle.info) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Clean Energy Data (reegle.info) took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Linked Clean Energy Data (reegle.info) took 7.677078247070312e-05s
Believability | Calculation of trust value for Linked Clean Energy Data (reegle.info) took 1.0013580322265625e-05s
INFO | --- Analysis for clean-energy-data-reegle took 1.974191665649414s
Availability | SPARQL endpoint availability check for CLLD-afbo took 8.106231689453125e-05s
Availability | VoID file availability check for CLLD-afbo took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for CLLD-afbo took 0.17382502555847168s
Reputation | Calculation of the PageRank for CLLD-afbo took 0.02026200294494629s
Interlinking | Calculation of Degree of Connection for CLLD-afbo took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CLLD-afbo took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for CLLD-afbo took 0.00010204315185546875s
Believability | Calculation of trust value for CLLD-afbo took 1.1920928955078125e-05s
INFO | --- Analysis for clld-afbo took 1.9649975299835205s
Availability | SPARQL endpoint availability check for CLLD-APICS took 8.130073547363281e-05s
Availability | VoID file availability check for CLLD-APICS took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for CLLD-APICS took 0.18151521682739258s
Reputation | Calculation of the PageRank for CLLD-APICS took 0.02025318145751953s
Interlinking | Calculation of Degree of Connection for CLLD-APICS took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CLLD-APICS took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for CLLD-APICS took 7.2479248046875e-05s
Believability | Calculation of trust value for CLLD-APICS took 1.2159347534179688e-05s
INFO | --- Analysis for clld-apics took 2.015070676803589s
Availability | SPARQL endpoint availability check for CLLD-EWAVE took 8.368492126464844e-05s
Availability | VoID file availability check for CLLD-EWAVE took 0.0002357959747314453s
Completeness | Calculation of interlinking completeness for CLLD-EWAVE took 0.17818999290466309s
Reputation | Calculation of the PageRank for CLLD-EWAVE took 0.020308732986450195s
Interlinking | Calculation of Degree of Connection for CLLD-EWAVE took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CLLD-EWAVE took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for CLLD-EWAVE took 3.4809112548828125e-05s
Believability | Calculation of trust value for CLLD-EWAVE took 1.2874603271484375e-05s
INFO | --- Analysis for clld-ewave took 1.9848873615264893s
Availability | SPARQL endpoint availability check for CLLD-GLOTTOLOG took 5.340576171875e-05s
Availability | VoID file availability check for CLLD-GLOTTOLOG took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for CLLD-GLOTTOLOG took 0.17902708053588867s
Reputation | Calculation of the PageRank for CLLD-GLOTTOLOG took 0.02036571502685547s
Interlinking | Calculation of Degree of Connection for CLLD-GLOTTOLOG took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for CLLD-GLOTTOLOG took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for CLLD-GLOTTOLOG took 9.5367431640625e-05s
Believability | Calculation of trust value for CLLD-GLOTTOLOG took 1.1682510375976562e-05s
INFO | --- Analysis for clld-glottolog took 1.9587557315826416s
Availability | SPARQL endpoint availability check for CLLD-PHOIBLE took 8.20159912109375e-05s
Availability | VoID file availability check for CLLD-PHOIBLE took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for CLLD-PHOIBLE took 0.20623302459716797s
Reputation | Calculation of the PageRank for CLLD-PHOIBLE took 0.0201113224029541s
Interlinking | Calculation of Degree of Connection for CLLD-PHOIBLE took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CLLD-PHOIBLE took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for CLLD-PHOIBLE took 7.772445678710938e-05s
Believability | Calculation of trust value for CLLD-PHOIBLE took 1.1682510375976562e-05s
INFO | --- Analysis for clld-phoible took 1.9679667949676514s
Availability | SPARQL endpoint availability check for CLLD-SAILS took 8.034706115722656e-05s
Availability | VoID file availability check for CLLD-SAILS took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for CLLD-SAILS took 0.19013047218322754s
Reputation | Calculation of the PageRank for CLLD-SAILS took 0.020694255828857422s
Interlinking | Calculation of Degree of Connection for CLLD-SAILS took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CLLD-SAILS took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for CLLD-SAILS took 7.271766662597656e-05s
Believability | Calculation of trust value for CLLD-SAILS took 1.1444091796875e-05s
INFO | --- Analysis for clld-sails took 2.005401372909546s
Availability | SPARQL endpoint availability check for CLLD-WALS took 3.981590270996094e-05s
Availability | VoID file availability check for CLLD-WALS took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for CLLD-WALS took 0.17317461967468262s
Reputation | Calculation of the PageRank for CLLD-WALS took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for CLLD-WALS took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for CLLD-WALS took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for CLLD-WALS took 8.535385131835938e-05s
Believability | Calculation of trust value for CLLD-WALS took 6.9141387939453125e-06s
INFO | --- Analysis for clld-wals took 1.954559087753296s
Availability | SPARQL endpoint availability check for CLLD-WOLD took 3.981590270996094e-05s
Availability | VoID file availability check for CLLD-WOLD took 0.00043773651123046875s
Completeness | Calculation of interlinking completeness for CLLD-WOLD took 0.17276239395141602s
Reputation | Calculation of the PageRank for CLLD-WOLD took 0.02006816864013672s
Interlinking | Calculation of Degree of Connection for CLLD-WOLD took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for CLLD-WOLD took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for CLLD-WOLD took 7.414817810058594e-05s
Believability | Calculation of trust value for CLLD-WOLD took 1.0728836059570312e-05s
INFO | --- Analysis for clld-wold took 1.990391492843628s
Availability | SPARQL endpoint availability check for COD inventory took 8.249282836914062e-05s
Availability | VoID file availability check for COD inventory took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for COD inventory took 0.1899266242980957s
Reputation | Calculation of the PageRank for COD inventory took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for COD inventory took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for COD inventory took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for COD inventory took 2.9087066650390625e-05s
Believability | Calculation of trust value for COD inventory took 7.3909759521484375e-06s
INFO | --- Analysis for cod-inventory took 2.0063071250915527s
Availability | SPARQL endpoint availability check for Cooperation Databank took 3.8623809814453125e-05s
Availability | VoID file availability check for Cooperation Databank took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for Cooperation Databank took 0.17391657829284668s
Reputation | Calculation of the PageRank for Cooperation Databank took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Cooperation Databank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Cooperation Databank took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Cooperation Databank took 3.600120544433594e-05s
Believability | Calculation of trust value for Cooperation Databank took 1.2636184692382812e-05s
INFO | --- Analysis for CoDa took 1.972576379776001s
Availability | SPARQL endpoint availability check for CODE Endpoint took 4.1961669921875e-05s
Availability | VoID file availability check for CODE Endpoint took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for CODE Endpoint took 0.18765521049499512s
Reputation | Calculation of the PageRank for CODE Endpoint took 0.021097898483276367s
Interlinking | Calculation of Degree of Connection for CODE Endpoint took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for CODE Endpoint took 0.0010645389556884766s
Interlinking | Calculation of Clustering coefficient for CODE Endpoint took 3.933906555175781e-05s
Believability | Calculation of trust value for CODE Endpoint took 1.1920928955078125e-05s
INFO | --- Analysis for code-endpoint took 2.0028369426727295s
Availability | SPARQL endpoint availability check for OpenUpLabs COINS took 4.00543212890625e-05s
Availability | VoID file availability check for OpenUpLabs COINS took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for OpenUpLabs COINS took 0.18441224098205566s
Reputation | Calculation of the PageRank for OpenUpLabs COINS took 0.020630359649658203s
Interlinking | Calculation of Degree of Connection for OpenUpLabs COINS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenUpLabs COINS took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs COINS took 3.337860107421875e-05s
Believability | Calculation of trust value for OpenUpLabs COINS took 1.2874603271484375e-05s
INFO | --- Analysis for coins-openuplabs took 1.9787869453430176s
Availability | SPARQL endpoint availability check for Catalogue of Life in China 2003 Edition took 4.076957702636719e-05s
Availability | VoID file availability check for Catalogue of Life in China 2003 Edition took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Catalogue of Life in China 2003 Edition took 0.17514562606811523s
Reputation | Calculation of the PageRank for Catalogue of Life in China 2003 Edition took 0.020135879516601562s
Interlinking | Calculation of Degree of Connection for Catalogue of Life in China 2003 Edition took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Catalogue of Life in China 2003 Edition took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for Catalogue of Life in China 2003 Edition took 8.797645568847656e-05s
Believability | Calculation of trust value for Catalogue of Life in China 2003 Edition took 1.2636184692382812e-05s
INFO | --- Analysis for CoLChina_sp2000 took 1.9557428359985352s
Availability | SPARQL endpoint availability check for COLINDA - Conference Linked Data took 8.153915405273438e-05s
Availability | VoID file availability check for COLINDA - Conference Linked Data took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for COLINDA - Conference Linked Data took 0.1737685203552246s
Reputation | Calculation of the PageRank for COLINDA - Conference Linked Data took 0.020673513412475586s
Interlinking | Calculation of Degree of Connection for COLINDA - Conference Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for COLINDA - Conference Linked Data took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for COLINDA - Conference Linked Data took 3.981590270996094e-05s
Believability | Calculation of trust value for COLINDA - Conference Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for colinda took 2.0044336318969727s
Availability | SPARQL endpoint availability check for CN  2012 took 8.153915405273438e-05s
Availability | VoID file availability check for CN  2012 took 0.00042128562927246094s
Completeness | Calculation of interlinking completeness for CN  2012 took 0.17456865310668945s
Reputation | Calculation of the PageRank for CN  2012 took 0.020277738571166992s
Interlinking | Calculation of Degree of Connection for CN  2012 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for CN  2012 took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for CN  2012 took 3.457069396972656e-05s
Believability | Calculation of trust value for CN  2012 took 1.1205673217773438e-05s
INFO | --- Analysis for combined-nomenclature-2012 took 1.9781248569488525s
Availability | SPARQL endpoint availability check for Comments on Literature in Literature (CoLiL) took 8.296966552734375e-05s
Availability | VoID file availability check for Comments on Literature in Literature (CoLiL) took 0.00042724609375s
Completeness | Calculation of interlinking completeness for Comments on Literature in Literature (CoLiL) took 0.17980647087097168s
Reputation | Calculation of the PageRank for Comments on Literature in Literature (CoLiL) took 0.020070552825927734s
Interlinking | Calculation of Degree of Connection for Comments on Literature in Literature (CoLiL) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Comments on Literature in Literature (CoLiL) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Comments on Literature in Literature (CoLiL) took 2.7894973754882812e-05s
Believability | Calculation of trust value for Comments on Literature in Literature (CoLiL) took 6.67572021484375e-06s
INFO | --- Analysis for comments-on-literature-in-literature took 1.9614310264587402s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of strawberry by period took 0.00010967254638671875s
Availability | VoID file availability check for Comparative analysis of production volume by area of strawberry by period took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of strawberry by period took 0.173675537109375s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of strawberry by period took 0.02239704132080078s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of strawberry by period took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of strawberry by period took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of strawberry by period took 2.9087066650390625e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of strawberry by period took 1.0967254638671875e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-strawberry-by-period took 1.9940814971923828s
Availability | SPARQL endpoint availability check for Price competitiveness of pear by region took 4.315376281738281e-05s
Availability | VoID file availability check for Price competitiveness of pear by region took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Price competitiveness of pear by region took 0.1756739616394043s
Reputation | Calculation of the PageRank for Price competitiveness of pear by region took 0.02195906639099121s
Interlinking | Calculation of Degree of Connection for Price competitiveness of pear by region took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Price competitiveness of pear by region took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of pear by region took 3.3855438232421875e-05s
Believability | Calculation of trust value for Price competitiveness of pear by region took 1.33514404296875e-05s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period took 1.9942922592163086s
Availability | SPARQL endpoint availability check for Comparative analysis of production volume by area of watermelon by period took 8.654594421386719e-05s
Availability | VoID file availability check for Comparative analysis of production volume by area of watermelon by period took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for Comparative analysis of production volume by area of watermelon by period took 0.1757805347442627s
Reputation | Calculation of the PageRank for Comparative analysis of production volume by area of watermelon by period took 0.020720958709716797s
Interlinking | Calculation of Degree of Connection for Comparative analysis of production volume by area of watermelon by period took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Comparative analysis of production volume by area of watermelon by period took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Comparative analysis of production volume by area of watermelon by period took 3.0994415283203125e-05s
Believability | Calculation of trust value for Comparative analysis of production volume by area of watermelon by period took 9.775161743164062e-06s
INFO | --- Analysis for comparative-analysis-of-production-volume-by-area-of-watermelon-by-period-2 took 1.9933979511260986s
Availability | SPARQL endpoint availability check for Price competitiveness of grape by region took 8.0108642578125e-05s
Availability | VoID file availability check for Price competitiveness of grape by region took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Price competitiveness of grape by region took 0.18410348892211914s
Reputation | Calculation of the PageRank for Price competitiveness of grape by region took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for Price competitiveness of grape by region took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Price competitiveness of grape by region took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Price competitiveness of grape by region took 3.0279159545898438e-05s
Believability | Calculation of trust value for Price competitiveness of grape by region took 1.0013580322265625e-05s
INFO | --- Analysis for comparison-of-price-competitiveness-of-grape-by-region took 2.022385597229004s
Availability | SPARQL endpoint availability check for Computational Historical Semantics in LiLa took 3.981590270996094e-05s
Availability | VoID file availability check for Computational Historical Semantics in LiLa took 0.00037169456481933594s
Completeness | Calculation of interlinking completeness for Computational Historical Semantics in LiLa took 0.1799170970916748s
Reputation | Calculation of the PageRank for Computational Historical Semantics in LiLa took 0.020172834396362305s
Interlinking | Calculation of Degree of Connection for Computational Historical Semantics in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Computational Historical Semantics in LiLa took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Computational Historical Semantics in LiLa took 3.6716461181640625e-05s
Believability | Calculation of trust value for Computational Historical Semantics in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for CompHistSem took 2.006640911102295s
Availability | SPARQL endpoint availability check for Requirements on the COMSODE project based on selected datasets took 3.981590270996094e-05s
Availability | VoID file availability check for Requirements on the COMSODE project based on selected datasets took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for Requirements on the COMSODE project based on selected datasets took 0.17360758781433105s
Reputation | Calculation of the PageRank for Requirements on the COMSODE project based on selected datasets took 0.02183389663696289s
Interlinking | Calculation of Degree of Connection for Requirements on the COMSODE project based on selected datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Requirements on the COMSODE project based on selected datasets took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Requirements on the COMSODE project based on selected datasets took 3.719329833984375e-05s
Believability | Calculation of trust value for Requirements on the COMSODE project based on selected datasets took 5.7220458984375e-06s
INFO | --- Analysis for comsode-d3-2 took 1.9683620929718018s
Availability | SPARQL endpoint availability check for ConceptNet took 8.487701416015625e-05s
Availability | VoID file availability check for ConceptNet took 0.00021386146545410156s
Completeness | Calculation of interlinking completeness for ConceptNet took 0.1773066520690918s
Reputation | Calculation of the PageRank for ConceptNet took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for ConceptNet took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ConceptNet took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for ConceptNet took 3.814697265625e-05s
Believability | Calculation of trust value for ConceptNet took 1.0013580322265625e-05s
INFO | --- Analysis for conceptnet took 1.9871575832366943s
Availability | SPARQL endpoint availability check for 2011 US Congress People took 0.000102996826171875s
Availability | VoID file availability check for 2011 US Congress People took 0.0004162788391113281s
Completeness | Calculation of interlinking completeness for 2011 US Congress People took 0.18257713317871094s
Reputation | Calculation of the PageRank for 2011 US Congress People took 0.020687103271484375s
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.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for 2011 US Congress People took 8.130073547363281e-05s
Believability | Calculation of trust value for 2011 US Congress People took 9.5367431640625e-06s
INFO | --- Analysis for congresspeople took 1.9767017364501953s
Availability | SPARQL endpoint availability check for MIMO took 7.963180541992188e-05s
Availability | VoID file availability check for MIMO took 0.0004143714904785156s
Completeness | Calculation of interlinking completeness for MIMO took 0.17838191986083984s
Reputation | Calculation of the PageRank for MIMO took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for MIMO took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for MIMO took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for MIMO took 1.2159347534179688e-05s
Believability | Calculation of trust value for MIMO took 1.0728836059570312e-05s
INFO | --- Analysis for CONNECTED took 2.001056432723999s
Availability | SPARQL endpoint availability check for LODsyndesis Dataset took 8.177757263183594e-05s
Availability | VoID file availability check for LODsyndesis Dataset took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for LODsyndesis Dataset took 0.17235708236694336s
Reputation | Calculation of the PageRank for LODsyndesis Dataset took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for LODsyndesis Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LODsyndesis Dataset took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for LODsyndesis Dataset took 3.123283386230469e-05s
Believability | Calculation of trust value for LODsyndesis Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for connectivity-of-lod-datasets took 2.024268865585327s
Availability | SPARQL endpoint availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 3.9577484130859375e-05s
Availability | VoID file availability check for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.17984700202941895s
Reputation | Calculation of the PageRank for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.020415067672729492s
Interlinking | Calculation of Degree of Connection for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Copac: union catalogue of major University, Specialist, and National Libraries in the UK and Ireland took 0.0007159709930419922s
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 1.1920928955078125e-05s
INFO | --- Analysis for copac-library-catalogue took 1.9916925430297852s
Availability | SPARQL endpoint availability check for Copyright Free Music took 8.535385131835938e-05s
Availability | VoID file availability check for Copyright Free Music took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Copyright Free Music took 0.17505693435668945s
Reputation | Calculation of the PageRank for Copyright Free Music took 0.020865917205810547s
Interlinking | Calculation of Degree of Connection for Copyright Free Music took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Copyright Free Music took 0.0007615089416503906s
Interlinking | Calculation of Clustering coefficient for Copyright Free Music took 3.0994415283203125e-05s
Believability | Calculation of trust value for Copyright Free Music took 5.245208740234375e-06s
INFO | --- Analysis for Copyright_Free_Music took 1.9684290885925293s
Availability | SPARQL endpoint availability check for CopyrightTermBank took 4.00543212890625e-05s
Availability | VoID file availability check for CopyrightTermBank took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for CopyrightTermBank took 0.1840970516204834s
Reputation | Calculation of the PageRank for CopyrightTermBank took 0.022208452224731445s
Interlinking | Calculation of Degree of Connection for CopyrightTermBank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for CopyrightTermBank took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for CopyrightTermBank took 6.532669067382812e-05s
Believability | Calculation of trust value for CopyrightTermBank took 1.0967254638671875e-05s
INFO | --- Analysis for copyrighttermbank took 1.9840948581695557s
Availability | SPARQL endpoint availability check for CORE - Semantic Similarity of Open Access publications took 8.416175842285156e-05s
Availability | VoID file availability check for CORE - Semantic Similarity of Open Access publications took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for CORE - Semantic Similarity of Open Access publications took 0.17993617057800293s
Reputation | Calculation of the PageRank for CORE - Semantic Similarity of Open Access publications took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for CORE - Semantic Similarity of Open Access publications took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CORE - Semantic Similarity of Open Access publications took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for CORE - Semantic Similarity of Open Access publications took 3.695487976074219e-05s
Believability | Calculation of trust value for CORE - Semantic Similarity of Open Access publications took 1.1205673217773438e-05s
INFO | --- Analysis for core took 2.0662693977355957s
Availability | SPARQL endpoint availability check for Corine linked dataset @PSNC took 4.029273986816406e-05s
Availability | VoID file availability check for Corine linked dataset @PSNC took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Corine linked dataset @PSNC took 0.19096708297729492s
Reputation | Calculation of the PageRank for Corine linked dataset @PSNC took 0.02050924301147461s
Interlinking | Calculation of Degree of Connection for Corine linked dataset @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Corine linked dataset @PSNC took 0.0007183551788330078s
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 1.2159347534179688e-05s
INFO | --- Analysis for Corine_linked_dataset took 1.9800150394439697s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 8.082389831542969e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.17335247993469238s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.02059459686279297s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Hongcheon) Environmental Status took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Hongcheon) Environmental Status took 2.86102294921875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Hongcheon) Environmental Status took 1.3113021850585938e-05s
INFO | --- Analysis for corn took 1.9844646453857422s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 4.1961669921875e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Goesan) Environmental Status took 0.00021219253540039062s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Goesan) Environmental Status took 0.17179274559020996s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Goesan) Environmental Status took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Corn's Famous mountainous district (Goesan) Environmental Status took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corn's Famous mountainous district (Goesan) Environmental Status took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Goesan) Environmental Status took 3.0040740966796875e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Goesan) Environmental Status took 1.2874603271484375e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-goesan-environmental-status took 1.9895226955413818s
Availability | SPARQL endpoint availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 8.058547973632812e-05s
Availability | VoID file availability check for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.00028324127197265625s
Completeness | Calculation of interlinking completeness for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.18137025833129883s
Reputation | Calculation of the PageRank for Corn's Famous mountainous district (Jeongseon) Environmental Status took 0.020676374435424805s
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.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Corn's Famous mountainous district (Jeongseon) Environmental Status took 3.24249267578125e-05s
Believability | Calculation of trust value for Corn's Famous mountainous district (Jeongseon) Environmental Status took 1.33514404296875e-05s
INFO | --- Analysis for corn-s-famous-mountainous-district-jeongseon-environmental-status took 1.9952402114868164s
Availability | SPARQL endpoint availability check for Cornetto1.2 took 8.225440979003906e-05s
Availability | VoID file availability check for Cornetto1.2 took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Cornetto1.2 took 0.1805417537689209s
Reputation | Calculation of the PageRank for Cornetto1.2 took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for Cornetto1.2 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Cornetto1.2 took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Cornetto1.2 took 5.6743621826171875e-05s
Believability | Calculation of trust value for Cornetto1.2 took 1.3113021850585938e-05s
INFO | --- Analysis for cornetto took 1.973459243774414s
Availability | SPARQL endpoint availability check for Corporate Body Named Authority List  took 4.172325134277344e-05s
Availability | VoID file availability check for Corporate Body Named Authority List  took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for Corporate Body Named Authority List  took 0.1747589111328125s
Reputation | Calculation of the PageRank for Corporate Body Named Authority List  took 0.020317792892456055s
Interlinking | Calculation of Degree of Connection for Corporate Body Named Authority List  took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corporate Body Named Authority List  took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Corporate Body Named Authority List  took 4.863739013671875e-05s
Believability | Calculation of trust value for Corporate Body Named Authority List  took 1.0013580322265625e-05s
INFO | --- Analysis for corporate-body took 1.9598991870880127s
Availability | SPARQL endpoint availability check for Corpus Fibonacci in LiLa took 7.987022399902344e-05s
Availability | VoID file availability check for Corpus Fibonacci in LiLa took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Corpus Fibonacci in LiLa took 0.17994308471679688s
Reputation | Calculation of the PageRank for Corpus Fibonacci in LiLa took 0.020595312118530273s
Interlinking | Calculation of Degree of Connection for Corpus Fibonacci in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Corpus Fibonacci in LiLa took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Corpus Fibonacci in LiLa took 3.528594970703125e-05s
Believability | Calculation of trust value for Corpus Fibonacci in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for CorpusFibonacci took 2.0035409927368164s
Availability | SPARQL endpoint availability check for CORS Check - HTTP Header Logs for Linked Open Data took 3.910064697265625e-05s
Availability | VoID file availability check for CORS Check - HTTP Header Logs for Linked Open Data took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for CORS Check - HTTP Header Logs for Linked Open Data took 0.18111038208007812s
Reputation | Calculation of the PageRank for CORS Check - HTTP Header Logs for Linked Open Data took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for CORS Check - HTTP Header Logs for Linked Open Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CORS Check - HTTP Header Logs for Linked Open Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for CORS Check - HTTP Header Logs for Linked Open Data took 2.765655517578125e-05s
Believability | Calculation of trust value for CORS Check - HTTP Header Logs for Linked Open Data took 1.2159347534179688e-05s
INFO | --- Analysis for corscheck took 1.9795863628387451s
Availability | SPARQL endpoint availability check for Country Name Authority List took 8.535385131835938e-05s
Availability | VoID file availability check for Country Name Authority List took 0.00023293495178222656s
Completeness | Calculation of interlinking completeness for Country Name Authority List took 0.1836836338043213s
Reputation | Calculation of the PageRank for Country Name Authority List took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for Country Name Authority List took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Country Name Authority List took 0.0006973743438720703s
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 1.33514404296875e-05s
INFO | --- Analysis for country-authority-list took 2.0242645740509033s
Availability | SPARQL endpoint availability check for Courts thesaurus took 8.296966552734375e-05s
Availability | VoID file availability check for Courts thesaurus took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Courts thesaurus took 0.18013286590576172s
Reputation | Calculation of the PageRank for Courts thesaurus took 0.021155834197998047s
Interlinking | Calculation of Degree of Connection for Courts thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Courts thesaurus took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Courts thesaurus took 6.461143493652344e-05s
Believability | Calculation of trust value for Courts thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for courts-thesaurus took 1.9720752239227295s
Availability | SPARQL endpoint availability check for Covid-on-the-Web Dataset took 4.00543212890625e-05s
Availability | VoID file availability check for Covid-on-the-Web Dataset took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Covid-on-the-Web Dataset took 0.18438458442687988s
Reputation | Calculation of the PageRank for Covid-on-the-Web Dataset took 0.022542953491210938s
Interlinking | Calculation of Degree of Connection for Covid-on-the-Web Dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Covid-on-the-Web Dataset took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Covid-on-the-Web Dataset took 7.653236389160156e-05s
Believability | Calculation of trust value for Covid-on-the-Web Dataset took 1.3589859008789062e-05s
INFO | --- Analysis for Covid-on-the-Web took 1.976938247680664s
Availability | SPARQL endpoint availability check for CPA 2008 took 8.225440979003906e-05s
Availability | VoID file availability check for CPA 2008 took 0.00023984909057617188s
Completeness | Calculation of interlinking completeness for CPA 2008 took 0.17320609092712402s
Reputation | Calculation of the PageRank for CPA 2008 took 0.021051406860351562s
Interlinking | Calculation of Degree of Connection for CPA 2008 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CPA 2008 took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for CPA 2008 took 3.4809112548828125e-05s
Believability | Calculation of trust value for CPA 2008 took 7.867813110351562e-06s
INFO | --- Analysis for cpa-2008 took 2.0152816772460938s
Availability | SPARQL endpoint availability check for Cooperative Patent Classification took 4.0531158447265625e-05s
Availability | VoID file availability check for Cooperative Patent Classification took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Cooperative Patent Classification took 0.18086624145507812s
Reputation | Calculation of the PageRank for Cooperative Patent Classification took 0.020247459411621094s
Interlinking | Calculation of Degree of Connection for Cooperative Patent Classification took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Cooperative Patent Classification took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Cooperative Patent Classification took 3.3855438232421875e-05s
Believability | Calculation of trust value for Cooperative Patent Classification took 1.0967254638671875e-05s
INFO | --- Analysis for CPC took 1.9617292881011963s
Availability | SPARQL endpoint availability check for CPC 2008 took 9.822845458984375e-05s
Availability | VoID file availability check for CPC 2008 took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for CPC 2008 took 0.1822509765625s
Reputation | Calculation of the PageRank for CPC 2008 took 0.020241975784301758s
Interlinking | Calculation of Degree of Connection for CPC 2008 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for CPC 2008 took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for CPC 2008 took 3.504753112792969e-05s
Believability | Calculation of trust value for CPC 2008 took 1.0967254638671875e-05s
INFO | --- Analysis for cpc-2008 took 1.9838597774505615s
Availability | SPARQL endpoint availability check for CPV  2003 took 8.082389831542969e-05s
Availability | VoID file availability check for CPV  2003 took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for CPV  2003 took 0.17275476455688477s
Reputation | Calculation of the PageRank for CPV  2003 took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for CPV  2003 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CPV  2003 took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for CPV  2003 took 3.4332275390625e-05s
Believability | Calculation of trust value for CPV  2003 took 1.1205673217773438e-05s
INFO | --- Analysis for cpv-2003 took 1.9601972103118896s
Availability | SPARQL endpoint availability check for CPV 2008 took 3.910064697265625e-05s
Availability | VoID file availability check for CPV 2008 took 0.00020432472229003906s
Completeness | Calculation of interlinking completeness for CPV 2008 took 0.1793498992919922s
Reputation | Calculation of the PageRank for CPV 2008 took 0.02195906639099121s
Interlinking | Calculation of Degree of Connection for CPV 2008 took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for CPV 2008 took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for CPV 2008 took 4.673004150390625e-05s
Believability | Calculation of trust value for CPV 2008 took 1.0728836059570312e-05s
INFO | --- Analysis for cpv-2008 took 1.976771593093872s
Availability | SPARQL endpoint availability check for crowdsourcing-fb took 7.987022399902344e-05s
Availability | VoID file availability check for crowdsourcing-fb took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for crowdsourcing-fb took 0.1814868450164795s
Reputation | Calculation of the PageRank for crowdsourcing-fb took 0.02043461799621582s
Interlinking | Calculation of Degree of Connection for crowdsourcing-fb took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for crowdsourcing-fb took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for crowdsourcing-fb took 3.504753112792969e-05s
Believability | Calculation of trust value for crowdsourcing-fb took 1.0728836059570312e-05s
INFO | --- Analysis for crowdsourcing-fb took 1.9919803142547607s
Availability | SPARQL endpoint availability check for CRTM took 8.20159912109375e-05s
Availability | VoID file availability check for CRTM took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for CRTM took 0.1824507713317871s
Reputation | Calculation of the PageRank for CRTM took 0.02037358283996582s
Interlinking | Calculation of Degree of Connection for CRTM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CRTM took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for CRTM took 2.9802322387695312e-05s
Believability | Calculation of trust value for CRTM took 1.239776611328125e-05s
INFO | --- Analysis for crtm took 1.9921207427978516s
Availability | SPARQL endpoint availability check for Crystal Eye: Aggregated Crystallographic Data took 3.910064697265625e-05s
Availability | VoID file availability check for Crystal Eye: Aggregated Crystallographic Data took 0.00044274330139160156s
Completeness | Calculation of interlinking completeness for Crystal Eye: Aggregated Crystallographic Data took 0.18135762214660645s
Reputation | Calculation of the PageRank for Crystal Eye: Aggregated Crystallographic Data took 0.020107746124267578s
Interlinking | Calculation of Degree of Connection for Crystal Eye: Aggregated Crystallographic Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Crystal Eye: Aggregated Crystallographic Data took 0.0006985664367675781s
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 1.0967254638671875e-05s
INFO | --- Analysis for crystal-eye took 1.9538757801055908s
Availability | SPARQL endpoint availability check for CTIC Public Dataset Catalogs took 8.153915405273438e-05s
Availability | VoID file availability check for CTIC Public Dataset Catalogs took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for CTIC Public Dataset Catalogs took 0.18542075157165527s
Reputation | Calculation of the PageRank for CTIC Public Dataset Catalogs took 0.020572900772094727s
Interlinking | Calculation of Degree of Connection for CTIC Public Dataset Catalogs took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for CTIC Public Dataset Catalogs took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for CTIC Public Dataset Catalogs took 4.6253204345703125e-05s
Believability | Calculation of trust value for CTIC Public Dataset Catalogs took 1.2636184692382812e-05s
INFO | --- Analysis for ctic-public-dataset took 1.984189748764038s
Availability | SPARQL endpoint availability check for Cultivation status of GMO crops took 7.963180541992188e-05s
Availability | VoID file availability check for Cultivation status of GMO crops took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Cultivation status of GMO crops took 0.17713522911071777s
Reputation | Calculation of the PageRank for Cultivation status of GMO crops took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Cultivation status of GMO crops took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Cultivation status of GMO crops took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Cultivation status of GMO crops took 3.0279159545898438e-05s
Believability | Calculation of trust value for Cultivation status of GMO crops took 1.2874603271484375e-05s
INFO | --- Analysis for cultivation-status-of-gmo-crops took 1.950463056564331s
Availability | SPARQL endpoint availability check for CulturaLinkedData took 2.387824773788452s
Availability | VoID file availability check for CulturaLinkedData took 0.0004801750183105469s
Extra | Recovery of all triples for CulturaLinkedData took 142.0573697090149s
Performance | Total latancy measurement for CulturaLinkedData took 2.721747398376465s
Amount of data | Number of triples check for CulturaLinkedData took 0.764296293258667s
Interoperability | New terms check for CulturaLinkedData took 2.2630937099456787s
Versatility | Languages check for CulturaLinkedData took 61.06165790557861s
Interpretability | Number of blank nodes check for CulturaLinkedData took 1.9910097122192383s
Interpretability | RDF structures check for CulturaLinkedData took 0.46758365631103516s
Versatility | Serialization formats check for CulturaLinkedData took 2.3413467407226562s
Availability | RDF dump link check for CulturaLinkedData took 2.061932325363159s
License | MR license check for CulturaLinkedData took 0.7490558624267578s
License | HR license check for CulturaLinkedData took 63.295151710510254s
Amount of data | Number of property check for CulturaLinkedData took 1.9873576164245605s
Understandability | Number of label check for CulturaLinkedData took 1.2020759582519531s
Understandability | URI regex check for CulturaLinkedData took 0.6064772605895996s
Understandability | Vocabs check for CulturaLinkedData took 2.1013171672821045s
Verifiability | Authors check for CulturaLinkedData took 0.3182072639465332s
Verifiability | Publishers check for CulturaLinkedData took 2.1016955375671387s
Performance | Throughput check for CulturaLinkedData took 22.608543157577515s
Amount of data | Check the number of entities for CulturaLinkedData took 8.7738037109375e-05s
Verifiability | Contribs. check for CulturaLinkedData took 2.073029041290283s
Interlinking | sameAs chians check for CulturaLinkedData took 2.2042009830474854s
Interlinking | skos check for CulturaLinkedData took 0.5263333320617676s
Interlinking | skos check for CulturaLinkedData took 0.18668723106384277s
Timeliness | dataset update frequency check for CulturaLinkedData took 2.2039082050323486s
Currency | Creation date check for CulturaLinkedData took 2.323559284210205s
Currency | Modification date check for CulturaLinkedData took 3.9780213832855225s
Rep.Conc. | URIs length for CulturaLinkedData took 56.39201831817627s
Interoperability | New vocabularies check for CulturaLinkedData took 9.059906005859375e-06s
Consistency | Deprecated classes/propertiers check for CulturaLinkedData took 0.18902969360351562s
Accuracy | Check Functional Property for CulturaLinkedData took 2.038536310195923s
Accuracy | Check Inverse Functional Property for CulturaLinkedData took 1.9989545345306396s
Accuracy | Check Empty annotation labels for CulturaLinkedData took 44.7066433429718s
Accuracy | Check White space in annotation for CulturaLinkedData took 1.6085739135742188s
Accuracy | Check Datatype consistency for CulturaLinkedData took 1.304002285003662s
Consistency | Disjoint class check for CulturaLinkedData took 0.22558927536010742s
Consistency | Check Misplaced properties for CulturaLinkedData took 12.021337985992432s
Consistency | Misplaced classes for CulturaLinkedData took 6.093447685241699s
Consistency | Check Ontology hijacking for CulturaLinkedData took 44.48405480384827s
Consistency | Check Invalid usage of undefined classes for CulturaLinkedData took 1.3635683059692383s
Consistency | Check Invalid usage of undefined properties for CulturaLinkedData took 9.343189477920532s
Conciseness | Check Extensional conciseness for CulturaLinkedData took 1.4040942192077637s
Conciseness | Check Intensional conciseness for CulturaLinkedData took 0.19133400917053223s
Security | Sign check for CulturaLinkedData took 1.031691312789917s
Availability | Check URIs Dereferenciability for CulturaLinkedData took 16.369677305221558s
Completeness | Calculation of interlinking completeness for CulturaLinkedData took 0.32627272605895996s
Reputation | Calculation of the PageRank for CulturaLinkedData took 0.021067142486572266s
Interlinking | Calculation of Degree of Connection for CulturaLinkedData took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for CulturaLinkedData took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for CulturaLinkedData took 4.506111145019531e-05s
Interoperability | Check the re-using of existing vocabs for CulturaLinkedData took 2.1457672119140625e-06s
Believability | Calculation of trust value for CulturaLinkedData took 1.2636184692382812e-05s
INFO | --- Analysis for culturalinkeddata took 634.8418850898743s
Availability | SPARQL endpoint availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 9.250640869140625e-05s
Availability | VoID file availability check for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Data about business entities from the ARES system - business registry of the Czech Republic took 0.17772769927978516s
Reputation | Calculation of the PageRank for Data about business entities from the ARES system - business registry of the Czech Republic took 0.020226001739501953s
Interlinking | Calculation of Degree of Connection for Data about business entities from the ARES system - business registry of the Czech Republic took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Data about business entities from the ARES system - business registry of the Czech Republic took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Data about business entities from the ARES system - business registry of the Czech Republic took 4.8160552978515625e-05s
Believability | Calculation of trust value for Data about business entities from the ARES system - business registry of the Czech Republic took 1.2874603271484375e-05s
INFO | --- Analysis for cz-ares-or took 1.9725992679595947s
Availability | SPARQL endpoint availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 8.416175842285156e-05s
Availability | VoID file availability check for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0004878044128417969s
Completeness | Calculation of interlinking completeness for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.17571544647216797s
Reputation | Calculation of the PageRank for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Data about Czech business entities from the ARES system - Trade Licensing Register took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Data about Czech business entities from the ARES system - Trade Licensing Register took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Data about Czech business entities from the ARES system - Trade Licensing Register took 3.2901763916015625e-05s
Believability | Calculation of trust value for Data about Czech business entities from the ARES system - Trade Licensing Register took 1.239776611328125e-05s
INFO | --- Analysis for cz-ares-rzp took 2.01185941696167s
Availability | SPARQL endpoint availability check for Chemicals reported to the Integrated register of pollution took 4.124641418457031e-05s
Availability | VoID file availability check for Chemicals reported to the Integrated register of pollution took 0.0005056858062744141s
Completeness | Calculation of interlinking completeness for Chemicals reported to the Integrated register of pollution took 0.18252038955688477s
Reputation | Calculation of the PageRank for Chemicals reported to the Integrated register of pollution took 0.022922039031982422s
Interlinking | Calculation of Degree of Connection for Chemicals reported to the Integrated register of pollution took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Chemicals reported to the Integrated register of pollution took 0.0009300708770751953s
Interlinking | Calculation of Clustering coefficient for Chemicals reported to the Integrated register of pollution took 3.528594970703125e-05s
Believability | Calculation of trust value for Chemicals reported to the Integrated register of pollution took 1.1920928955078125e-05s
INFO | --- Analysis for cz-cenia-irz-chemicals took 1.9588520526885986s
Availability | SPARQL endpoint availability check for Integrated pollution registry took 4.029273986816406e-05s
Availability | VoID file availability check for Integrated pollution registry took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Integrated pollution registry took 0.18265795707702637s
Reputation | Calculation of the PageRank for Integrated pollution registry took 0.020208358764648438s
Interlinking | Calculation of Degree of Connection for Integrated pollution registry took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Integrated pollution registry took 0.0009706020355224609s
Interlinking | Calculation of Clustering coefficient for Integrated pollution registry took 4.267692565917969e-05s
Believability | Calculation of trust value for Integrated pollution registry took 1.2636184692382812e-05s
INFO | --- Analysis for cz-cenia-pollution took 1.9650311470031738s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Contracts took 4.0531158447265625e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Contracts took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Contracts took 0.18145132064819336s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Contracts took 0.021149873733520508s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Contracts took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Contracts took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Contracts took 3.409385681152344e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Contracts took 1.239776611328125e-05s
INFO | --- Analysis for cz-contracts took 1.9555933475494385s
Availability | SPARQL endpoint availability check for List of courts of the Czech Republic took 8.296966552734375e-05s
Availability | VoID file availability check for List of courts of the Czech Republic took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for List of courts of the Czech Republic took 0.1813945770263672s
Reputation | Calculation of the PageRank for List of courts of the Czech Republic took 0.020791053771972656s
Interlinking | Calculation of Degree of Connection for List of courts of the Czech Republic took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for List of courts of the Czech Republic took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for List of courts of the Czech Republic took 2.765655517578125e-05s
Believability | Calculation of trust value for List of courts of the Czech Republic took 6.9141387939453125e-06s
INFO | --- Analysis for cz-courts took 2.017533540725708s
Availability | SPARQL endpoint availability check for Bans of the Czech Trade Inspection Authority took 8.511543273925781e-05s
Availability | VoID file availability check for Bans of the Czech Trade Inspection Authority took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Bans of the Czech Trade Inspection Authority took 0.17971587181091309s
Reputation | Calculation of the PageRank for Bans of the Czech Trade Inspection Authority took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for Bans of the Czech Trade Inspection Authority took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Bans of the Czech Trade Inspection Authority took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Bans of the Czech Trade Inspection Authority took 3.1948089599609375e-05s
Believability | Calculation of trust value for Bans of the Czech Trade Inspection Authority took 1.2159347534179688e-05s
INFO | --- Analysis for cz-ctia-bans took 1.9950990676879883s
Availability | SPARQL endpoint availability check for Confiscations of the Czech Trade Inspection Authority took 8.416175842285156e-05s
Availability | VoID file availability check for Confiscations of the Czech Trade Inspection Authority took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for Confiscations of the Czech Trade Inspection Authority took 0.17368578910827637s
Reputation | Calculation of the PageRank for Confiscations of the Czech Trade Inspection Authority took 0.020163536071777344s
Interlinking | Calculation of Degree of Connection for Confiscations of the Czech Trade Inspection Authority took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Confiscations of the Czech Trade Inspection Authority took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Confiscations of the Czech Trade Inspection Authority took 3.457069396972656e-05s
Believability | Calculation of trust value for Confiscations of the Czech Trade Inspection Authority took 1.3113021850585938e-05s
INFO | --- Analysis for cz-ctia-confiscations took 1.9952733516693115s
Availability | SPARQL endpoint availability check for Focus of the Czech Trade Inspection Authority's inspections took 4.029273986816406e-05s
Availability | VoID file availability check for Focus of the Czech Trade Inspection Authority's inspections took 0.00020623207092285156s
Completeness | Calculation of interlinking completeness for Focus of the Czech Trade Inspection Authority's inspections took 0.17917823791503906s
Reputation | Calculation of the PageRank for Focus of the Czech Trade Inspection Authority's inspections took 0.020368576049804688s
Interlinking | Calculation of Degree of Connection for Focus of the Czech Trade Inspection Authority's inspections took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Focus of the Czech Trade Inspection Authority's inspections took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Focus of the Czech Trade Inspection Authority's inspections took 3.552436828613281e-05s
Believability | Calculation of trust value for Focus of the Czech Trade Inspection Authority's inspections took 5.0067901611328125e-06s
INFO | --- Analysis for cz-ctia-focus took 1.9246487617492676s
Availability | SPARQL endpoint availability check for Inspections of the Czech Trade Inspection Authority took 9.560585021972656e-05s
Availability | VoID file availability check for Inspections of the Czech Trade Inspection Authority took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Inspections of the Czech Trade Inspection Authority took 0.1787886619567871s
Reputation | Calculation of the PageRank for Inspections of the Czech Trade Inspection Authority took 0.020886898040771484s
Interlinking | Calculation of Degree of Connection for Inspections of the Czech Trade Inspection Authority took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Inspections of the Czech Trade Inspection Authority took 0.000978708267211914s
Interlinking | Calculation of Clustering coefficient for Inspections of the Czech Trade Inspection Authority took 5.245208740234375e-05s
Believability | Calculation of trust value for Inspections of the Czech Trade Inspection Authority took 1.3589859008789062e-05s
INFO | --- Analysis for cz-ctia-inspections took 2.171332836151123s
Availability | SPARQL endpoint availability check for Sanctions of the Czech Trade Inspection Authority took 8.20159912109375e-05s
Availability | VoID file availability check for Sanctions of the Czech Trade Inspection Authority took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for Sanctions of the Czech Trade Inspection Authority took 0.17403793334960938s
Reputation | Calculation of the PageRank for Sanctions of the Czech Trade Inspection Authority took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for Sanctions of the Czech Trade Inspection Authority took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sanctions of the Czech Trade Inspection Authority took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Sanctions of the Czech Trade Inspection Authority took 3.600120544433594e-05s
Believability | Calculation of trust value for Sanctions of the Czech Trade Inspection Authority took 1.2874603271484375e-05s
INFO | --- Analysis for cz-ctia-sanctions took 1.9706017971038818s
Availability | SPARQL endpoint availability check for Cadastre offices from Czech land registry took 8.344650268554688e-05s
Availability | VoID file availability check for Cadastre offices from Czech land registry took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for Cadastre offices from Czech land registry took 0.17519211769104004s
Reputation | Calculation of the PageRank for Cadastre offices from Czech land registry took 0.0202181339263916s
Interlinking | Calculation of Degree of Connection for Cadastre offices from Czech land registry took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Cadastre offices from Czech land registry took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Cadastre offices from Czech land registry took 4.1961669921875e-05s
Believability | Calculation of trust value for Cadastre offices from Czech land registry took 1.2636184692382812e-05s
INFO | --- Analysis for cz-cuzk-cadastre-offices took 2.0087318420410156s
Availability | SPARQL endpoint availability check for Code lists of the legal relationships and documents took 0.00010085105895996094s
Availability | VoID file availability check for Code lists of the legal relationships and documents took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for Code lists of the legal relationships and documents took 0.17444419860839844s
Reputation | Calculation of the PageRank for Code lists of the legal relationships and documents took 0.021535873413085938s
Interlinking | Calculation of Degree of Connection for Code lists of the legal relationships and documents took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Code lists of the legal relationships and documents took 0.0007956027984619141s
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 1.3589859008789062e-05s
INFO | --- Analysis for cz-cuzk-legal-relationships-documents took 1.971796989440918s
Availability | SPARQL endpoint availability check for Average salaries in regions of Czech republic took 4.124641418457031e-05s
Availability | VoID file availability check for Average salaries in regions of Czech republic took 0.00029158592224121094s
Completeness | Calculation of interlinking completeness for Average salaries in regions of Czech republic took 0.1826472282409668s
Reputation | Calculation of the PageRank for Average salaries in regions of Czech republic took 0.020316123962402344s
Interlinking | Calculation of Degree of Connection for Average salaries in regions of Czech republic took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Average salaries in regions of Czech republic took 0.0009105205535888672s
Interlinking | Calculation of Clustering coefficient for Average salaries in regions of Czech republic took 4.410743713378906e-05s
Believability | Calculation of trust value for Average salaries in regions of Czech republic took 1.3828277587890625e-05s
INFO | --- Analysis for cz-czso-average-salaries took 1.9806218147277832s
Availability | SPARQL endpoint availability check for Deaths by selected causes of death in regions of Czech Republic took 4.076957702636719e-05s
Availability | VoID file availability check for Deaths by selected causes of death in regions of Czech Republic took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Deaths by selected causes of death in regions of Czech Republic took 0.17818117141723633s
Reputation | Calculation of the PageRank for Deaths by selected causes of death in regions of Czech Republic took 0.02094745635986328s
Interlinking | Calculation of Degree of Connection for Deaths by selected causes of death in regions of Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Deaths by selected causes of death in regions of Czech Republic took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Deaths by selected causes of death in regions of Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Deaths by selected causes of death in regions of Czech Republic took 1.3113021850585938e-05s
INFO | --- Analysis for cz-czso-deaths-by-selected-causes-of-death took 1.9537861347198486s
Availability | SPARQL endpoint availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.029273986816406e-05s
Availability | VoID file availability check for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.17285442352294922s
Reputation | Calculation of the PageRank for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.02232527732849121s
Interlinking | Calculation of Degree of Connection for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Number of inhabitants in districts of Czech Republic in 5year age categories took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Number of inhabitants in districts of Czech Republic in 5year age categories took 4.00543212890625e-05s
Believability | Calculation of trust value for Number of inhabitants in districts of Czech Republic in 5year age categories took 1.1682510375976562e-05s
INFO | --- Analysis for cz-czso-demography-in-regions-czech-republic-age-categories took 1.978074073791504s
Availability | SPARQL endpoint availability check for Job applicants in regions of Czech Republic took 7.939338684082031e-05s
Availability | VoID file availability check for Job applicants in regions of Czech Republic took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for Job applicants in regions of Czech Republic took 0.18808317184448242s
Reputation | Calculation of the PageRank for Job applicants in regions of Czech Republic took 0.02174067497253418s
Interlinking | Calculation of Degree of Connection for Job applicants in regions of Czech Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Job applicants in regions of Czech Republic took 0.0008435249328613281s
Interlinking | Calculation of Clustering coefficient for Job applicants in regions of Czech Republic took 3.910064697265625e-05s
Believability | Calculation of trust value for Job applicants in regions of Czech Republic took 9.059906005859375e-06s
INFO | --- Analysis for cz-czso-job-applicants took 1.956301212310791s
Availability | SPARQL endpoint availability check for Job applicants and unemployment rate in regions of Czech Republic took 4.267692565917969e-05s
Availability | VoID file availability check for Job applicants and unemployment rate in regions of Czech Republic took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for Job applicants and unemployment rate in regions of Czech Republic took 0.18730497360229492s
Reputation | Calculation of the PageRank for Job applicants and unemployment rate in regions of Czech Republic took 0.020168304443359375s
Interlinking | Calculation of Degree of Connection for Job applicants and unemployment rate in regions of Czech Republic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Job applicants and unemployment rate in regions of Czech Republic took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Job applicants and unemployment rate in regions of Czech Republic took 3.7670135498046875e-05s
Believability | Calculation of trust value for Job applicants and unemployment rate in regions of Czech Republic took 8.106231689453125e-06s
INFO | --- Analysis for cz-czso-job-applicants-and-unemployment-rate took 1.9850897789001465s
Availability | SPARQL endpoint availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 4.0531158447265625e-05s
Availability | VoID file availability check for Structure of regions of Czech Republic according to Czech Statistical Office took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for Structure of regions of Czech Republic according to Czech Statistical Office took 0.18380331993103027s
Reputation | Calculation of the PageRank for Structure of regions of Czech Republic according to Czech Statistical Office took 0.020160198211669922s
Interlinking | Calculation of Degree of Connection for Structure of regions of Czech Republic according to Czech Statistical Office took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Structure of regions of Czech Republic according to Czech Statistical Office took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Structure of regions of Czech Republic according to Czech Statistical Office took 3.4332275390625e-05s
Believability | Calculation of trust value for Structure of regions of Czech Republic according to Czech Statistical Office took 7.867813110351562e-06s
INFO | --- Analysis for cz-czso-regions took 1.9684860706329346s
Availability | SPARQL endpoint availability check for Selected public health indicators in regions of Czech republic took 4.00543212890625e-05s
Availability | VoID file availability check for Selected public health indicators in regions of Czech republic took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Selected public health indicators in regions of Czech republic took 0.17529678344726562s
Reputation | Calculation of the PageRank for Selected public health indicators in regions of Czech republic took 0.02034139633178711s
Interlinking | Calculation of Degree of Connection for Selected public health indicators in regions of Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Selected public health indicators in regions of Czech republic took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Selected public health indicators in regions of Czech republic took 3.9577484130859375e-05s
Believability | Calculation of trust value for Selected public health indicators in regions of Czech republic took 5.245208740234375e-06s
INFO | --- Analysis for cz-czso-selected-indicators-of-public-health took 1.9355530738830566s
Availability | SPARQL endpoint availability check for Social service facilities and nursing in districts of Czech republic took 4.3392181396484375e-05s
Availability | VoID file availability check for Social service facilities and nursing in districts of Czech republic took 0.0002071857452392578s
Completeness | Calculation of interlinking completeness for Social service facilities and nursing in districts of Czech republic took 0.1767890453338623s
Reputation | Calculation of the PageRank for Social service facilities and nursing in districts of Czech republic took 0.020424842834472656s
Interlinking | Calculation of Degree of Connection for Social service facilities and nursing in districts of Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social service facilities and nursing in districts of Czech republic took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Social service facilities and nursing in districts of Czech republic took 3.838539123535156e-05s
Believability | Calculation of trust value for Social service facilities and nursing in districts of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-social-service-facilities took 1.9707469940185547s
Availability | SPARQL endpoint availability check for Unemployment rate in regions of Czech republic took 3.8623809814453125e-05s
Availability | VoID file availability check for Unemployment rate in regions of Czech republic took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Unemployment rate in regions of Czech republic took 0.19014382362365723s
Reputation | Calculation of the PageRank for Unemployment rate in regions of Czech republic took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Unemployment rate in regions of Czech republic took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Unemployment rate in regions of Czech republic took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Unemployment rate in regions of Czech republic took 3.886222839355469e-05s
Believability | Calculation of trust value for Unemployment rate in regions of Czech republic took 5.4836273193359375e-06s
INFO | --- Analysis for cz-czso-unemployment-rate took 1.9378323554992676s
Availability | SPARQL endpoint availability check for ATC groups took 8.58306884765625e-05s
Availability | VoID file availability check for ATC groups took 0.0005369186401367188s
Completeness | Calculation of interlinking completeness for ATC groups took 0.17411136627197266s
Reputation | Calculation of the PageRank for ATC groups took 0.02157735824584961s
Interlinking | Calculation of Degree of Connection for ATC groups took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ATC groups took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ATC groups took 6.818771362304688e-05s
Believability | Calculation of trust value for ATC groups took 8.344650268554688e-06s
INFO | --- Analysis for cz-eh-1-atc took 1.9791183471679688s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 8.749961853027344e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Financial fulfillments took 0.17938923835754395s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Financial fulfillments took 0.020114421844482422s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Financial fulfillments took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Financial fulfillments took 0.0007014274597167969s
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.2874603271484375e-05s
INFO | --- Analysis for cz-fulfillments took 1.9979751110076904s
Availability | SPARQL endpoint availability check for Czech Business Entity identification numbers and names took 8.320808410644531e-05s
Availability | VoID file availability check for Czech Business Entity identification numbers and names took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for Czech Business Entity identification numbers and names took 0.1863846778869629s
Reputation | Calculation of the PageRank for Czech Business Entity identification numbers and names took 0.020809173583984375s
Interlinking | Calculation of Degree of Connection for Czech Business Entity identification numbers and names took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech Business Entity identification numbers and names took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Czech Business Entity identification numbers and names took 4.9591064453125e-05s
Believability | Calculation of trust value for Czech Business Entity identification numbers and names took 1.3589859008789062e-05s
INFO | --- Analysis for cz-ic took 1.9704887866973877s
Availability | SPARQL endpoint availability check for List of Czech data boxes took 6.508827209472656e-05s
Availability | VoID file availability check for List of Czech data boxes took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for List of Czech data boxes took 0.17293882369995117s
Reputation | Calculation of the PageRank for List of Czech data boxes took 0.020429134368896484s
Interlinking | Calculation of Degree of Connection for List of Czech data boxes took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for List of Czech data boxes took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for List of Czech data boxes took 3.457069396972656e-05s
Believability | Calculation of trust value for List of Czech data boxes took 1.0251998901367188e-05s
INFO | --- Analysis for cz-list-of-databoxes took 1.970062255859375s
Availability | SPARQL endpoint availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.00010037422180175781s
Availability | VoID file availability check for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.17268919944763184s
Reputation | Calculation of the PageRank for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 3.2901763916015625e-05s
Believability | Calculation of trust value for Czech statistical classification of economic activities in the European Community (CZ-NACE) took 8.58306884765625e-06s
INFO | --- Analysis for cz-nace took 1.9789118766784668s
Availability | SPARQL endpoint availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 4.410743713378906e-05s
Availability | VoID file availability check for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.17965960502624512s
Reputation | Calculation of the PageRank for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.02203822135925293s
Interlinking | Calculation of Degree of Connection for Czech National Open Data Catalog in DCAT-AP v1.2 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Czech National Open Data Catalog in DCAT-AP v1.2 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Czech National Open Data Catalog in DCAT-AP v1.2 took 3.24249267578125e-05s
Believability | Calculation of trust value for Czech National Open Data Catalog in DCAT-AP v1.2 took 9.059906005859375e-06s
INFO | --- Analysis for cz-nkod took 1.9415099620819092s
Availability | SPARQL endpoint availability check for Registry of contracts of the Czech Republic - Orders took 8.20159912109375e-05s
Availability | VoID file availability check for Registry of contracts of the Czech Republic - Orders took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Registry of contracts of the Czech Republic - Orders took 0.17479300498962402s
Reputation | Calculation of the PageRank for Registry of contracts of the Czech Republic - Orders took 0.020221471786499023s
Interlinking | Calculation of Degree of Connection for Registry of contracts of the Czech Republic - Orders took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Registry of contracts of the Czech Republic - Orders took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Registry of contracts of the Czech Republic - Orders took 3.743171691894531e-05s
Believability | Calculation of trust value for Registry of contracts of the Czech Republic - Orders took 1.2874603271484375e-05s
INFO | --- Analysis for cz-orders took 2.0195963382720947s
Availability | SPARQL endpoint availability check for Institutions of public power of the Czech Republic took 8.559226989746094e-05s
Availability | VoID file availability check for Institutions of public power of the Czech Republic took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Institutions of public power of the Czech Republic took 0.17394447326660156s
Reputation | Calculation of the PageRank for Institutions of public power of the Czech Republic took 0.020522117614746094s
Interlinking | Calculation of Degree of Connection for Institutions of public power of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Institutions of public power of the Czech Republic took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Institutions of public power of the Czech Republic took 4.506111145019531e-05s
Believability | Calculation of trust value for Institutions of public power of the Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-ovm took 1.9720187187194824s
Availability | SPARQL endpoint availability check for Agendas of institutions of public power of the Czech Republic took 8.320808410644531e-05s
Availability | VoID file availability check for Agendas of institutions of public power of the Czech Republic took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Agendas of institutions of public power of the Czech Republic took 0.1786649227142334s
Reputation | Calculation of the PageRank for Agendas of institutions of public power of the Czech Republic took 0.021046876907348633s
Interlinking | Calculation of Degree of Connection for Agendas of institutions of public power of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Agendas of institutions of public power of the Czech Republic took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Agendas of institutions of public power of the Czech Republic took 3.790855407714844e-05s
Believability | Calculation of trust value for Agendas of institutions of public power of the Czech Republic took 1.239776611328125e-05s
INFO | --- Analysis for cz-ovm-agendas took 1.9811828136444092s
Availability | SPARQL endpoint availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 9.512901306152344e-05s
Availability | VoID file availability check for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.18562674522399902s
Reputation | Calculation of the PageRank for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.020548343658447266s
Interlinking | Calculation of Degree of Connection for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Registry of territorial identification, addresses and real estate of the Czech Republic took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Registry of territorial identification, addresses and real estate of the Czech Republic took 6.842613220214844e-05s
Believability | Calculation of trust value for Registry of territorial identification, addresses and real estate of the Czech Republic took 1.2636184692382812e-05s
INFO | --- Analysis for cz-ruian took 1.995375394821167s
Availability | SPARQL endpoint availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 5.53131103515625e-05s
Availability | VoID file availability check for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Audited subjects of Supreme Audit Office of the Czech Republic took 0.17557406425476074s
Reputation | Calculation of the PageRank for Audited subjects of Supreme Audit Office of the Czech Republic took 0.022542238235473633s
Interlinking | Calculation of Degree of Connection for Audited subjects of Supreme Audit Office of the Czech Republic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Audited subjects of Supreme Audit Office of the Czech Republic took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Audited subjects of Supreme Audit Office of the Czech Republic took 7.534027099609375e-05s
Believability | Calculation of trust value for Audited subjects of Supreme Audit Office of the Czech Republic took 1.33514404296875e-05s
INFO | --- Analysis for cz-sao-audited-subjects took 1.9684062004089355s
Availability | SPARQL endpoint availability check for Inspections of the Supreme Audit Office of the Czech Republic took 8.344650268554688e-05s
Availability | VoID file availability check for Inspections of the Supreme Audit Office of the Czech Republic took 0.0005135536193847656s
Completeness | Calculation of interlinking completeness for Inspections of the Supreme Audit Office of the Czech Republic took 0.18510866165161133s
Reputation | Calculation of the PageRank for Inspections of the Supreme Audit Office of the Czech Republic took 0.020610332489013672s
Interlinking | Calculation of Degree of Connection for Inspections of the Supreme Audit Office of the Czech Republic took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Inspections of the Supreme Audit Office of the Czech Republic took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Inspections of the Supreme Audit Office of the Czech Republic took 4.1961669921875e-05s
Believability | Calculation of trust value for Inspections of the Supreme Audit Office of the Czech Republic took 1.3589859008789062e-05s
INFO | --- Analysis for cz-sao-check-actions took 1.9896810054779053s
Availability | SPARQL endpoint availability check for List of laws used in inspection reports of SAO took 8.440017700195312e-05s
Availability | VoID file availability check for List of laws used in inspection reports of SAO took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for List of laws used in inspection reports of SAO took 0.1831343173980713s
Reputation | Calculation of the PageRank for List of laws used in inspection reports of SAO took 0.021973848342895508s
Interlinking | Calculation of Degree of Connection for List of laws used in inspection reports of SAO took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for List of laws used in inspection reports of SAO took 0.0010416507720947266s
Interlinking | Calculation of Clustering coefficient for List of laws used in inspection reports of SAO took 4.1484832763671875e-05s
Believability | Calculation of trust value for List of laws used in inspection reports of SAO took 1.3828277587890625e-05s
INFO | --- Analysis for cz-sao-check-actions-law took 2.0933005809783936s
Availability | SPARQL endpoint availability check for Active ingredients of medicinal products available in Czech Republic took 9.72747802734375e-05s
Availability | VoID file availability check for Active ingredients of medicinal products available in Czech Republic took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Active ingredients of medicinal products available in Czech Republic took 0.1841118335723877s
Reputation | Calculation of the PageRank for Active ingredients of medicinal products available in Czech Republic took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Active ingredients of medicinal products available in Czech Republic took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Active ingredients of medicinal products available in Czech Republic took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Active ingredients of medicinal products available in Czech Republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for Active ingredients of medicinal products available in Czech Republic took 8.58306884765625e-06s
INFO | --- Analysis for cz-sidc-drug-ingredients took 1.9771113395690918s
Availability | SPARQL endpoint availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 8.630752563476562e-05s
Availability | VoID file availability check for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for List of prices of reimbursed medicinal products marketed in Czech republic took 0.18323922157287598s
Reputation | Calculation of the PageRank for List of prices of reimbursed medicinal products marketed in Czech republic took 0.020353317260742188s
Interlinking | Calculation of Degree of Connection for List of prices of reimbursed medicinal products marketed in Czech republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for List of prices of reimbursed medicinal products marketed in Czech republic took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for List of prices of reimbursed medicinal products marketed in Czech republic took 3.5762786865234375e-05s
Believability | Calculation of trust value for List of prices of reimbursed medicinal products marketed in Czech republic took 1.3113021850585938e-05s
INFO | --- Analysis for cz-sidc-drug-prices took 1.9778673648834229s
Availability | SPARQL endpoint availability check for Medicinal products marketed in Czech Republic took 8.368492126464844e-05s
Availability | VoID file availability check for Medicinal products marketed in Czech Republic took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Medicinal products marketed in Czech Republic took 0.17442989349365234s
Reputation | Calculation of the PageRank for Medicinal products marketed in Czech Republic took 0.020396947860717773s
Interlinking | Calculation of Degree of Connection for Medicinal products marketed in Czech Republic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Medicinal products marketed in Czech Republic took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Medicinal products marketed in Czech Republic took 3.814697265625e-05s
Believability | Calculation of trust value for Medicinal products marketed in Czech Republic took 1.0967254638671875e-05s
INFO | --- Analysis for cz-sidc-drugs took 1.987682819366455s
Availability | SPARQL endpoint availability check for Summary types of Czech institutions of public power took 8.058547973632812e-05s
Availability | VoID file availability check for Summary types of Czech institutions of public power took 0.00047326087951660156s
Completeness | Calculation of interlinking completeness for Summary types of Czech institutions of public power took 0.18197178840637207s
Reputation | Calculation of the PageRank for Summary types of Czech institutions of public power took 0.020370006561279297s
Interlinking | Calculation of Degree of Connection for Summary types of Czech institutions of public power took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Summary types of Czech institutions of public power took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Summary types of Czech institutions of public power took 3.6716461181640625e-05s
Believability | Calculation of trust value for Summary types of Czech institutions of public power took 1.2636184692382812e-05s
INFO | --- Analysis for cz-souhrnne-typy-ovm took 2.0056333541870117s
Availability | SPARQL endpoint availability check for Evaluation of VaVaI results for 2013 took 8.487701416015625e-05s
Availability | VoID file availability check for Evaluation of VaVaI results for 2013 took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Evaluation of VaVaI results for 2013 took 0.17840099334716797s
Reputation | Calculation of the PageRank for Evaluation of VaVaI results for 2013 took 0.020562171936035156s
Interlinking | Calculation of Degree of Connection for Evaluation of VaVaI results for 2013 took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Evaluation of VaVaI results for 2013 took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Evaluation of VaVaI results for 2013 took 3.528594970703125e-05s
Believability | Calculation of trust value for Evaluation of VaVaI results for 2013 took 1.71661376953125e-05s
INFO | --- Analysis for cz-vavai-evaluation-2013 took 2.0253427028656006s
Availability | SPARQL endpoint availability check for State funding providers took 8.249282836914062e-05s
Availability | VoID file availability check for State funding providers took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for State funding providers took 0.17487764358520508s
Reputation | Calculation of the PageRank for State funding providers took 0.0221097469329834s
Interlinking | Calculation of Degree of Connection for State funding providers took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for State funding providers took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for State funding providers took 4.220008850097656e-05s
Believability | Calculation of trust value for State funding providers took 1.0251998901367188e-05s
INFO | --- Analysis for cz-vavai-funding-providers took 1.975846529006958s
Availability | SPARQL endpoint availability check for Organizations active in R&D took 8.368492126464844e-05s
Availability | VoID file availability check for Organizations active in R&D took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Organizations active in R&D took 0.17916560173034668s
Reputation | Calculation of the PageRank for Organizations active in R&D took 0.020665407180786133s
Interlinking | Calculation of Degree of Connection for Organizations active in R&D took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Organizations active in R&D took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Organizations active in R&D took 4.267692565917969e-05s
Believability | Calculation of trust value for Organizations active in R&D took 1.1920928955078125e-05s
INFO | --- Analysis for cz-vavai-organizations took 1.962425947189331s
Availability | SPARQL endpoint availability check for R&D Programmes took 4.1484832763671875e-05s
Availability | VoID file availability check for R&D Programmes took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for R&D Programmes took 0.17469096183776855s
Reputation | Calculation of the PageRank for R&D Programmes took 0.02204418182373047s
Interlinking | Calculation of Degree of Connection for R&D Programmes took 1.52587890625e-05s
Interlinking | Calculation of Centrality for R&D Programmes took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for R&D Programmes took 4.267692565917969e-05s
Believability | Calculation of trust value for R&D Programmes took 1.2159347534179688e-05s
INFO | --- Analysis for cz-vavai-programmes took 2.0346689224243164s
Availability | SPARQL endpoint availability check for R&D Projects took 8.344650268554688e-05s
Availability | VoID file availability check for R&D Projects took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for R&D Projects took 0.172379732131958s
Reputation | Calculation of the PageRank for R&D Projects took 0.02102184295654297s
Interlinking | Calculation of Degree of Connection for R&D Projects took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for R&D Projects took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for R&D Projects took 4.267692565917969e-05s
Believability | Calculation of trust value for R&D Projects took 1.1682510375976562e-05s
INFO | --- Analysis for cz-vavai-projects took 1.999267578125s
Availability | SPARQL endpoint availability check for Institutional research plans took 8.273124694824219e-05s
Availability | VoID file availability check for Institutional research plans took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Institutional research plans took 0.1919851303100586s
Reputation | Calculation of the PageRank for Institutional research plans took 0.020592212677001953s
Interlinking | Calculation of Degree of Connection for Institutional research plans took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Institutional research plans took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Institutional research plans took 4.220008850097656e-05s
Believability | Calculation of trust value for Institutional research plans took 1.3589859008789062e-05s
INFO | --- Analysis for cz-vavai-research-plans took 1.9959638118743896s
Availability | SPARQL endpoint availability check for Results of R&D took 8.320808410644531e-05s
Availability | VoID file availability check for Results of R&D took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Results of R&D took 0.17424488067626953s
Reputation | Calculation of the PageRank for Results of R&D took 0.020733356475830078s
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.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Results of R&D took 4.1484832763671875e-05s
Believability | Calculation of trust value for Results of R&D took 1.3113021850585938e-05s
INFO | --- Analysis for cz-vavai-results took 1.9831719398498535s
Availability | SPARQL endpoint availability check for Tenders in R&D took 8.273124694824219e-05s
Availability | VoID file availability check for Tenders in R&D took 0.0004661083221435547s
Completeness | Calculation of interlinking completeness for Tenders in R&D took 0.1731557846069336s
Reputation | Calculation of the PageRank for Tenders in R&D took 0.02113962173461914s
Interlinking | Calculation of Degree of Connection for Tenders in R&D took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Tenders in R&D took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Tenders in R&D took 4.1484832763671875e-05s
Believability | Calculation of trust value for Tenders in R&D took 1.0967254638671875e-05s
INFO | --- Analysis for cz-vavai-tenders took 1.9774010181427002s
Availability | SPARQL endpoint availability check for Czech addresses – Adresy v České republice took 4.172325134277344e-05s
Availability | VoID file availability check for Czech addresses – Adresy v České republice took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Czech addresses – Adresy v České republice took 0.17807769775390625s
Reputation | Calculation of the PageRank for Czech addresses – Adresy v České republice took 0.020504474639892578s
Interlinking | Calculation of Degree of Connection for Czech addresses – Adresy v České republice took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Czech addresses – Adresy v České republice took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Czech addresses – Adresy v České republice took 3.4809112548828125e-05s
Believability | Calculation of trust value for Czech addresses – Adresy v České republice took 1.1920928955078125e-05s
INFO | --- Analysis for czech_addresses took 1.9769275188446045s
Availability | SPARQL endpoint availability check for Dante Latin Loanwords in LiLa took 8.368492126464844e-05s
Availability | VoID file availability check for Dante Latin Loanwords in LiLa took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Dante Latin Loanwords in LiLa took 0.17307162284851074s
Reputation | Calculation of the PageRank for Dante Latin Loanwords in LiLa took 0.020688772201538086s
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.0007531642913818359s
Interlinking | Calculation of Clustering coefficient for Dante Latin Loanwords in LiLa took 4.315376281738281e-05s
Believability | Calculation of trust value for Dante Latin Loanwords in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for DanteLatinLoanwords took 1.9602012634277344s
Availability | SPARQL endpoint availability check for data.bnf.fr - Bibliothèque nationale de France took 0.3699300289154053s
Availability | VoID file availability check for data.bnf.fr - Bibliothèque nationale de France took 0.0004744529724121094s
Extra | Recovery of all triples for data.bnf.fr - Bibliothèque nationale de France took 140.95947074890137s
Performance | Total latancy measurement for data.bnf.fr - Bibliothèque nationale de France took 1.0603172779083252s
Amount of data | Number of triples check for data.bnf.fr - Bibliothèque nationale de France took 11.940150737762451s
Interoperability | New terms check for data.bnf.fr - Bibliothèque nationale de France took 4.369205474853516s
Versatility | Languages check for data.bnf.fr - Bibliothèque nationale de France took 120.28391981124878s
Interpretability | Number of blank nodes check for data.bnf.fr - Bibliothèque nationale de France took 0.23941898345947266s
Security | Check HTTPS for data.bnf.fr - Bibliothèque nationale de France took 0.12660741806030273s
Interpretability | RDF structures check for data.bnf.fr - Bibliothèque nationale de France took 0.3041348457336426s
Versatility | Serialization formats check for data.bnf.fr - Bibliothèque nationale de France took 0.25081706047058105s
Availability | RDF dump link check for data.bnf.fr - Bibliothèque nationale de France took 0.2352619171142578s
License | MR license check for data.bnf.fr - Bibliothèque nationale de France took 0.23974967002868652s
License | HR license check for data.bnf.fr - Bibliothèque nationale de France took 120.24787974357605s
Amount of data | Number of property check for data.bnf.fr - Bibliothèque nationale de France took 0.24010920524597168s
Understandability | Number of label check for data.bnf.fr - Bibliothèque nationale de France took 2.4576103687286377s
Understandability | URI regex check for data.bnf.fr - Bibliothèque nationale de France took 0.4727661609649658s
Understandability | Vocabs check for data.bnf.fr - Bibliothèque nationale de France took 0.25314831733703613s
Verifiability | Authors check for data.bnf.fr - Bibliothèque nationale de France took 0.23870325088500977s
Verifiability | Publishers check for data.bnf.fr - Bibliothèque nationale de France took 0.23954463005065918s
Performance | Throughput check for data.bnf.fr - Bibliothèque nationale de France took 10.501982688903809s
Amount of data | Check the number of entities for data.bnf.fr - Bibliothèque nationale de France took 7.343292236328125e-05s
Verifiability | Contribs. check for data.bnf.fr - Bibliothèque nationale de France took 0.23223090171813965s
Interlinking | sameAs chians check for data.bnf.fr - Bibliothèque nationale de France took 0.743577241897583s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 1.7509663105010986s
Interlinking | skos check for data.bnf.fr - Bibliothèque nationale de France took 0.7324800491333008s
Timeliness | dataset update frequency check for data.bnf.fr - Bibliothèque nationale de France took 0.24487686157226562s
Currency | Creation date check for data.bnf.fr - Bibliothèque nationale de France took 2.3875250816345215s
Currency | Modification date check for data.bnf.fr - Bibliothèque nationale de France took 3.758209466934204s
Rep.Conc. | URIs length for data.bnf.fr - Bibliothèque nationale de France took 86.90939021110535s
Interoperability | New vocabularies check for data.bnf.fr - Bibliothèque nationale de France took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for data.bnf.fr - Bibliothèque nationale de France took 0.23444175720214844s
Accuracy | Check Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.3409280776977539s
Accuracy | Check Inverse Functional Property for data.bnf.fr - Bibliothèque nationale de France took 0.42989635467529297s
Accuracy | Check Empty annotation labels for data.bnf.fr - Bibliothèque nationale de France took 48.48107981681824s
Accuracy | Check White space in annotation for data.bnf.fr - Bibliothèque nationale de France took 3.240872859954834s
Accuracy | Check Datatype consistency for data.bnf.fr - Bibliothèque nationale de France took 2.5971269607543945s
Consistency | Disjoint class check for data.bnf.fr - Bibliothèque nationale de France took 0.29439592361450195s
Consistency | Check Misplaced properties for data.bnf.fr - Bibliothèque nationale de France took 20.194201231002808s
Consistency | Misplaced classes for data.bnf.fr - Bibliothèque nationale de France took 8.797610998153687s
Consistency | Check Ontology hijacking for data.bnf.fr - Bibliothèque nationale de France took 50.67060351371765s
Consistency | Check Invalid usage of undefined classes for data.bnf.fr - Bibliothèque nationale de France took 1.4297425746917725s
Consistency | Check Invalid usage of undefined properties for data.bnf.fr - Bibliothèque nationale de France took 23.309488773345947s
Conciseness | Check Extensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 2.838883876800537s
Conciseness | Check Intensional conciseness for data.bnf.fr - Bibliothèque nationale de France took 0.2415306568145752s
Security | Sign check for data.bnf.fr - Bibliothèque nationale de France took 0.23452043533325195s
Availability | Check URIs Dereferenciability for data.bnf.fr - Bibliothèque nationale de France took 12.078275918960571s
Completeness | Calculation of interlinking completeness for data.bnf.fr - Bibliothèque nationale de France took 0.2944004535675049s
Reputation | Calculation of the PageRank for data.bnf.fr - Bibliothèque nationale de France took 0.02122354507446289s
Interlinking | Calculation of Degree of Connection for data.bnf.fr - Bibliothèque nationale de France took 1.52587890625e-05s
Interlinking | Calculation of Centrality for data.bnf.fr - Bibliothèque nationale de France took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for data.bnf.fr - Bibliothèque nationale de France took 0.00013947486877441406s
Interoperability | Check the re-using of existing vocabs for data.bnf.fr - Bibliothèque nationale de France took 2.384185791015625e-06s
Believability | Calculation of trust value for data.bnf.fr - Bibliothèque nationale de France took 1.1444091796875e-05s
INFO | --- Analysis for data-bnf-fr took 853.2943124771118s
Availability | SPARQL endpoint availability check for Open Data from the Italian National Research Council took 8.368492126464844e-05s
Availability | VoID file availability check for Open Data from the Italian National Research Council took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for Open Data from the Italian National Research Council took 0.18329930305480957s
Reputation | Calculation of the PageRank for Open Data from the Italian National Research Council took 0.022836923599243164s
Interlinking | Calculation of Degree of Connection for Open Data from the Italian National Research Council took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Data from the Italian National Research Council took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Open Data from the Italian National Research Council took 6.532669067382812e-05s
Believability | Calculation of trust value for Open Data from the Italian National Research Council took 1.1444091796875e-05s
INFO | --- Analysis for data-cnr-it took 2.040205717086792s
Availability | SPARQL endpoint availability check for Data.gov took 8.249282836914062e-05s
Availability | VoID file availability check for Data.gov took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Data.gov took 0.18385910987854004s
Reputation | Calculation of the PageRank for Data.gov took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Data.gov took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Data.gov took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Data.gov took 3.457069396972656e-05s
Believability | Calculation of trust value for Data.gov took 7.3909759521484375e-06s
INFO | --- Analysis for data-gov took 2.036166191101074s
Availability | SPARQL endpoint availability check for DataGovIE - Irish Government Data took 8.320808410644531e-05s
Availability | VoID file availability check for DataGovIE - Irish Government Data took 0.0005035400390625s
Completeness | Calculation of interlinking completeness for DataGovIE - Irish Government Data took 0.17892003059387207s
Reputation | Calculation of the PageRank for DataGovIE - Irish Government Data took 0.020728111267089844s
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.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for DataGovIE - Irish Government Data took 6.628036499023438e-05s
Believability | Calculation of trust value for DataGovIE - Irish Government Data took 1.3113021850585938e-05s
INFO | --- Analysis for data-gov-ie took 2.0343997478485107s
Availability | SPARQL endpoint availability check for data.gov.uk Time Intervals took 5.435943603515625e-05s
Availability | VoID file availability check for data.gov.uk Time Intervals took 0.00030231475830078125s
Completeness | Calculation of interlinking completeness for data.gov.uk Time Intervals took 0.19111371040344238s
Reputation | Calculation of the PageRank for data.gov.uk Time Intervals took 0.022609710693359375s
Interlinking | Calculation of Degree of Connection for data.gov.uk Time Intervals took 1.621246337890625e-05s
Interlinking | Calculation of Centrality for data.gov.uk Time Intervals took 0.0011010169982910156s
Interlinking | Calculation of Clustering coefficient for data.gov.uk Time Intervals took 8.845329284667969e-05s
Believability | Calculation of trust value for data.gov.uk Time Intervals took 1.3113021850585938e-05s
INFO | --- Analysis for data-gov-uk-time-intervals took 2.018385171890259s
Availability | SPARQL endpoint availability check for data-hnm-hu - Hungarian National Museum Datasets took 22.052677392959595s
Availability | VoID file availability check for data-hnm-hu - Hungarian National Museum Datasets took 0.0005428791046142578s
Completeness | Calculation of interlinking completeness for data-hnm-hu - Hungarian National Museum Datasets took 0.18448233604431152s
Reputation | Calculation of the PageRank for data-hnm-hu - Hungarian National Museum Datasets took 0.020773649215698242s
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.0007290840148925781s
Interlinking | Calculation of Clustering coefficient for data-hnm-hu - Hungarian National Museum Datasets took 7.319450378417969e-05s
Believability | Calculation of trust value for data-hnm-hu - Hungarian National Museum Datasets took 5.9604644775390625e-06s
INFO | --- Analysis for data-hnm-hu took 54.21531939506531s
Availability | SPARQL endpoint availability check for Climb Dataincubator took 0.19103503227233887s
Availability | VoID file availability check for Climb Dataincubator took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Climb Dataincubator took 0.17905640602111816s
Reputation | Calculation of the PageRank for Climb Dataincubator took 0.02014446258544922s
Interlinking | Calculation of Degree of Connection for Climb Dataincubator took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Climb Dataincubator took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for Climb Dataincubator took 6.818771362304688e-05s
Believability | Calculation of trust value for Climb Dataincubator took 1.1682510375976562e-05s
INFO | --- Analysis for data-incubator-climb took 2.2100303173065186s
Availability | SPARQL endpoint availability check for Discogs in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Discogs in RDF took 0.0005462169647216797s
Completeness | Calculation of interlinking completeness for Discogs in RDF took 0.1835627555847168s
Reputation | Calculation of the PageRank for Discogs in RDF took 0.02148890495300293s
Interlinking | Calculation of Degree of Connection for Discogs in RDF took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Discogs in RDF took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Discogs in RDF took 0.00012636184692382812s
Believability | Calculation of trust value for Discogs in RDF took 1.0728836059570312e-05s
INFO | --- Analysis for data-incubator-discogs took 3.206458568572998s
Availability | SPARQL endpoint availability check for Metoffice Weather Forecasts took 8.249282836914062e-05s
Availability | VoID file availability check for Metoffice Weather Forecasts took 0.0004954338073730469s
Completeness | Calculation of interlinking completeness for Metoffice Weather Forecasts took 0.18671941757202148s
Reputation | Calculation of the PageRank for Metoffice Weather Forecasts took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for Metoffice Weather Forecasts took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Metoffice Weather Forecasts took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Metoffice Weather Forecasts took 5.173683166503906e-05s
Believability | Calculation of trust value for Metoffice Weather Forecasts took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-metoffice took 2.04976487159729s
Availability | SPARQL endpoint availability check for Moseley Folk Festival Data took 0.06359624862670898s
Availability | VoID file availability check for Moseley Folk Festival Data took 0.0006606578826904297s
Completeness | Calculation of interlinking completeness for Moseley Folk Festival Data took 0.18995451927185059s
Reputation | Calculation of the PageRank for Moseley Folk Festival Data took 0.021964550018310547s
Interlinking | Calculation of Degree of Connection for Moseley Folk Festival Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Moseley Folk Festival Data took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Moseley Folk Festival Data took 8.368492126464844e-05s
Believability | Calculation of trust value for Moseley Folk Festival Data took 6.9141387939453125e-06s
INFO | --- Analysis for data-incubator-moseley took 4.062586307525635s
Availability | SPARQL endpoint availability check for Data Incubator: MusicBrainz took 0.049727678298950195s
Availability | VoID file availability check for Data Incubator: MusicBrainz took 0.0002684593200683594s
Completeness | Calculation of interlinking completeness for Data Incubator: MusicBrainz took 0.17675995826721191s
Reputation | Calculation of the PageRank for Data Incubator: MusicBrainz took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for Data Incubator: MusicBrainz took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Data Incubator: MusicBrainz took 0.0008425712585449219s
Interlinking | Calculation of Clustering coefficient for Data Incubator: MusicBrainz took 9.560585021972656e-05s
Believability | Calculation of trust value for Data Incubator: MusicBrainz took 1.2159347534179688e-05s
INFO | --- Analysis for data-incubator-musicbrainz took 2.026792287826538s
Availability | SPARQL endpoint availability check for NASA Space Flight & Astronaut data in RDF took 3.981590270996094e-05s
Availability | VoID file availability check for NASA Space Flight & Astronaut data in RDF took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for NASA Space Flight & Astronaut data in RDF took 0.19617986679077148s
Reputation | Calculation of the PageRank for NASA Space Flight & Astronaut data in RDF took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for NASA Space Flight & Astronaut data in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NASA Space Flight & Astronaut data in RDF took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for NASA Space Flight & Astronaut data in RDF took 7.987022399902344e-05s
Believability | Calculation of trust value for NASA Space Flight & Astronaut data in RDF took 1.1205673217773438e-05s
INFO | --- Analysis for data-incubator-nasa took 2.0157716274261475s
Availability | SPARQL endpoint availability check for Airport data from Our Airports published as RDF took 8.606910705566406e-05s
Availability | VoID file availability check for Airport data from Our Airports published as RDF took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for Airport data from Our Airports published as RDF took 0.19351553916931152s
Reputation | Calculation of the PageRank for Airport data from Our Airports published as RDF took 0.021168947219848633s
Interlinking | Calculation of Degree of Connection for Airport data from Our Airports published as RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Airport data from Our Airports published as RDF took 0.0006852149963378906s
Interlinking | Calculation of Clustering coefficient for Airport data from Our Airports published as RDF took 6.890296936035156e-05s
Believability | Calculation of trust value for Airport data from Our Airports published as RDF took 1.1444091796875e-05s
INFO | --- Analysis for data-incubator-our-airports took 2.0405046939849854s
Availability | SPARQL endpoint availability check for Pokedex data in RDF took 8.344650268554688e-05s
Availability | VoID file availability check for Pokedex data in RDF took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Pokedex data in RDF took 0.18283963203430176s
Reputation | Calculation of the PageRank for Pokedex data in RDF took 0.020070314407348633s
Interlinking | Calculation of Degree of Connection for Pokedex data in RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pokedex data in RDF took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Pokedex data in RDF took 8.797645568847656e-05s
Believability | Calculation of trust value for Pokedex data in RDF took 1.1444091796875e-05s
INFO | --- Analysis for data-incubator-pokedex took 1.9841647148132324s
Availability | SPARQL endpoint availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00010848045349121094s
Availability | VoID file availability check for Scottish Mountaineering Council Journals Issues 1-36 took 0.00048828125s
Completeness | Calculation of interlinking completeness for Scottish Mountaineering Council Journals Issues 1-36 took 0.18216562271118164s
Reputation | Calculation of the PageRank for Scottish Mountaineering Council Journals Issues 1-36 took 0.020468473434448242s
Interlinking | Calculation of Degree of Connection for Scottish Mountaineering Council Journals Issues 1-36 took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for Scottish Mountaineering Council Journals Issues 1-36 took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for Scottish Mountaineering Council Journals Issues 1-36 took 0.00011730194091796875s
Believability | Calculation of trust value for Scottish Mountaineering Council Journals Issues 1-36 took 1.1920928955078125e-05s
INFO | --- Analysis for data-incubator-smcjournals took 1.9991014003753662s
Availability | SPARQL endpoint availability check for data.open.ac.uk, Linked Data from the Open University took 8.106231689453125e-05s
Availability | VoID file availability check for data.open.ac.uk, Linked Data from the Open University took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for data.open.ac.uk, Linked Data from the Open University took 0.17482757568359375s
Reputation | Calculation of the PageRank for data.open.ac.uk, Linked Data from the Open University took 0.020170927047729492s
Interlinking | Calculation of Degree of Connection for data.open.ac.uk, Linked Data from the Open University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for data.open.ac.uk, Linked Data from the Open University took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for data.open.ac.uk, Linked Data from the Open University took 6.198883056640625e-05s
Believability | Calculation of trust value for data.open.ac.uk, Linked Data from the Open University took 1.1920928955078125e-05s
INFO | --- Analysis for data-open-ac-uk took 1.9775471687316895s
Availability | SPARQL endpoint availability check for Persée in RDF took 4.00543212890625e-05s
Availability | VoID file availability check for Persée in RDF took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Persée in RDF took 0.17879223823547363s
Reputation | Calculation of the PageRank for Persée in RDF took 0.020731687545776367s
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.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Persée in RDF took 0.00011420249938964844s
Believability | Calculation of trust value for Persée in RDF took 1.1444091796875e-05s
INFO | --- Analysis for data-persee-fr took 1.9783425331115723s
Availability | SPARQL endpoint availability check for data.southampton.ac.uk with SPARQL endpoint took 8.153915405273438e-05s
Availability | VoID file availability check for data.southampton.ac.uk with SPARQL endpoint took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for data.southampton.ac.uk with SPARQL endpoint took 0.1810321807861328s
Reputation | Calculation of the PageRank for data.southampton.ac.uk with SPARQL endpoint took 0.020322799682617188s
Interlinking | Calculation of Degree of Connection for data.southampton.ac.uk with SPARQL endpoint took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for data.southampton.ac.uk with SPARQL endpoint took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for data.southampton.ac.uk with SPARQL endpoint took 3.0517578125e-05s
Believability | Calculation of trust value for data.southampton.ac.uk with SPARQL endpoint took 8.58306884765625e-06s
INFO | --- Analysis for data-southampton-ac-uk took 2.1096057891845703s
Availability | SPARQL endpoint availability check for data-szepmuveszeti-hu took 1.1128771305084229s
Availability | VoID file availability check for data-szepmuveszeti-hu took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for data-szepmuveszeti-hu took 0.18204975128173828s
Reputation | Calculation of the PageRank for data-szepmuveszeti-hu took 0.020647525787353516s
Interlinking | Calculation of Degree of Connection for data-szepmuveszeti-hu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for data-szepmuveszeti-hu took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for data-szepmuveszeti-hu took 0.00011014938354492188s
Believability | Calculation of trust value for data-szepmuveszeti-hu took 1.0967254638671875e-05s
INFO | --- Analysis for data-szepmuveszeti-hu took 3.722419500350952s
Availability | SPARQL endpoint availability check for Open Data Web took 8.225440979003906e-05s
Availability | VoID file availability check for Open Data Web took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Open Data Web took 0.1815180778503418s
Reputation | Calculation of the PageRank for Open Data Web took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Open Data Web took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Data Web took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Open Data Web took 3.075599670410156e-05s
Believability | Calculation of trust value for Open Data Web took 6.198883056640625e-06s
INFO | --- Analysis for data.odw.tw took 1.9802367687225342s
Availability | SPARQL endpoint availability check for DataFAQs took 8.106231689453125e-05s
Availability | VoID file availability check for DataFAQs took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for DataFAQs took 0.16816163063049316s
Reputation | Calculation of the PageRank for DataFAQs took 0.02036285400390625s
Interlinking | Calculation of Degree of Connection for DataFAQs took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DataFAQs took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for DataFAQs took 3.0517578125e-05s
Believability | Calculation of trust value for DataFAQs took 5.9604644775390625e-06s
INFO | --- Analysis for datafaqs took 1.9400577545166016s
Availability | SPARQL endpoint availability check for datahub took 8.678436279296875e-05s
Availability | VoID file availability check for datahub took 0.0005419254302978516s
Completeness | Calculation of interlinking completeness for datahub took 0.17699360847473145s
Reputation | Calculation of the PageRank for datahub took 0.020316362380981445s
Interlinking | Calculation of Degree of Connection for datahub took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for datahub took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for datahub took 4.649162292480469e-05s
Believability | Calculation of trust value for datahub took 1.1682510375976562e-05s
INFO | --- Analysis for datahub took 1.9741251468658447s
Availability | SPARQL endpoint availability check for Open Datasets in South Korea took 8.225440979003906e-05s
Availability | VoID file availability check for Open Datasets in South Korea took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Open Datasets in South Korea took 0.1804797649383545s
Reputation | Calculation of the PageRank for Open Datasets in South Korea took 0.020989656448364258s
Interlinking | Calculation of Degree of Connection for Open Datasets in South Korea took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Datasets in South Korea took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Open Datasets in South Korea took 3.0517578125e-05s
Believability | Calculation of trust value for Open Datasets in South Korea took 1.0967254638671875e-05s
INFO | --- Analysis for datahub-kr-datamap took 2.0019373893737793s
Availability | SPARQL endpoint availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 8.559226989746094e-05s
Availability | VoID file availability check for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.18576598167419434s
Reputation | Calculation of the PageRank for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 6.699562072753906e-05s
Believability | Calculation of trust value for DATATURCYL - LOD for tourists in Castilla y León (Spain) took 1.1920928955078125e-05s
INFO | --- Analysis for dataturcyl-lod-for-tourists-in-castilla-y-leon-spain took 2.0623316764831543s
Availability | SPARQL endpoint availability check for datos-artium-org took 21.163506507873535s
Availability | VoID file availability check for datos-artium-org took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for datos-artium-org took 0.2063455581665039s
Reputation | Calculation of the PageRank for datos-artium-org took 0.02234506607055664s
Interlinking | Calculation of Degree of Connection for datos-artium-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for datos-artium-org took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for datos-artium-org took 0.00011467933654785156s
Believability | Calculation of trust value for datos-artium-org took 1.0013580322265625e-05s
INFO | --- Analysis for datos-artium-org took 53.32374048233032s
Availability | SPARQL endpoint availability check for Datos.bcn.cl took 3.814697265625e-05s
Availability | VoID file availability check for Datos.bcn.cl took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for Datos.bcn.cl took 0.17296957969665527s
Reputation | Calculation of the PageRank for Datos.bcn.cl took 0.020363569259643555s
Interlinking | Calculation of Degree of Connection for Datos.bcn.cl took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Datos.bcn.cl took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for Datos.bcn.cl took 7.009506225585938e-05s
Believability | Calculation of trust value for Datos.bcn.cl took 1.0967254638671875e-05s
INFO | --- Analysis for datos-bcn-cl took 1.9852981567382812s
Availability | SPARQL endpoint availability check for datos.bne.es took 0.3152484893798828s
Availability | VoID file availability check for datos.bne.es took 0.0004703998565673828s
Extra | Recovery of all triples for datos.bne.es took 136.7593080997467s
Performance | Total latancy measurement for datos.bne.es took 5.201116561889648s
Amount of data | Number of triples check for datos.bne.es took 0.8827390670776367s
Interoperability | New terms check for datos.bne.es took 4.204777240753174s
Versatility | Languages check for datos.bne.es took 63.928542613983154s
Interpretability | Number of blank nodes check for datos.bne.es took 2.146834373474121s
Security | Check HTTPS for datos.bne.es took 4.078228950500488s
Interpretability | RDF structures check for datos.bne.es took 2.3257179260253906s
Versatility | Serialization formats check for datos.bne.es took 0.6190469264984131s
Availability | RDF dump link check for datos.bne.es took 2.2286922931671143s
License | MR license check for datos.bne.es took 0.8933243751525879s
License | HR license check for datos.bne.es took 62.317218542099s
Amount of data | Number of property check for datos.bne.es took 0.32212018966674805s
Understandability | Number of label check for datos.bne.es took 1.0880601406097412s
Understandability | URI regex check for datos.bne.es took 2.66825532913208s
Understandability | Vocabs check for datos.bne.es took 0.38336968421936035s
Verifiability | Authors check for datos.bne.es took 0.4520993232727051s
Verifiability | Publishers check for datos.bne.es took 0.40761351585388184s
Performance | Throughput check for datos.bne.es took 21.473750352859497s
Amount of data | Check the number of entities for datos.bne.es took 6.794929504394531e-05s
Verifiability | Contribs. check for datos.bne.es took 0.39463114738464355s
Interlinking | sameAs chians check for datos.bne.es took 0.5251190662384033s
Interlinking | skos check for datos.bne.es took 2.4544692039489746s
Interlinking | skos check for datos.bne.es took 2.0668880939483643s
Timeliness | dataset update frequency check for datos.bne.es took 2.3088653087615967s
Currency | Creation date check for datos.bne.es took 2.5717897415161133s
Currency | Modification date check for datos.bne.es took 0.6301939487457275s
Rep.Conc. | URIs length for datos.bne.es took 55.41670513153076s
Interoperability | New vocabularies check for datos.bne.es took 9.5367431640625e-06s
Consistency | Deprecated classes/propertiers check for datos.bne.es took 0.3142554759979248s
Accuracy | Check Functional Property for datos.bne.es took 0.31502389907836914s
Accuracy | Check Inverse Functional Property for datos.bne.es took 0.3156263828277588s
Accuracy | Check Empty annotation labels for datos.bne.es took 44.34008836746216s
Accuracy | Check White space in annotation for datos.bne.es took 1.5999670028686523s
Accuracy | Check Datatype consistency for datos.bne.es took 1.2558841705322266s
Consistency | Disjoint class check for datos.bne.es took 0.3610191345214844s
Consistency | Check Misplaced properties for datos.bne.es took 10.46342134475708s
Consistency | Misplaced classes for datos.bne.es took 4.373686075210571s
Consistency | Check Ontology hijacking for datos.bne.es took 45.572678089141846s
Consistency | Check Invalid usage of undefined classes for datos.bne.es took 1.3792774677276611s
Consistency | Check Invalid usage of undefined properties for datos.bne.es took 9.50234079360962s
Conciseness | Check Extensional conciseness for datos.bne.es took 1.3735425472259521s
Conciseness | Check Intensional conciseness for datos.bne.es took 0.31470346450805664s
Security | Sign check for datos.bne.es took 3.0084826946258545s
Availability | Check URIs Dereferenciability for datos.bne.es took 14.829644680023193s
Completeness | Calculation of interlinking completeness for datos.bne.es took 0.34018611907958984s
Reputation | Calculation of the PageRank for datos.bne.es took 0.021181821823120117s
Interlinking | Calculation of Degree of Connection for datos.bne.es took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for datos.bne.es took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for datos.bne.es took 0.00011777877807617188s
Interoperability | Check the re-using of existing vocabs for datos.bne.es took 2.1457672119140625e-06s
Believability | Calculation of trust value for datos.bne.es took 6.198883056640625e-06s
INFO | --- Analysis for datos-bne-es took 648.9398355484009s
Availability | SPARQL endpoint availability check for dbacademic took 4.00543212890625e-05s
Availability | VoID file availability check for dbacademic took 0.00025582313537597656s
Completeness | Calculation of interlinking completeness for dbacademic took 0.17378497123718262s
Reputation | Calculation of the PageRank for dbacademic took 0.020161151885986328s
Interlinking | Calculation of Degree of Connection for dbacademic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for dbacademic took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for dbacademic took 2.765655517578125e-05s
Believability | Calculation of trust value for dbacademic took 1.2874603271484375e-05s
INFO | --- Analysis for dbacademic took 1.9600846767425537s
Availability | SPARQL endpoint availability check for DBkWik took 8.392333984375e-05s
Availability | VoID file availability check for DBkWik took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for DBkWik took 0.1841285228729248s
Reputation | Calculation of the PageRank for DBkWik took 0.021343231201171875s
Interlinking | Calculation of Degree of Connection for DBkWik took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBkWik took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for DBkWik took 6.651878356933594e-05s
Believability | Calculation of trust value for DBkWik took 1.1444091796875e-05s
INFO | --- Analysis for dbkwik took 1.978337287902832s
Availability | SPARQL endpoint availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010514259338378906s
Availability | VoID file availability check for DBLP Research Groups (University of Deusto-GNOSS) took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for DBLP Research Groups (University of Deusto-GNOSS) took 0.18781256675720215s
Reputation | Calculation of the PageRank for DBLP Research Groups (University of Deusto-GNOSS) took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for DBLP Research Groups (University of Deusto-GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBLP Research Groups (University of Deusto-GNOSS) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for DBLP Research Groups (University of Deusto-GNOSS) took 0.00010323524475097656s
Believability | Calculation of trust value for DBLP Research Groups (University of Deusto-GNOSS) took 7.62939453125e-06s
INFO | --- Analysis for dblp-deusto-gnoss took 1.9919407367706299s
Availability | SPARQL endpoint availability check for dblp Knowledge Graph took 8.058547973632812e-05s
Availability | VoID file availability check for dblp Knowledge Graph took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for dblp Knowledge Graph took 0.18243145942687988s
Reputation | Calculation of the PageRank for dblp Knowledge Graph took 0.021254539489746094s
Interlinking | Calculation of Degree of Connection for dblp Knowledge Graph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for dblp Knowledge Graph took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for dblp Knowledge Graph took 1.1682510375976562e-05s
Believability | Calculation of trust value for dblp Knowledge Graph took 1.430511474609375e-05s
INFO | --- Analysis for dblp-kg took 1.9893770217895508s
Availability | SPARQL endpoint availability check for dbnary took 4.315376281738281e-05s
Availability | VoID file availability check for dbnary took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for dbnary took 0.1724989414215088s
Reputation | Calculation of the PageRank for dbnary took 0.020279407501220703s
Interlinking | Calculation of Degree of Connection for dbnary took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for dbnary took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for dbnary took 4.76837158203125e-05s
Believability | Calculation of trust value for dbnary took 1.3113021850585938e-05s
INFO | --- Analysis for dbnary took 1.993307113647461s
Availability | SPARQL endpoint availability check for DBpedia took 9.679794311523438e-05s
Availability | VoID file availability check for DBpedia took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for DBpedia took 0.17623209953308105s
Reputation | Calculation of the PageRank for DBpedia took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for DBpedia took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for DBpedia took 0.0008969306945800781s
Believability | Calculation of trust value for DBpedia took 8.344650268554688e-06s
INFO | --- Analysis for dbpedia took 1.9408831596374512s
Availability | SPARQL endpoint availability check for DBpedia abstract corpus took 0.00010776519775390625s
Availability | VoID file availability check for DBpedia abstract corpus took 0.0004897117614746094s
Completeness | Calculation of interlinking completeness for DBpedia abstract corpus took 0.19246888160705566s
Reputation | Calculation of the PageRank for DBpedia abstract corpus took 0.020213603973388672s
Interlinking | Calculation of Degree of Connection for DBpedia abstract corpus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia abstract corpus took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for DBpedia abstract corpus took 6.246566772460938e-05s
Believability | Calculation of trust value for DBpedia abstract corpus took 1.2636184692382812e-05s
INFO | --- Analysis for dbpedia-abstract-corpus took 2.0606226921081543s
Availability | SPARQL endpoint availability check for DBpedia Commons took 4.506111145019531e-05s
Availability | VoID file availability check for DBpedia Commons took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for DBpedia Commons took 0.18233895301818848s
Reputation | Calculation of the PageRank for DBpedia Commons took 0.022425413131713867s
Interlinking | Calculation of Degree of Connection for DBpedia Commons took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DBpedia Commons took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for DBpedia Commons took 6.127357482910156e-05s
Believability | Calculation of trust value for DBpedia Commons took 1.2874603271484375e-05s
INFO | --- Analysis for dbpedia-commons took 1.993459939956665s
Availability | SPARQL endpoint availability check for DBpedia in German took 8.130073547363281e-05s
Availability | VoID file availability check for DBpedia in German took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for DBpedia in German took 0.17770862579345703s
Reputation | Calculation of the PageRank for DBpedia in German took 0.020306110382080078s
Interlinking | Calculation of Degree of Connection for DBpedia in German took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia in German took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for DBpedia in German took 6.580352783203125e-05s
Believability | Calculation of trust value for DBpedia in German took 5.4836273193359375e-06s
INFO | --- Analysis for dbpedia-de took 1.982558012008667s
Availability | SPARQL endpoint availability check for DBpedia in Greek took 8.106231689453125e-05s
Availability | VoID file availability check for DBpedia in Greek took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for DBpedia in Greek took 0.1861863136291504s
Reputation | Calculation of the PageRank for DBpedia in Greek took 0.020258426666259766s
Interlinking | Calculation of Degree of Connection for DBpedia in Greek took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Greek took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for DBpedia in Greek took 0.00018358230590820312s
Believability | Calculation of trust value for DBpedia in Greek took 1.0967254638671875e-05s
INFO | --- Analysis for dbpedia-el took 1.9739782810211182s
Availability | SPARQL endpoint availability check for DBpedia in Spanish took 8.392333984375e-05s
Availability | VoID file availability check for DBpedia in Spanish took 0.00020170211791992188s
Completeness | Calculation of interlinking completeness for DBpedia in Spanish took 0.17650771141052246s
Reputation | Calculation of the PageRank for DBpedia in Spanish took 0.02021336555480957s
Interlinking | Calculation of Degree of Connection for DBpedia in Spanish took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Spanish took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for DBpedia in Spanish took 9.72747802734375e-05s
Believability | Calculation of trust value for DBpedia in Spanish took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-es took 1.966728687286377s
Availability | SPARQL endpoint availability check for DBpedia in Basque took 8.082389831542969e-05s
Availability | VoID file availability check for DBpedia in Basque took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for DBpedia in Basque took 0.1740739345550537s
Reputation | Calculation of the PageRank for DBpedia in Basque took 0.020262479782104492s
Interlinking | Calculation of Degree of Connection for DBpedia in Basque took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DBpedia in Basque took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for DBpedia in Basque took 2.956390380859375e-05s
Believability | Calculation of trust value for DBpedia in Basque took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-eu took 1.998774766921997s
Availability | SPARQL endpoint availability check for DBpedia in French took 9.250640869140625e-05s
Availability | VoID file availability check for DBpedia in French took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for DBpedia in French took 0.18753504753112793s
Reputation | Calculation of the PageRank for DBpedia in French took 0.02041482925415039s
Interlinking | Calculation of Degree of Connection for DBpedia in French took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia in French took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for DBpedia in French took 8.416175842285156e-05s
Believability | Calculation of trust value for DBpedia in French took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-fr took 1.9950761795043945s
Availability | SPARQL endpoint availability check for DBpedia in Japanese took 8.106231689453125e-05s
Availability | VoID file availability check for DBpedia in Japanese took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for DBpedia in Japanese took 0.17254233360290527s
Reputation | Calculation of the PageRank for DBpedia in Japanese took 0.021792888641357422s
Interlinking | Calculation of Degree of Connection for DBpedia in Japanese took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia in Japanese took 0.0008068084716796875s
Interlinking | Calculation of Clustering coefficient for DBpedia in Japanese took 9.584426879882812e-05s
Believability | Calculation of trust value for DBpedia in Japanese took 1.3589859008789062e-05s
INFO | --- Analysis for dbpedia-ja took 1.98024582862854s
Availability | SPARQL endpoint availability check for dbpedia lite took 6.175041198730469e-05s
Availability | VoID file availability check for dbpedia lite took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for dbpedia lite took 0.17310047149658203s
Reputation | Calculation of the PageRank for dbpedia lite took 0.021439552307128906s
Interlinking | Calculation of Degree of Connection for dbpedia lite took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for dbpedia lite took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for dbpedia lite took 9.942054748535156e-05s
Believability | Calculation of trust value for dbpedia lite took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-lite took 2.0129268169403076s
Availability | SPARQL endpoint availability check for DBpedia-Live took 7.987022399902344e-05s
Availability | VoID file availability check for DBpedia-Live took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for DBpedia-Live took 0.17303180694580078s
Reputation | Calculation of the PageRank for DBpedia-Live took 0.02311229705810547s
Interlinking | Calculation of Degree of Connection for DBpedia-Live took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DBpedia-Live took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for DBpedia-Live took 3.1948089599609375e-05s
Believability | Calculation of trust value for DBpedia-Live took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-live took 2.010122537612915s
Availability | SPARQL endpoint availability check for DBpedia in Dutch took 8.0108642578125e-05s
Availability | VoID file availability check for DBpedia in Dutch took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for DBpedia in Dutch took 0.17275571823120117s
Reputation | Calculation of the PageRank for DBpedia in Dutch took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for DBpedia in Dutch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia in Dutch took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DBpedia in Dutch took 0.00016188621520996094s
Believability | Calculation of trust value for DBpedia in Dutch took 1.0013580322265625e-05s
INFO | --- Analysis for dbpedia-nl took 1.9633021354675293s
Availability | SPARQL endpoint availability check for DBpedia in Portuguese took 8.368492126464844e-05s
Availability | VoID file availability check for DBpedia in Portuguese took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for DBpedia in Portuguese took 0.18436384201049805s
Reputation | Calculation of the PageRank for DBpedia in Portuguese took 0.021924734115600586s
Interlinking | Calculation of Degree of Connection for DBpedia in Portuguese took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBpedia in Portuguese took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for DBpedia in Portuguese took 7.724761962890625e-05s
Believability | Calculation of trust value for DBpedia in Portuguese took 6.198883056640625e-06s
INFO | --- Analysis for dbpedia-pt took 1.9566082954406738s
Availability | SPARQL endpoint availability check for DBpedia Spotlight took 5.412101745605469e-05s
Availability | VoID file availability check for DBpedia Spotlight took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight took 0.17272448539733887s
Reputation | Calculation of the PageRank for DBpedia Spotlight took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight took 3.218650817871094e-05s
Believability | Calculation of trust value for DBpedia Spotlight took 9.5367431640625e-06s
INFO | --- Analysis for dbpedia-spotlight took 1.9673635959625244s
Availability | SPARQL endpoint availability check for DBpedia Spotlight NIF NER Corpus took 3.886222839355469e-05s
Availability | VoID file availability check for DBpedia Spotlight NIF NER Corpus took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for DBpedia Spotlight NIF NER Corpus took 0.17115116119384766s
Reputation | Calculation of the PageRank for DBpedia Spotlight NIF NER Corpus took 0.020488977432250977s
Interlinking | Calculation of Degree of Connection for DBpedia Spotlight NIF NER Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBpedia Spotlight NIF NER Corpus took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for DBpedia Spotlight NIF NER Corpus took 6.318092346191406e-05s
Believability | Calculation of trust value for DBpedia Spotlight NIF NER Corpus took 1.049041748046875e-05s
INFO | --- Analysis for dbpedia-spotlight-nif-ner-corpus took 1.9574263095855713s
Availability | SPARQL endpoint availability check for DBpedia Wikidata took 3.886222839355469e-05s
Availability | VoID file availability check for DBpedia Wikidata took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for DBpedia Wikidata took 0.1770031452178955s
Reputation | Calculation of the PageRank for DBpedia Wikidata took 0.02142190933227539s
Interlinking | Calculation of Degree of Connection for DBpedia Wikidata took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBpedia Wikidata took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for DBpedia Wikidata took 3.0517578125e-05s
Believability | Calculation of trust value for DBpedia Wikidata took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia-wikidata took 1.9631984233856201s
Availability | SPARQL endpoint availability check for DBpedia took 8.082389831542969e-05s
Availability | VoID file availability check for DBpedia took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for DBpedia took 0.1731433868408203s
Reputation | Calculation of the PageRank for DBpedia took 0.022106409072875977s
Interlinking | Calculation of Degree of Connection for DBpedia took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DBpedia took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for DBpedia took 2.86102294921875e-05s
Believability | Calculation of trust value for DBpedia took 1.0251998901367188e-05s
INFO | --- Analysis for dbpedia_ took 1.9541802406311035s
Availability | SPARQL endpoint availability check for DBTropes took 4.291534423828125e-05s
Availability | VoID file availability check for DBTropes took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for DBTropes took 0.1704246997833252s
Reputation | Calculation of the PageRank for DBTropes took 0.021329879760742188s
Interlinking | Calculation of Degree of Connection for DBTropes took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for DBTropes took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for DBTropes took 9.036064147949219e-05s
Believability | Calculation of trust value for DBTropes took 5.4836273193359375e-06s
INFO | --- Analysis for dbtropes took 2.2090466022491455s
Availability | SPARQL endpoint availability check for DBTune – Music-Related RDF took 4.100799560546875e-05s
Availability | VoID file availability check for DBTune – Music-Related RDF took 0.0002372264862060547s
Completeness | Calculation of interlinking completeness for DBTune – Music-Related RDF took 0.17248153686523438s
Reputation | Calculation of the PageRank for DBTune – Music-Related RDF took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for DBTune – Music-Related RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune – Music-Related RDF took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for DBTune – Music-Related RDF took 4.0531158447265625e-05s
Believability | Calculation of trust value for DBTune – Music-Related RDF took 6.67572021484375e-06s
INFO | --- Analysis for dbtune took 1.917801856994629s
Availability | SPARQL endpoint availability check for DBTune.org Artists: Last.fm took 4.1961669921875e-05s
Availability | VoID file availability check for DBTune.org Artists: Last.fm took 0.0007295608520507812s
Completeness | Calculation of interlinking completeness for DBTune.org Artists: Last.fm took 0.17612886428833008s
Reputation | Calculation of the PageRank for DBTune.org Artists: Last.fm took 0.02039504051208496s
Interlinking | Calculation of Degree of Connection for DBTune.org Artists: Last.fm took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DBTune.org Artists: Last.fm took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for DBTune.org Artists: Last.fm took 5.507469177246094e-05s
Believability | Calculation of trust value for DBTune.org Artists: Last.fm took 6.4373016357421875e-06s
INFO | --- Analysis for dbtune-artists-last-fm took 1.9608194828033447s
Availability | SPARQL endpoint availability check for DBTune.org AudioScrobbler RDF Service took 4.220008850097656e-05s
Availability | VoID file availability check for DBTune.org AudioScrobbler RDF Service took 0.00023794174194335938s
Completeness | Calculation of interlinking completeness for DBTune.org AudioScrobbler RDF Service took 0.17940306663513184s
Reputation | Calculation of the PageRank for DBTune.org AudioScrobbler RDF Service took 0.020351648330688477s
Interlinking | Calculation of Degree of Connection for DBTune.org AudioScrobbler RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org AudioScrobbler RDF Service took 0.0007331371307373047s
Interlinking | Calculation of Clustering coefficient for DBTune.org AudioScrobbler RDF Service took 3.62396240234375e-05s
Believability | Calculation of trust value for DBTune.org AudioScrobbler RDF Service took 7.62939453125e-06s
INFO | --- Analysis for dbtune-audioscrobbler took 1.9189453125s
Availability | SPARQL endpoint availability check for DBTune.org/classical took 5.780306816101074s
Availability | VoID file availability check for DBTune.org/classical took 0.0006048679351806641s
Completeness | Calculation of interlinking completeness for DBTune.org/classical took 0.1819455623626709s
Reputation | Calculation of the PageRank for DBTune.org/classical took 0.020183324813842773s
Interlinking | Calculation of Degree of Connection for DBTune.org/classical took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org/classical took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for DBTune.org/classical took 9.918212890625e-05s
Believability | Calculation of trust value for DBTune.org/classical took 1.2636184692382812e-05s
INFO | --- Analysis for dbtune-classical took 8.167666673660278s
Availability | SPARQL endpoint availability check for DBTune.org John Peel sessions RDF server took 5.677443504333496s
Availability | VoID file availability check for DBTune.org John Peel sessions RDF server took 0.00022792816162109375s
Completeness | Calculation of interlinking completeness for DBTune.org John Peel sessions RDF server took 0.1747574806213379s
Reputation | Calculation of the PageRank for DBTune.org John Peel sessions RDF server took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for DBTune.org John Peel sessions RDF server took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for DBTune.org John Peel sessions RDF server took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for DBTune.org John Peel sessions RDF server took 6.580352783203125e-05s
Believability | Calculation of trust value for DBTune.org John Peel sessions RDF server took 5.4836273193359375e-06s
INFO | --- Analysis for dbtune-john-peel-sessions took 7.954771041870117s
Availability | SPARQL endpoint availability check for DBTune.org Magnatune RDF server took 5.558284044265747s
Availability | VoID file availability check for DBTune.org Magnatune RDF server took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for DBTune.org Magnatune RDF server took 0.1768350601196289s
Reputation | Calculation of the PageRank for DBTune.org Magnatune RDF server took 0.020336627960205078s
Interlinking | Calculation of Degree of Connection for DBTune.org Magnatune RDF server took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for DBTune.org Magnatune RDF server took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for DBTune.org Magnatune RDF server took 6.532669067382812e-05s
Believability | Calculation of trust value for DBTune.org Magnatune RDF server took 5.9604644775390625e-06s
INFO | --- Analysis for dbtune-magnatune took 7.991036415100098s
Availability | SPARQL endpoint availability check for DBTune.org Musicbrainz D2R Server took 180.48835706710815s
Availability | VoID file availability check for DBTune.org Musicbrainz D2R Server took 0.0002703666687011719s
Completeness | Calculation of interlinking completeness for DBTune.org Musicbrainz D2R Server took 0.17864060401916504s
Reputation | Calculation of the PageRank for DBTune.org Musicbrainz D2R Server took 0.02100658416748047s
Interlinking | Calculation of Degree of Connection for DBTune.org Musicbrainz D2R Server took 2.1457672119140625e-05s
Interlinking | Calculation of Centrality for DBTune.org Musicbrainz D2R Server took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for DBTune.org Musicbrainz D2R Server took 0.00011014938354492188s
Believability | Calculation of trust value for DBTune.org Musicbrainz D2R Server took 7.3909759521484375e-06s
INFO | --- Analysis for dbtune-musicbrainz took 312.8732068538666s
Availability | SPARQL endpoint availability check for DBTune.org MySpace RDF Service took 0.34482550621032715s
Availability | VoID file availability check for DBTune.org MySpace RDF Service took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for DBTune.org MySpace RDF Service took 0.17931342124938965s
Reputation | Calculation of the PageRank for DBTune.org MySpace RDF Service took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for DBTune.org MySpace RDF Service took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org MySpace RDF Service took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for DBTune.org MySpace RDF Service took 4.982948303222656e-05s
Believability | Calculation of trust value for DBTune.org MySpace RDF Service took 1.1920928955078125e-05s
INFO | --- Analysis for dbtune-myspace took 2.5941734313964844s
Availability | SPARQL endpoint availability check for OpenUpLabs DCLG took 8.106231689453125e-05s
Availability | VoID file availability check for OpenUpLabs DCLG took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for OpenUpLabs DCLG took 0.17813944816589355s
Reputation | Calculation of the PageRank for OpenUpLabs DCLG took 0.022363662719726562s
Interlinking | Calculation of Degree of Connection for OpenUpLabs DCLG took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs DCLG took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs DCLG took 2.956390380859375e-05s
Believability | Calculation of trust value for OpenUpLabs DCLG took 1.1682510375976562e-05s
INFO | --- Analysis for dclg-openuplabs took 1.990067958831787s
Availability | SPARQL endpoint availability check for data.dcs took 8.034706115722656e-05s
Availability | VoID file availability check for data.dcs took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for data.dcs took 0.17897844314575195s
Reputation | Calculation of the PageRank for data.dcs took 0.022257328033447266s
Interlinking | Calculation of Degree of Connection for data.dcs took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for data.dcs took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for data.dcs took 6.198883056640625e-05s
Believability | Calculation of trust value for data.dcs took 1.2159347534179688e-05s
INFO | --- Analysis for dcs-sheffield took 2.487663745880127s
Availability | SPARQL endpoint availability check for Germany - Bundesministerium der Finanzen - Budget took 4.0531158447265625e-05s
Availability | VoID file availability check for Germany - Bundesministerium der Finanzen - Budget took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Germany - Bundesministerium der Finanzen - Budget took 0.3550717830657959s
Reputation | Calculation of the PageRank for Germany - Bundesministerium der Finanzen - Budget took 0.020134449005126953s
Interlinking | Calculation of Degree of Connection for Germany - Bundesministerium der Finanzen - Budget took 1.0013580322265625e-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.075599670410156e-05s
Believability | Calculation of trust value for Germany - Bundesministerium der Finanzen - Budget took 7.3909759521484375e-06s
INFO | --- Analysis for de-budget took 2.400362730026245s
Availability | SPARQL endpoint availability check for de-gaap-ontology-lexicon took 4.3392181396484375e-05s
Availability | VoID file availability check for de-gaap-ontology-lexicon took 0.0005207061767578125s
Completeness | Calculation of interlinking completeness for de-gaap-ontology-lexicon took 0.17495989799499512s
Reputation | Calculation of the PageRank for de-gaap-ontology-lexicon took 0.020476818084716797s
Interlinking | Calculation of Degree of Connection for de-gaap-ontology-lexicon took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for de-gaap-ontology-lexicon took 0.0007672309875488281s
Interlinking | Calculation of Clustering coefficient for de-gaap-ontology-lexicon took 4.076957702636719e-05s
Believability | Calculation of trust value for de-gaap-ontology-lexicon took 1.1920928955078125e-05s
INFO | --- Analysis for de-gaap-ontology-lexicon took 1.9739725589752197s
Availability | SPARQL endpoint availability check for Debian Package Tracking System took 5.316734313964844e-05s
Availability | VoID file availability check for Debian Package Tracking System took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Debian Package Tracking System took 0.17508244514465332s
Reputation | Calculation of the PageRank for Debian Package Tracking System took 0.02028965950012207s
Interlinking | Calculation of Degree of Connection for Debian Package Tracking System took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Debian Package Tracking System took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Debian Package Tracking System took 4.220008850097656e-05s
Believability | Calculation of trust value for Debian Package Tracking System took 1.1205673217773438e-05s
INFO | --- Analysis for debian-package-tracking-system took 1.933105707168579s
Availability | SPARQL endpoint availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.00010418891906738281s
Availability | VoID file availability check for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.17530131340026855s
Reputation | Calculation of the PageRank for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 2.8133392333984375e-05s
Believability | Calculation of trust value for Delimitación Territorial de las Juntas Administrativas de Zaragoza took 1.239776611328125e-05s
INFO | --- Analysis for delimitacion-territorial-juntas-administrativas-zaragoza took 1.9715979099273682s
Availability | SPARQL endpoint availability check for Demografie took 4.029273986816406e-05s
Availability | VoID file availability check for Demografie took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Demografie took 0.18291807174682617s
Reputation | Calculation of the PageRank for Demografie took 0.020193815231323242s
Interlinking | Calculation of Degree of Connection for Demografie took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Demografie took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Demografie took 2.8133392333984375e-05s
Believability | Calculation of trust value for Demografie took 1.2159347534179688e-05s
INFO | --- Analysis for demografie took 1.9623627662658691s
Availability | SPARQL endpoint availability check for Projeto Desaparecidos took 8.273124694824219e-05s
Availability | VoID file availability check for Projeto Desaparecidos took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Projeto Desaparecidos took 0.1742420196533203s
Reputation | Calculation of the PageRank for Projeto Desaparecidos took 0.020154476165771484s
Interlinking | Calculation of Degree of Connection for Projeto Desaparecidos took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Projeto Desaparecidos took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Projeto Desaparecidos took 3.218650817871094e-05s
Believability | Calculation of trust value for Projeto Desaparecidos took 1.1682510375976562e-05s
INFO | --- Analysis for desaparecidos took 1.9735057353973389s
Availability | SPARQL endpoint availability check for Deusto Entrepreneurship: sharing business knowledge took 8.034706115722656e-05s
Availability | VoID file availability check for Deusto Entrepreneurship: sharing business knowledge took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Deusto Entrepreneurship: sharing business knowledge took 0.18257761001586914s
Reputation | Calculation of the PageRank for Deusto Entrepreneurship: sharing business knowledge took 0.020310401916503906s
Interlinking | Calculation of Degree of Connection for Deusto Entrepreneurship: sharing business knowledge took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Deusto Entrepreneurship: sharing business knowledge took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Deusto Entrepreneurship: sharing business knowledge took 9.512901306152344e-05s
Believability | Calculation of trust value for Deusto Entrepreneurship: sharing business knowledge took 1.0967254638671875e-05s
INFO | --- Analysis for deustoentrepreneurship took 2.015817642211914s
Availability | SPARQL endpoint availability check for DeustoTech (Deusto Institute of Technology) took 8.440017700195312e-05s
Availability | VoID file availability check for DeustoTech (Deusto Institute of Technology) took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for DeustoTech (Deusto Institute of Technology) took 0.17258667945861816s
Reputation | Calculation of the PageRank for DeustoTech (Deusto Institute of Technology) took 0.021471261978149414s
Interlinking | Calculation of Degree of Connection for DeustoTech (Deusto Institute of Technology) took 3.075599670410156e-05s
Interlinking | Calculation of Centrality for DeustoTech (Deusto Institute of Technology) took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DeustoTech (Deusto Institute of Technology) took 0.00010275840759277344s
Believability | Calculation of trust value for DeustoTech (Deusto Institute of Technology) took 1.1205673217773438e-05s
INFO | --- Analysis for deustotech took 1.9649608135223389s
Availability | SPARQL endpoint availability check for Deutsche Biographie took 1.4313578605651855s
Availability | VoID file availability check for Deutsche Biographie took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Deutsche Biographie took 0.17727351188659668s
Reputation | Calculation of the PageRank for Deutsche Biographie took 0.020194053649902344s
Interlinking | Calculation of Degree of Connection for Deutsche Biographie took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Deutsche Biographie took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Deutsche Biographie took 3.4332275390625e-05s
Believability | Calculation of trust value for Deutsche Biographie took 6.9141387939453125e-06s
INFO | --- Analysis for deutsche-biographie took 3.8737809658050537s
Availability | SPARQL endpoint availability check for Deutsche Nationalbibliografie (DNB) took 8.487701416015625e-05s
Availability | VoID file availability check for Deutsche Nationalbibliografie (DNB) took 0.0004837512969970703s
Completeness | Calculation of interlinking completeness for Deutsche Nationalbibliografie (DNB) took 0.18355774879455566s
Reputation | Calculation of the PageRank for Deutsche Nationalbibliografie (DNB) took 0.020181894302368164s
Interlinking | Calculation of Degree of Connection for Deutsche Nationalbibliografie (DNB) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Deutsche Nationalbibliografie (DNB) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Deutsche Nationalbibliografie (DNB) took 5.626678466796875e-05s
Believability | Calculation of trust value for Deutsche Nationalbibliografie (DNB) took 1.1205673217773438e-05s
INFO | --- Analysis for deutsche-nationalbibliografie-dnb took 1.998962640762329s
Availability | SPARQL endpoint availability check for dev8d took 8.225440979003906e-05s
Availability | VoID file availability check for dev8d took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for dev8d took 0.17476963996887207s
Reputation | Calculation of the PageRank for dev8d took 0.020200014114379883s
Interlinking | Calculation of Degree of Connection for dev8d took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for dev8d took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for dev8d took 6.318092346191406e-05s
Believability | Calculation of trust value for dev8d took 1.2159347534179688e-05s
INFO | --- Analysis for dev8d took 2.024749279022217s
Availability | SPARQL endpoint availability check for Dewey Decimal Classification (DDC) took 8.487701416015625e-05s
Availability | VoID file availability check for Dewey Decimal Classification (DDC) took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for Dewey Decimal Classification (DDC) took 0.18105435371398926s
Reputation | Calculation of the PageRank for Dewey Decimal Classification (DDC) took 0.020455360412597656s
Interlinking | Calculation of Degree of Connection for Dewey Decimal Classification (DDC) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Dewey Decimal Classification (DDC) took 0.0009300708770751953s
Interlinking | Calculation of Clustering coefficient for Dewey Decimal Classification (DDC) took 6.365776062011719e-05s
Believability | Calculation of trust value for Dewey Decimal Classification (DDC) took 1.239776611328125e-05s
INFO | --- Analysis for dewey_decimal_classification took 1.979637861251831s
Availability | SPARQL endpoint availability check for Distributed Hydrology Soil Vegetation Model took 4.00543212890625e-05s
Availability | VoID file availability check for Distributed Hydrology Soil Vegetation Model took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Distributed Hydrology Soil Vegetation Model took 0.18729710578918457s
Reputation | Calculation of the PageRank for Distributed Hydrology Soil Vegetation Model took 0.02039170265197754s
Interlinking | Calculation of Degree of Connection for Distributed Hydrology Soil Vegetation Model took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Distributed Hydrology Soil Vegetation Model took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Distributed Hydrology Soil Vegetation Model took 2.8133392333984375e-05s
Believability | Calculation of trust value for Distributed Hydrology Soil Vegetation Model took 1.2159347534179688e-05s
INFO | --- Analysis for DHSVM took 1.9936249256134033s
Availability | SPARQL endpoint availability check for Diachronic Ontologies from People's Daily took 8.153915405273438e-05s
Availability | VoID file availability check for Diachronic Ontologies from People's Daily took 0.0005552768707275391s
Completeness | Calculation of interlinking completeness for Diachronic Ontologies from People's Daily took 0.18249130249023438s
Reputation | Calculation of the PageRank for Diachronic Ontologies from People's Daily took 0.020475149154663086s
Interlinking | Calculation of Degree of Connection for Diachronic Ontologies from People's Daily took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Diachronic Ontologies from People's Daily took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Diachronic Ontologies from People's Daily took 2.7894973754882812e-05s
Believability | Calculation of trust value for Diachronic Ontologies from People's Daily took 1.239776611328125e-05s
INFO | --- Analysis for diachronic-ontologies-peoples-daily took 1.9964120388031006s
Availability | SPARQL endpoint availability check for Diavgeia took 3.9577484130859375e-05s
Availability | VoID file availability check for Diavgeia took 0.0005054473876953125s
Completeness | Calculation of interlinking completeness for Diavgeia took 0.1889638900756836s
Reputation | Calculation of the PageRank for Diavgeia took 0.02057027816772461s
Interlinking | Calculation of Degree of Connection for Diavgeia took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Diavgeia took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Diavgeia took 8.058547973632812e-05s
Believability | Calculation of trust value for Diavgeia took 1.3113021850585938e-05s
INFO | --- Analysis for diavgeia took 1.9744300842285156s
Availability | SPARQL endpoint availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 8.678436279296875e-05s
Availability | VoID file availability check for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.1861584186553955s
Reputation | Calculation of the PageRank for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.020362138748168945s
Interlinking | Calculation of Degree of Connection for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 0.00011992454528808594s
Believability | Calculation of trust value for Didactalia, índice de recursos educativos para profesores, padres y alumnos (GNOSS) took 1.239776611328125e-05s
INFO | --- Analysis for didactalia took 2.0108907222747803s
Availability | SPARQL endpoint availability check for diigo.feed took 4.1961669921875e-05s
Availability | VoID file availability check for diigo.feed took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for diigo.feed took 0.17142105102539062s
Reputation | Calculation of the PageRank for diigo.feed took 0.020288944244384766s
Interlinking | Calculation of Degree of Connection for diigo.feed took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for diigo.feed took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for diigo.feed took 2.9087066650390625e-05s
Believability | Calculation of trust value for diigo.feed took 1.2874603271484375e-05s
INFO | --- Analysis for diigo-feed took 1.9680743217468262s
Availability | SPARQL endpoint availability check for DisGeNET took 3.981590270996094e-05s
Availability | VoID file availability check for DisGeNET took 0.0002429485321044922s
Completeness | Calculation of interlinking completeness for DisGeNET took 0.17946767807006836s
Reputation | Calculation of the PageRank for DisGeNET took 0.020152807235717773s
Interlinking | Calculation of Degree of Connection for DisGeNET took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for DisGeNET took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for DisGeNET took 0.0001704692840576172s
Believability | Calculation of trust value for DisGeNET took 1.2636184692382812e-05s
INFO | --- Analysis for disgenet took 1.9665865898132324s
Availability | SPARQL endpoint availability check for CAP Italia in RDF took 8.559226989746094e-05s
Availability | VoID file availability check for CAP Italia in RDF took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for CAP Italia in RDF took 0.1790013313293457s
Reputation | Calculation of the PageRank for CAP Italia in RDF took 0.021590232849121094s
Interlinking | Calculation of Degree of Connection for CAP Italia in RDF took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for CAP Italia in RDF took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for CAP Italia in RDF took 2.956390380859375e-05s
Believability | Calculation of trust value for CAP Italia in RDF took 1.239776611328125e-05s
INFO | --- Analysis for disk took 2.077385187149048s
Availability | SPARQL endpoint availability check for Distritos de Zaragoza took 0.00010275840759277344s
Availability | VoID file availability check for Distritos de Zaragoza took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Distritos de Zaragoza took 0.18575310707092285s
Reputation | Calculation of the PageRank for Distritos de Zaragoza took 0.020162582397460938s
Interlinking | Calculation of Degree of Connection for Distritos de Zaragoza took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Distritos de Zaragoza took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Distritos de Zaragoza took 2.86102294921875e-05s
Believability | Calculation of trust value for Distritos de Zaragoza took 1.2636184692382812e-05s
INFO | --- Analysis for distritos-zaragoza took 1.9731993675231934s
Availability | SPARQL endpoint availability check for DKH (Deusto Knowledge Hub) took 8.368492126464844e-05s
Availability | VoID file availability check for DKH (Deusto Knowledge Hub) took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for DKH (Deusto Knowledge Hub) took 0.18494820594787598s
Reputation | Calculation of the PageRank for DKH (Deusto Knowledge Hub) took 0.020324230194091797s
Interlinking | Calculation of Degree of Connection for DKH (Deusto Knowledge Hub) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DKH (Deusto Knowledge Hub) took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for DKH (Deusto Knowledge Hub) took 2.8133392333984375e-05s
Believability | Calculation of trust value for DKH (Deusto Knowledge Hub) took 1.3589859008789062e-05s
INFO | --- Analysis for dkh-deusto-knowledge-hub took 1.9852070808410645s
Availability | SPARQL endpoint availability check for DM2E took 8.153915405273438e-05s
Availability | VoID file availability check for DM2E took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for DM2E took 0.1795506477355957s
Reputation | Calculation of the PageRank for DM2E took 0.021172523498535156s
Interlinking | Calculation of Degree of Connection for DM2E took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DM2E took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for DM2E took 0.00010609626770019531s
Believability | Calculation of trust value for DM2E took 9.059906005859375e-06s
INFO | --- Analysis for dm2e took 2.495476007461548s
Availability | SPARQL endpoint availability check for DMOZ RDF Dump took 4.38690185546875e-05s
Availability | VoID file availability check for DMOZ RDF Dump took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for DMOZ RDF Dump took 0.18050885200500488s
Reputation | Calculation of the PageRank for DMOZ RDF Dump took 0.020487308502197266s
Interlinking | Calculation of Degree of Connection for DMOZ RDF Dump took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for DMOZ RDF Dump took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for DMOZ RDF Dump took 3.0040740966796875e-05s
Believability | Calculation of trust value for DMOZ RDF Dump took 1.2159347534179688e-05s
INFO | --- Analysis for dmoz_rdf_dump took 1.978114128112793s
Availability | SPARQL endpoint availability check for Gemeinsame Normdatei (GND) took 8.249282836914062e-05s
Availability | VoID file availability check for Gemeinsame Normdatei (GND) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Gemeinsame Normdatei (GND) took 0.1748971939086914s
Reputation | Calculation of the PageRank for Gemeinsame Normdatei (GND) took 0.020561933517456055s
Interlinking | Calculation of Degree of Connection for Gemeinsame Normdatei (GND) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Gemeinsame Normdatei (GND) took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Gemeinsame Normdatei (GND) took 0.00014901161193847656s
Believability | Calculation of trust value for Gemeinsame Normdatei (GND) took 1.2159347534179688e-05s
INFO | --- Analysis for dnb-gemeinsame-normdatei took 1.9990620613098145s
Availability | SPARQL endpoint availability check for DOAP Store took 8.821487426757812e-05s
Availability | VoID file availability check for DOAP Store took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for DOAP Store took 0.18038153648376465s
Reputation | Calculation of the PageRank for DOAP Store took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for DOAP Store took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for DOAP Store took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for DOAP Store took 2.7894973754882812e-05s
Believability | Calculation of trust value for DOAP Store took 1.1920928955078125e-05s
INFO | --- Analysis for doap_store took 1.9577043056488037s
Availability | SPARQL endpoint availability check for CrossRef DOI Resolver took 3.981590270996094e-05s
Availability | VoID file availability check for CrossRef DOI Resolver took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for CrossRef DOI Resolver took 0.17510199546813965s
Reputation | Calculation of the PageRank for CrossRef DOI Resolver took 0.020181655883789062s
Interlinking | Calculation of Degree of Connection for CrossRef DOI Resolver took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CrossRef DOI Resolver took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for CrossRef DOI Resolver took 5.984306335449219e-05s
Believability | Calculation of trust value for CrossRef DOI Resolver took 1.2636184692382812e-05s
INFO | --- Analysis for doi took 1.9606008529663086s
Availability | SPARQL endpoint availability check for Driggu Florentino took 7.939338684082031e-05s
Availability | VoID file availability check for Driggu Florentino took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Driggu Florentino took 0.17689800262451172s
Reputation | Calculation of the PageRank for Driggu Florentino took 0.021216392517089844s
Interlinking | Calculation of Degree of Connection for Driggu Florentino took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Driggu Florentino took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Driggu Florentino took 2.7418136596679688e-05s
Believability | Calculation of trust value for Driggu Florentino took 1.1444091796875e-05s
INFO | --- Analysis for Driggu took 2.0169026851654053s
Availability | SPARQL endpoint availability check for Drug Data from the Health Insurance Fund of Macedonia took 8.463859558105469e-05s
Availability | VoID file availability check for Drug Data from the Health Insurance Fund of Macedonia took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for Drug Data from the Health Insurance Fund of Macedonia took 0.1762073040008545s
Reputation | Calculation of the PageRank for Drug Data from the Health Insurance Fund of Macedonia took 0.021363496780395508s
Interlinking | Calculation of Degree of Connection for Drug Data from the Health Insurance Fund of Macedonia took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Drug Data from the Health Insurance Fund of Macedonia took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Drug Data from the Health Insurance Fund of Macedonia took 3.4809112548828125e-05s
Believability | Calculation of trust value for Drug Data from the Health Insurance Fund of Macedonia took 1.1444091796875e-05s
INFO | --- Analysis for drug-data-hifm took 2.012495517730713s
Availability | SPARQL endpoint availability check for dspace took 8.177757263183594e-05s
Availability | VoID file availability check for dspace took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for dspace took 0.17259955406188965s
Reputation | Calculation of the PageRank for dspace took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for dspace took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for dspace took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for dspace took 3.0279159545898438e-05s
Believability | Calculation of trust value for dspace took 1.0013580322265625e-05s
INFO | --- Analysis for dspace took 1.9671971797943115s
Availability | SPARQL endpoint availability check for DURAARK - Linked Building Data took 9.655952453613281e-05s
Availability | VoID file availability check for DURAARK - Linked Building Data took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for DURAARK - Linked Building Data took 0.1841883659362793s
Reputation | Calculation of the PageRank for DURAARK - Linked Building Data took 0.0204007625579834s
Interlinking | Calculation of Degree of Connection for DURAARK - Linked Building Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for DURAARK - Linked Building Data took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for DURAARK - Linked Building Data took 3.123283386230469e-05s
Believability | Calculation of trust value for DURAARK - Linked Building Data took 1.0967254638671875e-05s
INFO | --- Analysis for duraark-linked-building-data took 1.9744398593902588s
Availability | SPARQL endpoint availability check for MetaLex Document Server took 8.034706115722656e-05s
Availability | VoID file availability check for MetaLex Document Server took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for MetaLex Document Server took 0.17318463325500488s
Reputation | Calculation of the PageRank for MetaLex Document Server took 0.020763158798217773s
Interlinking | Calculation of Degree of Connection for MetaLex Document Server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MetaLex Document Server took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for MetaLex Document Server took 3.2901763916015625e-05s
Believability | Calculation of trust value for MetaLex Document Server took 1.0967254638671875e-05s
INFO | --- Analysis for dutch-national-regulations-metalex took 1.9859740734100342s
Availability | SPARQL endpoint availability check for Dutch Ships and Sailors took 2.5031988620758057s
Availability | VoID file availability check for Dutch Ships and Sailors took 0.001112222671508789s
Completeness | Calculation of interlinking completeness for Dutch Ships and Sailors took 0.1792001724243164s
Reputation | Calculation of the PageRank for Dutch Ships and Sailors took 0.020401477813720703s
Interlinking | Calculation of Degree of Connection for Dutch Ships and Sailors took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Dutch Ships and Sailors took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Dutch Ships and Sailors took 3.790855407714844e-05s
Believability | Calculation of trust value for Dutch Ships and Sailors took 1.1205673217773438e-05s
INFO | --- Analysis for dutch-ships-and-sailors took 6.579483985900879s
Availability | SPARQL endpoint availability check for DWS-Group took 8.7738037109375e-05s
Availability | VoID file availability check for DWS-Group took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for DWS-Group took 0.17282390594482422s
Reputation | Calculation of the PageRank for DWS-Group took 0.020574092864990234s
Interlinking | Calculation of Degree of Connection for DWS-Group took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for DWS-Group took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for DWS-Group took 0.00010228157043457031s
Believability | Calculation of trust value for DWS-Group took 1.3113021850585938e-05s
INFO | --- Analysis for dws-group took 1.9760141372680664s
Availability | SPARQL endpoint availability check for E1 - Nuvem dados took 4.410743713378906e-05s
Availability | VoID file availability check for E1 - Nuvem dados took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for E1 - Nuvem dados took 0.1746363639831543s
Reputation | Calculation of the PageRank for E1 - Nuvem dados took 0.021574974060058594s
Interlinking | Calculation of Degree of Connection for E1 - Nuvem dados took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for E1 - Nuvem dados took 0.001070261001586914s
Interlinking | Calculation of Clustering coefficient for E1 - Nuvem dados took 4.124641418457031e-05s
Believability | Calculation of trust value for E1 - Nuvem dados took 1.2159347534179688e-05s
INFO | --- Analysis for E1 took 1.9680776596069336s
Availability | SPARQL endpoint availability check for eagle-i @ University of Alaska Fairbanks took 8.273124694824219e-05s
Availability | VoID file availability check for eagle-i @ University of Alaska Fairbanks took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Alaska Fairbanks took 0.18706583976745605s
Reputation | Calculation of the PageRank for eagle-i @ University of Alaska Fairbanks took 0.021354198455810547s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Alaska Fairbanks took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Alaska Fairbanks took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Alaska Fairbanks took 0.00011706352233886719s
Believability | Calculation of trust value for eagle-i @ University of Alaska Fairbanks took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-alaska took 2.005880117416382s
Availability | SPARQL endpoint availability check for eagle-i @ Clark Atlanta University took 8.440017700195312e-05s
Availability | VoID file availability check for eagle-i @ Clark Atlanta University took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for eagle-i @ Clark Atlanta University took 0.17865824699401855s
Reputation | Calculation of the PageRank for eagle-i @ Clark Atlanta University took 0.020354747772216797s
Interlinking | Calculation of Degree of Connection for eagle-i @ Clark Atlanta University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Clark Atlanta University took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Clark Atlanta University took 5.2928924560546875e-05s
Believability | Calculation of trust value for eagle-i @ Clark Atlanta University took 1.239776611328125e-05s
INFO | --- Analysis for eagle-i-cau took 1.9661409854888916s
Availability | SPARQL endpoint availability check for eagle-i @ The City College of New York took 8.082389831542969e-05s
Availability | VoID file availability check for eagle-i @ The City College of New York took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for eagle-i @ The City College of New York took 0.22494077682495117s
Reputation | Calculation of the PageRank for eagle-i @ The City College of New York took 0.027141809463500977s
Interlinking | Calculation of Degree of Connection for eagle-i @ The City College of New York took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for eagle-i @ The City College of New York took 0.0012922286987304688s
Interlinking | Calculation of Clustering coefficient for eagle-i @ The City College of New York took 9.894371032714844e-05s
Believability | Calculation of trust value for eagle-i @ The City College of New York took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-ccny-cuny took 2.038940191268921s
Availability | SPARQL endpoint availability check for eagle-i @ Charles R. Drew University took 6.175041198730469e-05s
Availability | VoID file availability check for eagle-i @ Charles R. Drew University took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for eagle-i @ Charles R. Drew University took 0.17771148681640625s
Reputation | Calculation of the PageRank for eagle-i @ Charles R. Drew University took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for eagle-i @ Charles R. Drew University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Charles R. Drew University took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Charles R. Drew University took 9.584426879882812e-05s
Believability | Calculation of trust value for eagle-i @ Charles R. Drew University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-cdrewu took 1.9442689418792725s
Availability | SPARQL endpoint availability check for eagle-i @ Dartmouth College took 8.177757263183594e-05s
Availability | VoID file availability check for eagle-i @ Dartmouth College took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for eagle-i @ Dartmouth College took 0.17410707473754883s
Reputation | Calculation of the PageRank for eagle-i @ Dartmouth College took 0.020810842514038086s
Interlinking | Calculation of Degree of Connection for eagle-i @ Dartmouth College took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Dartmouth College took 0.0009832382202148438s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Dartmouth College took 0.00017261505126953125s
Believability | Calculation of trust value for eagle-i @ Dartmouth College took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-dartmouth took 1.9840500354766846s
Availability | SPARQL endpoint availability check for eagle-i @ Florida Agricultural and Mechanical University took 8.273124694824219e-05s
Availability | VoID file availability check for eagle-i @ Florida Agricultural and Mechanical University took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for eagle-i @ Florida Agricultural and Mechanical University took 0.17861437797546387s
Reputation | Calculation of the PageRank for eagle-i @ Florida Agricultural and Mechanical University took 0.02061772346496582s
Interlinking | Calculation of Degree of Connection for eagle-i @ Florida Agricultural and Mechanical University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Florida Agricultural and Mechanical University took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Florida Agricultural and Mechanical University took 8.58306884765625e-05s
Believability | Calculation of trust value for eagle-i @ Florida Agricultural and Mechanical University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-famu took 1.9634029865264893s
Availability | SPARQL endpoint availability check for eagle-i @ Harvard University took 8.869171142578125e-05s
Availability | VoID file availability check for eagle-i @ Harvard University took 0.0004696846008300781s
Completeness | Calculation of interlinking completeness for eagle-i @ Harvard University took 0.1827709674835205s
Reputation | Calculation of the PageRank for eagle-i @ Harvard University took 0.020450830459594727s
Interlinking | Calculation of Degree of Connection for eagle-i @ Harvard University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Harvard University took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Harvard University took 0.0001285076141357422s
Believability | Calculation of trust value for eagle-i @ Harvard University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-harvard took 1.9891722202301025s
Availability | SPARQL endpoint availability check for eagle-i @ University of Hawai’i at Mānoa took 8.177757263183594e-05s
Availability | VoID file availability check for eagle-i @ University of Hawai’i at Mānoa took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Hawai’i at Mānoa took 0.17562150955200195s
Reputation | Calculation of the PageRank for eagle-i @ University of Hawai’i at Mānoa took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Hawai’i at Mānoa took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Hawai’i at Mānoa took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Hawai’i at Mānoa took 0.0001239776611328125s
Believability | Calculation of trust value for eagle-i @ University of Hawai’i at Mānoa took 5.245208740234375e-06s
INFO | --- Analysis for eagle-i-hawaii took 1.951413869857788s
Availability | SPARQL endpoint availability check for eagle-i @ Howard University took 4.0531158447265625e-05s
Availability | VoID file availability check for eagle-i @ Howard University took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for eagle-i @ Howard University took 0.18190622329711914s
Reputation | Calculation of the PageRank for eagle-i @ Howard University took 0.020302295684814453s
Interlinking | Calculation of Degree of Connection for eagle-i @ Howard University took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Howard University took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Howard University took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Howard University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-howard took 1.9729666709899902s
Availability | SPARQL endpoint availability check for eagle-i @ Hunter College took 8.893013000488281e-05s
Availability | VoID file availability check for eagle-i @ Hunter College took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for eagle-i @ Hunter College took 0.1779017448425293s
Reputation | Calculation of the PageRank for eagle-i @ Hunter College took 0.020574331283569336s
Interlinking | Calculation of Degree of Connection for eagle-i @ Hunter College took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for eagle-i @ Hunter College took 0.0008678436279296875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Hunter College took 7.700920104980469e-05s
Believability | Calculation of trust value for eagle-i @ Hunter College took 1.2636184692382812e-05s
INFO | --- Analysis for eagle-i-hunter-cuny took 1.9729399681091309s
Availability | SPARQL endpoint availability check for eagle-i @ Jackson State University took 3.9577484130859375e-05s
Availability | VoID file availability check for eagle-i @ Jackson State University took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for eagle-i @ Jackson State University took 0.17362523078918457s
Reputation | Calculation of the PageRank for eagle-i @ Jackson State University took 0.020276784896850586s
Interlinking | Calculation of Degree of Connection for eagle-i @ Jackson State University took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Jackson State University took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Jackson State University took 0.00014352798461914062s
Believability | Calculation of trust value for eagle-i @ Jackson State University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-jsu took 2.001474618911743s
Availability | SPARQL endpoint availability check for eagle-i @ Meharry Medical College took 3.9577484130859375e-05s
Availability | VoID file availability check for eagle-i @ Meharry Medical College took 0.00021505355834960938s
Completeness | Calculation of interlinking completeness for eagle-i @ Meharry Medical College took 0.17995738983154297s
Reputation | Calculation of the PageRank for eagle-i @ Meharry Medical College took 0.022504806518554688s
Interlinking | Calculation of Degree of Connection for eagle-i @ Meharry Medical College took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Meharry Medical College took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Meharry Medical College took 4.1484832763671875e-05s
Believability | Calculation of trust value for eagle-i @ Meharry Medical College took 1.1920928955078125e-05s
INFO | --- Analysis for eagle-i-meharry took 2.0252153873443604s
Availability | SPARQL endpoint availability check for eagle-i @ Montana State University took 3.9577484130859375e-05s
Availability | VoID file availability check for eagle-i @ Montana State University took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for eagle-i @ Montana State University took 0.17339706420898438s
Reputation | Calculation of the PageRank for eagle-i @ Montana State University took 0.02199530601501465s
Interlinking | Calculation of Degree of Connection for eagle-i @ Montana State University took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for eagle-i @ Montana State University took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Montana State University took 9.846687316894531e-05s
Believability | Calculation of trust value for eagle-i @ Montana State University took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-montana took 1.9854722023010254s
Availability | SPARQL endpoint availability check for eagle-i @ Morehouse School of Medicine took 4.1484832763671875e-05s
Availability | VoID file availability check for eagle-i @ Morehouse School of Medicine took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for eagle-i @ Morehouse School of Medicine took 0.18483924865722656s
Reputation | Calculation of the PageRank for eagle-i @ Morehouse School of Medicine took 0.02110433578491211s
Interlinking | Calculation of Degree of Connection for eagle-i @ Morehouse School of Medicine took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for eagle-i @ Morehouse School of Medicine took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Morehouse School of Medicine took 9.083747863769531e-05s
Believability | Calculation of trust value for eagle-i @ Morehouse School of Medicine took 1.1682510375976562e-05s
INFO | --- Analysis for eagle-i-msm took 1.9936330318450928s
Availability | SPARQL endpoint availability check for eagle-i @ Oregon Health and Science University took 8.392333984375e-05s
Availability | VoID file availability check for eagle-i @ Oregon Health and Science University took 0.00035071372985839844s
Completeness | Calculation of interlinking completeness for eagle-i @ Oregon Health and Science University took 0.18158483505249023s
Reputation | Calculation of the PageRank for eagle-i @ Oregon Health and Science University took 0.02042102813720703s
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.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Oregon Health and Science University took 0.0001251697540283203s
Believability | Calculation of trust value for eagle-i @ Oregon Health and Science University took 1.0967254638671875e-05s
INFO | --- Analysis for eagle-i-ohsu took 2.040814161300659s
Availability | SPARQL endpoint availability check for eagle-i @ Ponce School of Medicine took 3.9577484130859375e-05s
Availability | VoID file availability check for eagle-i @ Ponce School of Medicine took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for eagle-i @ Ponce School of Medicine took 0.17837834358215332s
Reputation | Calculation of the PageRank for eagle-i @ Ponce School of Medicine took 0.020615100860595703s
Interlinking | Calculation of Degree of Connection for eagle-i @ Ponce School of Medicine took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Ponce School of Medicine took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Ponce School of Medicine took 6.651878356933594e-05s
Believability | Calculation of trust value for eagle-i @ Ponce School of Medicine took 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-psm took 1.9908416271209717s
Availability | SPARQL endpoint availability check for eagle-i @ Texas Southern University took 3.910064697265625e-05s
Availability | VoID file availability check for eagle-i @ Texas Southern University took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for eagle-i @ Texas Southern University took 0.18504548072814941s
Reputation | Calculation of the PageRank for eagle-i @ Texas Southern University took 0.02043771743774414s
Interlinking | Calculation of Degree of Connection for eagle-i @ Texas Southern University took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Texas Southern University took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Texas Southern University took 6.341934204101562e-05s
Believability | Calculation of trust value for eagle-i @ Texas Southern University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-tsu took 1.9784622192382812s
Availability | SPARQL endpoint availability check for eagle-i @ Tuskegee University took 0.00010204315185546875s
Availability | VoID file availability check for eagle-i @ Tuskegee University took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for eagle-i @ Tuskegee University took 0.18090558052062988s
Reputation | Calculation of the PageRank for eagle-i @ Tuskegee University took 0.02042555809020996s
Interlinking | Calculation of Degree of Connection for eagle-i @ Tuskegee University took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Tuskegee University took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Tuskegee University took 6.365776062011719e-05s
Believability | Calculation of trust value for eagle-i @ Tuskegee University took 1.1205673217773438e-05s
INFO | --- Analysis for eagle-i-tuskegee took 1.9665699005126953s
Availability | SPARQL endpoint availability check for eagle-i @ Universidad Central del Caribe took 4.0531158447265625e-05s
Availability | VoID file availability check for eagle-i @ Universidad Central del Caribe took 0.0005075931549072266s
Completeness | Calculation of interlinking completeness for eagle-i @ Universidad Central del Caribe took 0.18038010597229004s
Reputation | Calculation of the PageRank for eagle-i @ Universidad Central del Caribe took 0.020721912384033203s
Interlinking | Calculation of Degree of Connection for eagle-i @ Universidad Central del Caribe took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ Universidad Central del Caribe took 0.0007102489471435547s
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 6.198883056640625e-06s
INFO | --- Analysis for eagle-i-uccaribe took 1.9826915264129639s
Availability | SPARQL endpoint availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 8.249282836914062e-05s
Availability | VoID file availability check for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0005350112915039062s
Completeness | Calculation of interlinking completeness for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.17631864547729492s
Reputation | Calculation of the PageRank for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.02035689353942871s
Interlinking | Calculation of Degree of Connection for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 0.00012159347534179688s
Believability | Calculation of trust value for eagle-i@ University of Puerto Rico - Medical Sciences Campus took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-upr took 1.9830071926116943s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at El Paso took 4.029273986816406e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at El Paso took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at El Paso took 0.17831087112426758s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at El Paso took 0.021361589431762695s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at El Paso took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at El Paso took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at El Paso took 6.0558319091796875e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at El Paso took 1.1444091796875e-05s
INFO | --- Analysis for eagle-i-utep took 2.1109702587127686s
Availability | SPARQL endpoint availability check for eagle-i @ University of Texas at San Antonio took 8.535385131835938e-05s
Availability | VoID file availability check for eagle-i @ University of Texas at San Antonio took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for eagle-i @ University of Texas at San Antonio took 0.1792747974395752s
Reputation | Calculation of the PageRank for eagle-i @ University of Texas at San Antonio took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for eagle-i @ University of Texas at San Antonio took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for eagle-i @ University of Texas at San Antonio took 6.628036499023438e-05s
Believability | Calculation of trust value for eagle-i @ University of Texas at San Antonio took 1.0251998901367188e-05s
INFO | --- Analysis for eagle-i-utsa took 2.035855770111084s
Availability | SPARQL endpoint availability check for eagle-i @ Vanderbilt University took 4.3392181396484375e-05s
Availability | VoID file availability check for eagle-i @ Vanderbilt University took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for eagle-i @ Vanderbilt University took 0.177321195602417s
Reputation | Calculation of the PageRank for eagle-i @ Vanderbilt University took 0.02163243293762207s
Interlinking | Calculation of Degree of Connection for eagle-i @ Vanderbilt University took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for eagle-i @ Vanderbilt University took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Vanderbilt University took 0.00010752677917480469s
Believability | Calculation of trust value for eagle-i @ Vanderbilt University took 1.2159347534179688e-05s
INFO | --- Analysis for eagle-i-vanderbilt took 1.9726955890655518s
Availability | SPARQL endpoint availability check for eagle-i @ Xavier University of Louisiana took 4.410743713378906e-05s
Availability | VoID file availability check for eagle-i @ Xavier University of Louisiana took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for eagle-i @ Xavier University of Louisiana took 0.22580242156982422s
Reputation | Calculation of the PageRank for eagle-i @ Xavier University of Louisiana took 0.021402359008789062s
Interlinking | Calculation of Degree of Connection for eagle-i @ Xavier University of Louisiana took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for eagle-i @ Xavier University of Louisiana took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for eagle-i @ Xavier University of Louisiana took 7.414817810058594e-05s
Believability | Calculation of trust value for eagle-i @ Xavier University of Louisiana took 5.9604644775390625e-06s
INFO | --- Analysis for eagle-i-xula took 2.029505491256714s
Availability | SPARQL endpoint availability check for Emergency situation took 7.987022399902344e-05s
Availability | VoID file availability check for Emergency situation took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for Emergency situation took 0.19214510917663574s
Reputation | Calculation of the PageRank for Emergency situation took 0.022454500198364258s
Interlinking | Calculation of Degree of Connection for Emergency situation took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Emergency situation took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Emergency situation took 4.744529724121094e-05s
Believability | Calculation of trust value for Emergency situation took 5.0067901611328125e-06s
INFO | --- Analysis for Earthquake took 1.9698290824890137s
Availability | SPARQL endpoint availability check for ESO took 4.6253204345703125e-05s
Availability | VoID file availability check for ESO took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for ESO took 0.17369318008422852s
Reputation | Calculation of the PageRank for ESO took 0.021943092346191406s
Interlinking | Calculation of Degree of Connection for ESO took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for ESO took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for ESO took 8.177757263183594e-05s
Believability | Calculation of trust value for ESO took 1.2874603271484375e-05s
INFO | --- Analysis for Earthquake_case took 1.9824092388153076s
Availability | SPARQL endpoint availability check for European Central Bank (ECB) Linked Data took 8.463859558105469e-05s
Availability | VoID file availability check for European Central Bank (ECB) Linked Data took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for European Central Bank (ECB) Linked Data took 0.18776226043701172s
Reputation | Calculation of the PageRank for European Central Bank (ECB) Linked Data took 0.021346092224121094s
Interlinking | Calculation of Degree of Connection for European Central Bank (ECB) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for European Central Bank (ECB) Linked Data took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for European Central Bank (ECB) Linked Data took 0.00010013580322265625s
Believability | Calculation of trust value for European Central Bank (ECB) Linked Data took 4.76837158203125e-06s
INFO | --- Analysis for ecb-linked-data took 1.9829432964324951s
Availability | SPARQL endpoint availability check for European Central Bank Statistics (PublicData.eu) took 8.368492126464844e-05s
Availability | VoID file availability check for European Central Bank Statistics (PublicData.eu) took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for European Central Bank Statistics (PublicData.eu) took 0.18314647674560547s
Reputation | Calculation of the PageRank for European Central Bank Statistics (PublicData.eu) took 0.020428180694580078s
Interlinking | Calculation of Degree of Connection for European Central Bank Statistics (PublicData.eu) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Central Bank Statistics (PublicData.eu) took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for European Central Bank Statistics (PublicData.eu) took 4.029273986816406e-05s
Believability | Calculation of trust value for European Central Bank Statistics (PublicData.eu) took 1.3828277587890625e-05s
INFO | --- Analysis for ecb-statistics-linked-data took 2.014953136444092s
Availability | SPARQL endpoint availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 1.4895906448364258s
Availability | VoID file availability check for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for ECCO-TCP Eighteenth Century Texts Linked Data took 0.17620086669921875s
Reputation | Calculation of the PageRank for ECCO-TCP Eighteenth Century Texts Linked Data took 0.022206783294677734s
Interlinking | Calculation of Degree of Connection for ECCO-TCP Eighteenth Century Texts Linked Data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ECCO-TCP Eighteenth Century Texts Linked Data took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for ECCO-TCP Eighteenth Century Texts Linked Data took 6.604194641113281e-05s
Believability | Calculation of trust value for ECCO-TCP Eighteenth Century Texts Linked Data took 9.775161743164062e-06s
INFO | --- Analysis for ecco-tcp-linked-data took 4.284539699554443s
Availability | SPARQL endpoint availability check for ECLAP took 20.58326530456543s
Availability | VoID file availability check for ECLAP took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for ECLAP took 0.17571306228637695s
Reputation | Calculation of the PageRank for ECLAP took 0.02036595344543457s
Interlinking | Calculation of Degree of Connection for ECLAP took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for ECLAP took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ECLAP took 3.9577484130859375e-05s
Believability | Calculation of trust value for ECLAP took 1.2159347534179688e-05s
INFO | --- Analysis for eclap took 52.778059244155884s
Availability | SPARQL endpoint availability check for 《老子》译本传播知识图谱 took 8.273124694824219e-05s
Availability | VoID file availability check for 《老子》译本传播知识图谱 took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for 《老子》译本传播知识图谱 took 0.17435145378112793s
Reputation | Calculation of the PageRank for 《老子》译本传播知识图谱 took 0.02173304557800293s
Interlinking | Calculation of Degree of Connection for 《老子》译本传播知识图谱 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for 《老子》译本传播知识图谱 took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for 《老子》译本传播知识图谱 took 1.33514404296875e-05s
Believability | Calculation of trust value for 《老子》译本传播知识图谱 took 8.58306884765625e-06s
INFO | --- Analysis for ECNU-GISer took 1.9458317756652832s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 4.220008850097656e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0003170967102050781s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.17752647399902344s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.02109551429748535s
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.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 5.626678466796875e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 8.344650268554688e-06s
INFO | --- Analysis for ecs took 1.9592041969299316s
Availability | SPARQL endpoint availability check for Edificios Históricos en Zaragoza took 5.0067901611328125e-05s
Availability | VoID file availability check for Edificios Históricos en Zaragoza took 0.00031495094299316406s
Completeness | Calculation of interlinking completeness for Edificios Históricos en Zaragoza took 0.1742546558380127s
Reputation | Calculation of the PageRank for Edificios Históricos en Zaragoza took 0.020488739013671875s
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.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for Edificios Históricos en Zaragoza took 4.029273986816406e-05s
Believability | Calculation of trust value for Edificios Históricos en Zaragoza took 8.58306884765625e-06s
INFO | --- Analysis for edificios-historicos-zaragoza took 1.9052467346191406s
Availability | SPARQL endpoint availability check for Edublogs took 4.0531158447265625e-05s
Availability | VoID file availability check for Edublogs took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Edublogs took 0.16746973991394043s
Reputation | Calculation of the PageRank for Edublogs took 0.02017664909362793s
Interlinking | Calculation of Degree of Connection for Edublogs took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Edublogs took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Edublogs took 9.560585021972656e-05s
Believability | Calculation of trust value for Edublogs took 7.867813110351562e-06s
INFO | --- Analysis for edublogs took 1.922497272491455s
Availability | SPARQL endpoint availability check for education.data.gov.uk took 4.291534423828125e-05s
Availability | VoID file availability check for education.data.gov.uk took 0.00025010108947753906s
Completeness | Calculation of interlinking completeness for education.data.gov.uk took 0.16742706298828125s
Reputation | Calculation of the PageRank for education.data.gov.uk took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for education.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for education.data.gov.uk took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for education.data.gov.uk took 8.463859558105469e-05s
Believability | Calculation of trust value for education.data.gov.uk took 7.152557373046875e-06s
INFO | --- Analysis for education-data-gov-uk took 1.930734395980835s
Availability | SPARQL endpoint availability check for OpenUpLabs Education took 4.124641418457031e-05s
Availability | VoID file availability check for OpenUpLabs Education took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Education took 0.17096519470214844s
Reputation | Calculation of the PageRank for OpenUpLabs Education took 0.020652055740356445s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Education took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Education took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Education took 3.123283386230469e-05s
Believability | Calculation of trust value for OpenUpLabs Education took 6.9141387939453125e-06s
INFO | --- Analysis for education-openuplabs took 1.941617488861084s
Availability | SPARQL endpoint availability check for Educational programs - SISVU took 3.886222839355469e-05s
Availability | VoID file availability check for Educational programs - SISVU took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for Educational programs - SISVU took 0.17682385444641113s
Reputation | Calculation of the PageRank for Educational programs - SISVU took 0.022238731384277344s
Interlinking | Calculation of Degree of Connection for Educational programs - SISVU took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Educational programs - SISVU took 0.0007634162902832031s
Interlinking | Calculation of Clustering coefficient for Educational programs - SISVU took 5.054473876953125e-05s
Believability | Calculation of trust value for Educational programs - SISVU took 5.7220458984375e-06s
INFO | --- Analysis for educationalprograms_sisvu took 1.9626491069793701s
Availability | SPARQL endpoint availability check for European Environment Agency Published Products took 4.172325134277344e-05s
Availability | VoID file availability check for European Environment Agency Published Products took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for European Environment Agency Published Products took 0.17992877960205078s
Reputation | Calculation of the PageRank for European Environment Agency Published Products took 0.020891666412353516s
Interlinking | Calculation of Degree of Connection for European Environment Agency Published Products took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for European Environment Agency Published Products took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for European Environment Agency Published Products took 3.933906555175781e-05s
Believability | Calculation of trust value for European Environment Agency Published Products took 1.1682510375976562e-05s
INFO | --- Analysis for eea took 1.9663782119750977s
Availability | SPARQL endpoint availability check for EEA Reporting Obligations Database took 4.792213439941406e-05s
Availability | VoID file availability check for EEA Reporting Obligations Database took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for EEA Reporting Obligations Database took 0.17442584037780762s
Reputation | Calculation of the PageRank for EEA Reporting Obligations Database took 0.02022242546081543s
Interlinking | Calculation of Degree of Connection for EEA Reporting Obligations Database took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EEA Reporting Obligations Database took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for EEA Reporting Obligations Database took 5.2928924560546875e-05s
Believability | Calculation of trust value for EEA Reporting Obligations Database took 1.239776611328125e-05s
INFO | --- Analysis for eea-rod took 1.9559078216552734s
Availability | SPARQL endpoint availability check for EEA Vocabularies took 8.0108642578125e-05s
Availability | VoID file availability check for EEA Vocabularies took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for EEA Vocabularies took 0.1807539463043213s
Reputation | Calculation of the PageRank for EEA Vocabularies took 0.02036905288696289s
Interlinking | Calculation of Degree of Connection for EEA Vocabularies took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EEA Vocabularies took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for EEA Vocabularies took 9.107589721679688e-05s
Believability | Calculation of trust value for EEA Vocabularies took 1.239776611328125e-05s
INFO | --- Analysis for eea-vocabularies took 2.0176408290863037s
Availability | SPARQL endpoint availability check for Ege University Linked Open Data took 8.273124694824219e-05s
Availability | VoID file availability check for Ege University Linked Open Data took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Ege University Linked Open Data took 0.1795063018798828s
Reputation | Calculation of the PageRank for Ege University Linked Open Data took 0.020154714584350586s
Interlinking | Calculation of Degree of Connection for Ege University Linked Open Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ege University Linked Open Data took 0.0007405281066894531s
Interlinking | Calculation of Clustering coefficient for Ege University Linked Open Data took 3.123283386230469e-05s
Believability | Calculation of trust value for Ege University Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for ege-university-linked-open-data took 1.9915387630462646s
Availability | SPARQL endpoint availability check for E-Government Ontology took 4.220008850097656e-05s
Availability | VoID file availability check for E-Government Ontology took 0.00029349327087402344s
Completeness | Calculation of interlinking completeness for E-Government Ontology took 0.18626904487609863s
Reputation | Calculation of the PageRank for E-Government Ontology took 0.020124197006225586s
Interlinking | Calculation of Degree of Connection for E-Government Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for E-Government Ontology took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for E-Government Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for E-Government Ontology took 8.106231689453125e-06s
INFO | --- Analysis for EGovOntology took 2.347944736480713s
Availability | SPARQL endpoint availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 9.894371032714844e-05s
Availability | VoID file availability check for Aragon Interoperable Information Structure EI2A - aragon open data took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Aragon Interoperable Information Structure EI2A - aragon open data took 0.18494200706481934s
Reputation | Calculation of the PageRank for Aragon Interoperable Information Structure EI2A - aragon open data took 0.020532846450805664s
Interlinking | Calculation of Degree of Connection for Aragon Interoperable Information Structure EI2A - aragon open data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Aragon Interoperable Information Structure EI2A - aragon open data took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Aragon Interoperable Information Structure EI2A - aragon open data took 4.601478576660156e-05s
Believability | Calculation of trust value for Aragon Interoperable Information Structure EI2A - aragon open data took 7.3909759521484375e-06s
INFO | --- Analysis for ei2a took 1.976700782775879s
Availability | SPARQL endpoint availability check for EIONET RDF Data took 4.2438507080078125e-05s
Availability | VoID file availability check for EIONET RDF Data took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for EIONET RDF Data took 0.18454241752624512s
Reputation | Calculation of the PageRank for EIONET RDF Data took 0.022215604782104492s
Interlinking | Calculation of Degree of Connection for EIONET RDF Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EIONET RDF Data took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for EIONET RDF Data took 0.00010633468627929688s
Believability | Calculation of trust value for EIONET RDF Data took 1.2159347534179688e-05s
INFO | --- Analysis for eionet-rdf took 1.9929563999176025s
Availability | SPARQL endpoint availability check for Google’s Easter Egg i took 4.482269287109375e-05s
Availability | VoID file availability check for Google’s Easter Egg i took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Google’s Easter Egg i took 0.17731571197509766s
Reputation | Calculation of the PageRank for Google’s Easter Egg i took 0.022432327270507812s
Interlinking | Calculation of Degree of Connection for Google’s Easter Egg i took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Google’s Easter Egg i took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Google’s Easter Egg i took 3.0994415283203125e-05s
Believability | Calculation of trust value for Google’s Easter Egg i took 1.239776611328125e-05s
INFO | --- Analysis for ElgooG_ took 1.981675148010254s
Availability | SPARQL endpoint availability check for ELTE Digital Institutional Repository (EDIT) took 7.867813110351562e-05s
Availability | VoID file availability check for ELTE Digital Institutional Repository (EDIT) took 0.0004296302795410156s
Completeness | Calculation of interlinking completeness for ELTE Digital Institutional Repository (EDIT) took 0.18964934349060059s
Reputation | Calculation of the PageRank for ELTE Digital Institutional Repository (EDIT) took 0.020180702209472656s
Interlinking | Calculation of Degree of Connection for ELTE Digital Institutional Repository (EDIT) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ELTE Digital Institutional Repository (EDIT) took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for ELTE Digital Institutional Repository (EDIT) took 2.8133392333984375e-05s
Believability | Calculation of trust value for ELTE Digital Institutional Repository (EDIT) took 1.0967254638671875e-05s
INFO | --- Analysis for elte-digital-institutional-repository-edit took 1.9787983894348145s
Availability | SPARQL endpoint availability check for El Viajero's tourism dataset took 3.933906555175781e-05s
Availability | VoID file availability check for El Viajero's tourism dataset took 0.000457763671875s
Completeness | Calculation of interlinking completeness for El Viajero's tourism dataset took 0.18329882621765137s
Reputation | Calculation of the PageRank for El Viajero's tourism dataset took 0.021881818771362305s
Interlinking | Calculation of Degree of Connection for El Viajero's tourism dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for El Viajero's tourism dataset took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for El Viajero's tourism dataset took 7.152557373046875e-05s
Believability | Calculation of trust value for El Viajero's tourism dataset took 1.1920928955078125e-05s
INFO | --- Analysis for elviajero took 1.993260145187378s
Availability | SPARQL endpoint availability check for EMN took 7.987022399902344e-05s
Availability | VoID file availability check for EMN took 0.00022363662719726562s
Completeness | Calculation of interlinking completeness for EMN took 0.18194341659545898s
Reputation | Calculation of the PageRank for EMN took 0.020958900451660156s
Interlinking | Calculation of Degree of Connection for EMN took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EMN took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for EMN took 3.743171691894531e-05s
Believability | Calculation of trust value for EMN took 1.0013580322265625e-05s
INFO | --- Analysis for emn took 1.937363862991333s
Availability | SPARQL endpoint availability check for EnAKTing CO2 Emission Dataset took 8.320808410644531e-05s
Availability | VoID file availability check for EnAKTing CO2 Emission Dataset took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for EnAKTing CO2 Emission Dataset took 0.17405271530151367s
Reputation | Calculation of the PageRank for EnAKTing CO2 Emission Dataset took 0.020502090454101562s
Interlinking | Calculation of Degree of Connection for EnAKTing CO2 Emission Dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for EnAKTing CO2 Emission Dataset took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for EnAKTing CO2 Emission Dataset took 4.9114227294921875e-05s
Believability | Calculation of trust value for EnAKTing CO2 Emission Dataset took 5.4836273193359375e-06s
INFO | --- Analysis for enakting-co2emission took 1.9716546535491943s
Availability | SPARQL endpoint availability check for EnAKTing Crime Dataset took 8.058547973632812e-05s
Availability | VoID file availability check for EnAKTing Crime Dataset took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for EnAKTing Crime Dataset took 0.17250680923461914s
Reputation | Calculation of the PageRank for EnAKTing Crime Dataset took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for EnAKTing Crime Dataset took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EnAKTing Crime Dataset took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for EnAKTing Crime Dataset took 4.00543212890625e-05s
Believability | Calculation of trust value for EnAKTing Crime Dataset took 1.0013580322265625e-05s
INFO | --- Analysis for enakting-crime took 1.9781208038330078s
Availability | SPARQL endpoint availability check for EnAKTing Energy Dataset took 8.20159912109375e-05s
Availability | VoID file availability check for EnAKTing Energy Dataset took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for EnAKTing Energy Dataset took 0.17127323150634766s
Reputation | Calculation of the PageRank for EnAKTing Energy Dataset took 0.02027440071105957s
Interlinking | Calculation of Degree of Connection for EnAKTing Energy Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EnAKTing Energy Dataset took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for EnAKTing Energy Dataset took 3.743171691894531e-05s
Believability | Calculation of trust value for EnAKTing Energy Dataset took 1.239776611328125e-05s
INFO | --- Analysis for enakting-energy took 1.9515151977539062s
Availability | SPARQL endpoint availability check for EnAKTing Mortality Dataset took 8.058547973632812e-05s
Availability | VoID file availability check for EnAKTing Mortality Dataset took 0.0005402565002441406s
Completeness | Calculation of interlinking completeness for EnAKTing Mortality Dataset took 0.18336176872253418s
Reputation | Calculation of the PageRank for EnAKTing Mortality Dataset took 0.022579431533813477s
Interlinking | Calculation of Degree of Connection for EnAKTing Mortality Dataset took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for EnAKTing Mortality Dataset took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for EnAKTing Mortality Dataset took 9.179115295410156e-05s
Believability | Calculation of trust value for EnAKTing Mortality Dataset took 7.62939453125e-06s
INFO | --- Analysis for enakting-mortality took 1.9735498428344727s
Availability | SPARQL endpoint availability check for EnAKTing NHS Dataset took 4.1484832763671875e-05s
Availability | VoID file availability check for EnAKTing NHS Dataset took 0.00029659271240234375s
Completeness | Calculation of interlinking completeness for EnAKTing NHS Dataset took 0.18222284317016602s
Reputation | Calculation of the PageRank for EnAKTing NHS Dataset took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for EnAKTing NHS Dataset took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EnAKTing NHS Dataset took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for EnAKTing NHS Dataset took 4.00543212890625e-05s
Believability | Calculation of trust value for EnAKTing NHS Dataset took 8.58306884765625e-06s
INFO | --- Analysis for enakting-nhs took 1.9754204750061035s
Availability | SPARQL endpoint availability check for EnAKTing Population Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for EnAKTing Population Dataset took 0.00023055076599121094s
Completeness | Calculation of interlinking completeness for EnAKTing Population Dataset took 0.1772754192352295s
Reputation | Calculation of the PageRank for EnAKTing Population Dataset took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for EnAKTing Population Dataset took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EnAKTing Population Dataset took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for EnAKTing Population Dataset took 5.412101745605469e-05s
Believability | Calculation of trust value for EnAKTing Population Dataset took 8.344650268554688e-06s
INFO | --- Analysis for enakting-population took 1.9237945079803467s
Availability | SPARQL endpoint availability check for Enel Shops took 4.124641418457031e-05s
Availability | VoID file availability check for Enel Shops took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Enel Shops took 0.1719973087310791s
Reputation | Calculation of the PageRank for Enel Shops took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Enel Shops took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Enel Shops took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Enel Shops took 3.361701965332031e-05s
Believability | Calculation of trust value for Enel Shops took 7.867813110351562e-06s
INFO | --- Analysis for enel-shops took 1.9166584014892578s
Availability | SPARQL endpoint availability check for Energy efficiency assessments and improvements took 4.315376281738281e-05s
Availability | VoID file availability check for Energy efficiency assessments and improvements took 0.00028705596923828125s
Completeness | Calculation of interlinking completeness for Energy efficiency assessments and improvements took 0.17651963233947754s
Reputation | Calculation of the PageRank for Energy efficiency assessments and improvements took 0.02050304412841797s
Interlinking | Calculation of Degree of Connection for Energy efficiency assessments and improvements took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Energy efficiency assessments and improvements took 0.0007467269897460938s
Interlinking | Calculation of Clustering coefficient for Energy efficiency assessments and improvements took 3.457069396972656e-05s
Believability | Calculation of trust value for Energy efficiency assessments and improvements took 8.344650268554688e-06s
INFO | --- Analysis for energy-efficiency took 1.9421889781951904s
Availability | SPARQL endpoint availability check for English Heritage Archaeological Sciences Thesaurus took 4.8160552978515625e-05s
Availability | VoID file availability check for English Heritage Archaeological Sciences Thesaurus took 0.0002779960632324219s
Completeness | Calculation of interlinking completeness for English Heritage Archaeological Sciences Thesaurus took 0.17731046676635742s
Reputation | Calculation of the PageRank for English Heritage Archaeological Sciences Thesaurus took 0.021066665649414062s
Interlinking | Calculation of Degree of Connection for English Heritage Archaeological Sciences Thesaurus took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for English Heritage Archaeological Sciences Thesaurus took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for English Heritage Archaeological Sciences Thesaurus took 4.267692565917969e-05s
Believability | Calculation of trust value for English Heritage Archaeological Sciences Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for english-heritage-archaeological-sciences-thesaurus took 1.9359357357025146s
Availability | SPARQL endpoint availability check for English Heritage Building Materials Thesaurus took 8.535385131835938e-05s
Availability | VoID file availability check for English Heritage Building Materials Thesaurus took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for English Heritage Building Materials Thesaurus took 0.17816972732543945s
Reputation | Calculation of the PageRank for English Heritage Building Materials Thesaurus took 0.02038884162902832s
Interlinking | Calculation of Degree of Connection for English Heritage Building Materials Thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for English Heritage Building Materials Thesaurus took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for English Heritage Building Materials Thesaurus took 3.218650817871094e-05s
Believability | Calculation of trust value for English Heritage Building Materials Thesaurus took 8.58306884765625e-06s
INFO | --- Analysis for english-heritage-building-materials-thesaurus took 1.986457109451294s
Availability | SPARQL endpoint availability check for English Heritage Components Thesaurus took 8.058547973632812e-05s
Availability | VoID file availability check for English Heritage Components Thesaurus took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for English Heritage Components Thesaurus took 0.18188691139221191s
Reputation | Calculation of the PageRank for English Heritage Components Thesaurus took 0.02065134048461914s
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.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for English Heritage Components Thesaurus took 3.361701965332031e-05s
Believability | Calculation of trust value for English Heritage Components Thesaurus took 9.059906005859375e-06s
INFO | --- Analysis for english-heritage-components-thesaurus took 2.004542112350464s
Availability | SPARQL endpoint availability check for English Heritage Event Types Thesaurus took 8.20159912109375e-05s
Availability | VoID file availability check for English Heritage Event Types Thesaurus took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for English Heritage Event Types Thesaurus took 0.18128037452697754s
Reputation | Calculation of the PageRank for English Heritage Event Types Thesaurus took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for English Heritage Event Types Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for English Heritage Event Types Thesaurus took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for English Heritage Event Types Thesaurus took 3.218650817871094e-05s
Believability | Calculation of trust value for English Heritage Event Types Thesaurus took 1.6927719116210938e-05s
INFO | --- Analysis for english-heritage-event-types-thesaurus took 1.9564628601074219s
Availability | SPARQL endpoint availability check for English Heritage Evidence Thesaurus took 4.100799560546875e-05s
Availability | VoID file availability check for English Heritage Evidence Thesaurus took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for English Heritage Evidence Thesaurus took 0.17565274238586426s
Reputation | Calculation of the PageRank for English Heritage Evidence Thesaurus took 0.02039480209350586s
Interlinking | Calculation of Degree of Connection for English Heritage Evidence Thesaurus took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for English Heritage Evidence Thesaurus took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for English Heritage Evidence Thesaurus took 3.0279159545898438e-05s
Believability | Calculation of trust value for English Heritage Evidence Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for english-heritage-evidence-thesaurus took 1.9904954433441162s
Availability | SPARQL endpoint availability check for English Heritage Maritime Craft Thesaurus took 8.082389831542969e-05s
Availability | VoID file availability check for English Heritage Maritime Craft Thesaurus took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for English Heritage Maritime Craft Thesaurus took 0.18274974822998047s
Reputation | Calculation of the PageRank for English Heritage Maritime Craft Thesaurus took 0.02268362045288086s
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.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for English Heritage Maritime Craft Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for English Heritage Maritime Craft Thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for english-heritage-maritime-craft-thesaurus took 1.9859037399291992s
Availability | SPARQL endpoint availability check for English Heritage Monument Types Thesaurus took 5.53131103515625e-05s
Availability | VoID file availability check for English Heritage Monument Types Thesaurus took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for English Heritage Monument Types Thesaurus took 0.17640185356140137s
Reputation | Calculation of the PageRank for English Heritage Monument Types Thesaurus took 0.02201986312866211s
Interlinking | Calculation of Degree of Connection for English Heritage Monument Types Thesaurus took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for English Heritage Monument Types Thesaurus took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for English Heritage Monument Types Thesaurus took 3.2901763916015625e-05s
Believability | Calculation of trust value for English Heritage Monument Types Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for english-heritage-monument-types-thesaurus took 2.007521152496338s
Availability | SPARQL endpoint availability check for English Heritage Periods List took 1.200441837310791s
Availability | VoID file availability check for English Heritage Periods List took 0.0003337860107421875s
Extra | Recovery of all triples for English Heritage Periods List took 0.34432172775268555s
Performance | Total latancy measurement for English Heritage Periods List took 1.6547234058380127s
Amount of data | Number of triples check for English Heritage Periods List took 0.495983362197876s
Versatility | Languages check for English Heritage Periods List took 0.27771687507629395s
Interpretability | Number of blank nodes check for English Heritage Periods List took 0.5079712867736816s
Security | Check HTTPS for English Heritage Periods List took 0.21144962310791016s
Interpretability | RDF structures check for English Heritage Periods List took 0.27874755859375s
Versatility | Serialization formats check for English Heritage Periods List took 0.5023646354675293s
Availability | RDF dump link check for English Heritage Periods List took 0.33688926696777344s
License | MR license check for English Heritage Periods List took 0.4080686569213867s
License | HR license check for English Heritage Periods List took 0.3443763256072998s
Amount of data | Number of property check for English Heritage Periods List took 0.35917139053344727s
Understandability | Number of label check for English Heritage Periods List took 0.4374847412109375s
Understandability | URI regex check for English Heritage Periods List took 1.6484935283660889s
Understandability | Vocabs check for English Heritage Periods List took 0.3830263614654541s
Verifiability | Authors check for English Heritage Periods List took 0.37900424003601074s
Verifiability | Publishers check for English Heritage Periods List took 0.35428929328918457s
Performance | Throughput check for English Heritage Periods List took 12.812655448913574s
Amount of data | Check the number of entities for English Heritage Periods List took 6.651878356933594e-05s
Verifiability | Contribs. check for English Heritage Periods List took 0.34561657905578613s
Interlinking | sameAs chians check for English Heritage Periods List took 0.32057952880859375s
Interlinking | skos check for English Heritage Periods List took 0.3485705852508545s
Interlinking | skos check for English Heritage Periods List took 0.33995580673217773s
Timeliness | dataset update frequency check for English Heritage Periods List took 0.43358588218688965s
Currency | Creation date check for English Heritage Periods List took 0.6403911113739014s
Currency | Modification date check for English Heritage Periods List took 0.732574462890625s
Rep.Conc. | URIs length for English Heritage Periods List took 0.7204298973083496s
Interoperability | New vocabularies check for English Heritage Periods List took 3.337860107421875e-06s
Consistency | Deprecated classes/propertiers check for English Heritage Periods List took 0.348405122756958s
Accuracy | Check Functional Property for English Heritage Periods List took 0.32685303688049316s
Accuracy | Check Inverse Functional Property for English Heritage Periods List took 0.3161435127258301s
Consistency | Disjoint class check for English Heritage Periods List took 0.31161952018737793s
Consistency | Check Ontology hijacking for English Heritage Periods List took 0.34335947036743164s
Consistency | Check Invalid usage of undefined properties for English Heritage Periods List took 1.6050691604614258s
Conciseness | Check Extensional conciseness for English Heritage Periods List took 0.0001552104949951172s
Security | Sign check for English Heritage Periods List took 0.3460664749145508s
Completeness | Calculation of interlinking completeness for English Heritage Periods List took 0.17713069915771484s
Reputation | Calculation of the PageRank for English Heritage Periods List took 0.021990299224853516s
Interlinking | Calculation of Degree of Connection for English Heritage Periods List took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for English Heritage Periods List took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for English Heritage Periods List took 3.457069396972656e-05s
Interoperability | Check the re-using of existing vocabs for English Heritage Periods List took 1.6689300537109375e-06s
Believability | Calculation of trust value for English Heritage Periods List took 1.2159347534179688e-05s
INFO | --- Analysis for english-heritage-periods-list took 49.46327447891235s
Availability | SPARQL endpoint availability check for English Index of Multiple Deprivation Ranking 2010 took 3.981590270996094e-05s
Availability | VoID file availability check for English Index of Multiple Deprivation Ranking 2010 took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Ranking 2010 took 0.17472362518310547s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Ranking 2010 took 0.02052783966064453s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Ranking 2010 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Ranking 2010 took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Ranking 2010 took 3.528594970703125e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Ranking 2010 took 5.7220458984375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-ranking-2010 took 1.9178972244262695s
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.00021457672119140625s
Completeness | Calculation of interlinking completeness for English Index of Multiple Deprivation Score 2010 took 0.17512273788452148s
Reputation | Calculation of the PageRank for English Index of Multiple Deprivation Score 2010 took 0.020313739776611328s
Interlinking | Calculation of Degree of Connection for English Index of Multiple Deprivation Score 2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Index of Multiple Deprivation Score 2010 took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for English Index of Multiple Deprivation Score 2010 took 8.654594421386719e-05s
Believability | Calculation of trust value for English Index of Multiple Deprivation Score 2010 took 5.245208740234375e-06s
INFO | --- Analysis for english-index-of-multiple-deprivation-score-2010 took 1.9303278923034668s
Availability | SPARQL endpoint availability check for English Indices of Multiple Deprivation took 7.152557373046875e-05s
Availability | VoID file availability check for English Indices of Multiple Deprivation took 0.00020766258239746094s
Completeness | Calculation of interlinking completeness for English Indices of Multiple Deprivation took 0.17909479141235352s
Reputation | Calculation of the PageRank for English Indices of Multiple Deprivation took 0.020360708236694336s
Interlinking | Calculation of Degree of Connection for English Indices of Multiple Deprivation took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for English Indices of Multiple Deprivation took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for English Indices of Multiple Deprivation took 3.0994415283203125e-05s
Believability | Calculation of trust value for English Indices of Multiple Deprivation took 5.245208740234375e-06s
INFO | --- Analysis for english-indices-of-multiple-deprivation took 1.917243480682373s
Availability | SPARQL endpoint availability check for English WordNet took 4.3392181396484375e-05s
Availability | VoID file availability check for English WordNet took 0.00020551681518554688s
Completeness | Calculation of interlinking completeness for English WordNet took 0.16761088371276855s
Reputation | Calculation of the PageRank for English WordNet took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for English WordNet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English WordNet took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for English WordNet took 3.4332275390625e-05s
Believability | Calculation of trust value for English WordNet took 5.245208740234375e-06s
INFO | --- Analysis for english-wordnet took 1.915163278579712s
Availability | SPARQL endpoint availability check for English Heritage Places took 7.200241088867188e-05s
Availability | VoID file availability check for English Heritage Places took 0.00020885467529296875s
Completeness | Calculation of interlinking completeness for English Heritage Places took 0.17310309410095215s
Reputation | Calculation of the PageRank for English Heritage Places took 0.0206143856048584s
Interlinking | Calculation of Degree of Connection for English Heritage Places took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for English Heritage Places took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for English Heritage Places took 3.123283386230469e-05s
Believability | Calculation of trust value for English Heritage Places took 5.245208740234375e-06s
INFO | --- Analysis for englishheritage_places took 1.929065465927124s
Availability | SPARQL endpoint availability check for Enipedia - Energy Industry Data took 3.910064697265625e-05s
Availability | VoID file availability check for Enipedia - Energy Industry Data took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for Enipedia - Energy Industry Data took 0.16883087158203125s
Reputation | Calculation of the PageRank for Enipedia - Energy Industry Data took 0.020416975021362305s
Interlinking | Calculation of Degree of Connection for Enipedia - Energy Industry Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Enipedia - Energy Industry Data took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Enipedia - Energy Industry Data took 8.7738037109375e-05s
Believability | Calculation of trust value for Enipedia - Energy Industry Data took 5.245208740234375e-06s
INFO | --- Analysis for enipedia took 1.91916823387146s
Availability | SPARQL endpoint availability check for Enslaved.org took 8.606910705566406e-05s
Availability | VoID file availability check for Enslaved.org took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Enslaved.org took 0.1740097999572754s
Reputation | Calculation of the PageRank for Enslaved.org took 0.02086925506591797s
Interlinking | Calculation of Degree of Connection for Enslaved.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Enslaved.org took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Enslaved.org took 3.123283386230469e-05s
Believability | Calculation of trust value for Enslaved.org took 9.775161743164062e-06s
INFO | --- Analysis for enslaved.org took 3.2906835079193115s
Availability | SPARQL endpoint availability check for ENTICE Educational Episodes Knowledge Graph took 0.00011038780212402344s
Availability | VoID file availability check for ENTICE Educational Episodes Knowledge Graph took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for ENTICE Educational Episodes Knowledge Graph took 0.17492246627807617s
Reputation | Calculation of the PageRank for ENTICE Educational Episodes Knowledge Graph took 0.020406723022460938s
Interlinking | Calculation of Degree of Connection for ENTICE Educational Episodes Knowledge Graph took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ENTICE Educational Episodes Knowledge Graph took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for ENTICE Educational Episodes Knowledge Graph took 4.982948303222656e-05s
Believability | Calculation of trust value for ENTICE Educational Episodes Knowledge Graph took 1.0967254638671875e-05s
INFO | --- Analysis for entice-graph took 1.9540464878082275s
Availability | SPARQL endpoint availability check for Entrez Gene took 4.076957702636719e-05s
Availability | VoID file availability check for Entrez Gene took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Entrez Gene took 0.17524957656860352s
Reputation | Calculation of the PageRank for Entrez Gene took 0.028057575225830078s
Interlinking | Calculation of Degree of Connection for Entrez Gene took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Entrez Gene took 0.0011441707611083984s
Interlinking | Calculation of Clustering coefficient for Entrez Gene took 4.410743713378906e-05s
Believability | Calculation of trust value for Entrez Gene took 9.775161743164062e-06s
INFO | --- Analysis for entrez_gene took 1.95591402053833s
Availability | SPARQL endpoint availability check for Entrez Gene Extract took 8.344650268554688e-05s
Availability | VoID file availability check for Entrez Gene Extract took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Entrez Gene Extract took 0.17879486083984375s
Reputation | Calculation of the PageRank for Entrez Gene Extract took 0.021382808685302734s
Interlinking | Calculation of Degree of Connection for Entrez Gene Extract took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Entrez Gene Extract took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Entrez Gene Extract took 3.123283386230469e-05s
Believability | Calculation of trust value for Entrez Gene Extract took 1.0251998901367188e-05s
INFO | --- Analysis for entrez_gene_extract took 2.0117135047912598s
Availability | SPARQL endpoint availability check for Environment Agency Bathing Water Quality took 4.076957702636719e-05s
Availability | VoID file availability check for Environment Agency Bathing Water Quality took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Environment Agency Bathing Water Quality took 0.18302536010742188s
Reputation | Calculation of the PageRank for Environment Agency Bathing Water Quality took 0.021342039108276367s
Interlinking | Calculation of Degree of Connection for Environment Agency Bathing Water Quality took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Environment Agency Bathing Water Quality took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Environment Agency Bathing Water Quality took 5.054473876953125e-05s
Believability | Calculation of trust value for Environment Agency Bathing Water Quality took 1.0728836059570312e-05s
INFO | --- Analysis for environment-agency-bathing-water-quality took 2.026364326477051s
Availability | SPARQL endpoint availability check for environment.data.gov.uk took 0.0001049041748046875s
Availability | VoID file availability check for environment.data.gov.uk took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for environment.data.gov.uk took 0.1794579029083252s
Reputation | Calculation of the PageRank for environment.data.gov.uk took 0.02053546905517578s
Interlinking | Calculation of Degree of Connection for environment.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for environment.data.gov.uk took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for environment.data.gov.uk took 4.482269287109375e-05s
Believability | Calculation of trust value for environment.data.gov.uk took 1.1205673217773438e-05s
INFO | --- Analysis for environment-data-gov-uk took 1.9942958354949951s
Availability | SPARQL endpoint availability check for EARTh took 0.00011205673217773438s
Availability | VoID file availability check for EARTh took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for EARTh took 0.18520832061767578s
Reputation | Calculation of the PageRank for EARTh took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for EARTh took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EARTh took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for EARTh took 9.512901306152344e-05s
Believability | Calculation of trust value for EARTh took 1.0728836059570312e-05s
INFO | --- Analysis for environmental-applications-reference-thesaurus took 2.0483458042144775s
Availability | SPARQL endpoint availability check for Micka (EO metadata) @PSNC took 3.910064697265625e-05s
Availability | VoID file availability check for Micka (EO metadata) @PSNC took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Micka (EO metadata) @PSNC took 0.18538165092468262s
Reputation | Calculation of the PageRank for Micka (EO metadata) @PSNC took 0.020708560943603516s
Interlinking | Calculation of Degree of Connection for Micka (EO metadata) @PSNC took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Micka (EO metadata) @PSNC took 0.0007197856903076172s
Interlinking | Calculation of Clustering coefficient for Micka (EO metadata) @PSNC took 3.147125244140625e-05s
Believability | Calculation of trust value for Micka (EO metadata) @PSNC took 1.049041748046875e-05s
INFO | --- Analysis for EO_metadata took 1.9991867542266846s
Availability | SPARQL endpoint availability check for Earth Observation Knowledge Packages took 8.225440979003906e-05s
Availability | VoID file availability check for Earth Observation Knowledge Packages took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for Earth Observation Knowledge Packages took 0.17481446266174316s
Reputation | Calculation of the PageRank for Earth Observation Knowledge Packages took 0.020560026168823242s
Interlinking | Calculation of Degree of Connection for Earth Observation Knowledge Packages took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Earth Observation Knowledge Packages took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Earth Observation Knowledge Packages took 3.0517578125e-05s
Believability | Calculation of trust value for Earth Observation Knowledge Packages took 1.0251998901367188e-05s
INFO | --- Analysis for EOKP-Datasets took 1.9653420448303223s
Availability | SPARQL endpoint availability check for EPA-CDR took 8.130073547363281e-05s
Availability | VoID file availability check for EPA-CDR took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for EPA-CDR took 0.1737508773803711s
Reputation | Calculation of the PageRank for EPA-CDR took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for EPA-CDR took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for EPA-CDR took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for EPA-CDR took 3.6716461181640625e-05s
Believability | Calculation of trust value for EPA-CDR took 1.0013580322265625e-05s
INFO | --- Analysis for epa-cdr took 1.955066204071045s
Availability | SPARQL endpoint availability check for EPA-FRS took 8.058547973632812e-05s
Availability | VoID file availability check for EPA-FRS took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for EPA-FRS took 0.17350220680236816s
Reputation | Calculation of the PageRank for EPA-FRS took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for EPA-FRS took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-FRS took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for EPA-FRS took 7.486343383789062e-05s
Believability | Calculation of trust value for EPA-FRS took 1.0728836059570312e-05s
INFO | --- Analysis for epa-frs took 1.967500925064087s
Availability | SPARQL endpoint availability check for EPA-RCRA took 8.249282836914062e-05s
Availability | VoID file availability check for EPA-RCRA took 0.00020241737365722656s
Completeness | Calculation of interlinking completeness for EPA-RCRA took 0.18367934226989746s
Reputation | Calculation of the PageRank for EPA-RCRA took 0.020340442657470703s
Interlinking | Calculation of Degree of Connection for EPA-RCRA took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EPA-RCRA took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for EPA-RCRA took 3.3855438232421875e-05s
Believability | Calculation of trust value for EPA-RCRA took 5.245208740234375e-06s
INFO | --- Analysis for epa-rcra took 1.9944703578948975s
Availability | SPARQL endpoint availability check for EPA-SRS took 4.291534423828125e-05s
Availability | VoID file availability check for EPA-SRS took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for EPA-SRS took 0.17885732650756836s
Reputation | Calculation of the PageRank for EPA-SRS took 0.021684646606445312s
Interlinking | Calculation of Degree of Connection for EPA-SRS took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for EPA-SRS took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for EPA-SRS took 7.605552673339844e-05s
Believability | Calculation of trust value for EPA-SRS took 1.2874603271484375e-05s
INFO | --- Analysis for epa-srs took 2.009902000427246s
Availability | SPARQL endpoint availability check for EPA-TRI took 8.463859558105469e-05s
Availability | VoID file availability check for EPA-TRI took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for EPA-TRI took 0.18219995498657227s
Reputation | Calculation of the PageRank for EPA-TRI took 0.020544052124023438s
Interlinking | Calculation of Degree of Connection for EPA-TRI took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for EPA-TRI took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for EPA-TRI took 3.647804260253906e-05s
Believability | Calculation of trust value for EPA-TRI took 8.344650268554688e-06s
INFO | --- Analysis for epa-tri took 2.0314695835113525s
Availability | SPARQL endpoint availability check for European Patent Office (EPO) took 4.2438507080078125e-05s
Availability | VoID file availability check for European Patent Office (EPO) took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for European Patent Office (EPO) took 0.17467689514160156s
Reputation | Calculation of the PageRank for European Patent Office (EPO) took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for European Patent Office (EPO) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for European Patent Office (EPO) took 0.0006878376007080078s
Interlinking | Calculation of Clustering coefficient for European Patent Office (EPO) took 9.012222290039062e-05s
Believability | Calculation of trust value for European Patent Office (EPO) took 1.1205673217773438e-05s
INFO | --- Analysis for epo took 2.0079755783081055s
Availability | SPARQL endpoint availability check for ePrints Harvest (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for ePrints Harvest (RKBExplorer) took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for ePrints Harvest (RKBExplorer) took 0.18308353424072266s
Reputation | Calculation of the PageRank for ePrints Harvest (RKBExplorer) took 0.021350383758544922s
Interlinking | Calculation of Degree of Connection for ePrints Harvest (RKBExplorer) took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for ePrints Harvest (RKBExplorer) took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for ePrints Harvest (RKBExplorer) took 0.0001304149627685547s
Believability | Calculation of trust value for ePrints Harvest (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for eprints-harvest-rkbexplorer took 1.9728355407714844s
Availability | SPARQL endpoint availability check for European Pollutant Release and Transfer Register (E-PRTR) took 8.177757263183594e-05s
Availability | VoID file availability check for European Pollutant Release and Transfer Register (E-PRTR) took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for European Pollutant Release and Transfer Register (E-PRTR) took 0.171417236328125s
Reputation | Calculation of the PageRank for European Pollutant Release and Transfer Register (E-PRTR) took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for European Pollutant Release and Transfer Register (E-PRTR) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for European Pollutant Release and Transfer Register (E-PRTR) took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for European Pollutant Release and Transfer Register (E-PRTR) took 7.963180541992188e-05s
Believability | Calculation of trust value for European Pollutant Release and Transfer Register (E-PRTR) took 1.0013580322265625e-05s
INFO | --- Analysis for eprtr took 1.968545913696289s
Availability | SPARQL endpoint availability check for Railway Infrastructure KG took 8.320808410644531e-05s
Availability | VoID file availability check for Railway Infrastructure KG took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Railway Infrastructure KG took 0.18295979499816895s
Reputation | Calculation of the PageRank for Railway Infrastructure KG took 0.020863771438598633s
Interlinking | Calculation of Degree of Connection for Railway Infrastructure KG took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Railway Infrastructure KG took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Railway Infrastructure KG took 3.218650817871094e-05s
Believability | Calculation of trust value for Railway Infrastructure KG took 1.1444091796875e-05s
INFO | --- Analysis for ERAKG took 2.00396466255188s
Availability | SPARQL endpoint availability check for reg took 4.220008850097656e-05s
Availability | VoID file availability check for reg took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for reg took 0.18027448654174805s
Reputation | Calculation of the PageRank for reg took 0.022437334060668945s
Interlinking | Calculation of Degree of Connection for reg took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for reg took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for reg took 1.4066696166992188e-05s
Believability | Calculation of trust value for reg took 1.0728836059570312e-05s
INFO | --- Analysis for erg took 2.006844997406006s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Kingdom of Spain took 8.130073547363281e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Kingdom of Spain took 0.0008878707885742188s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Kingdom of Spain took 0.18121004104614258s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Kingdom of Spain took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Kingdom of Spain took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Kingdom of Spain took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Kingdom of Spain took 3.0517578125e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Kingdom of Spain took 1.0728836059570312e-05s
INFO | --- Analysis for es-msssi-drug-prices took 1.9873199462890625s
Availability | SPARQL endpoint availability check for ESD Standards: Controlled lists for the UK public sector took 4.100799560546875e-05s
Availability | VoID file availability check for ESD Standards: Controlled lists for the UK public sector took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for ESD Standards: Controlled lists for the UK public sector took 0.16834616661071777s
Reputation | Calculation of the PageRank for ESD Standards: Controlled lists for the UK public sector took 0.021330595016479492s
Interlinking | Calculation of Degree of Connection for ESD Standards: Controlled lists for the UK public sector took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for ESD Standards: Controlled lists for the UK public sector took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for ESD Standards: Controlled lists for the UK public sector took 9.036064147949219e-05s
Believability | Calculation of trust value for ESD Standards: Controlled lists for the UK public sector took 1.0013580322265625e-05s
INFO | --- Analysis for esd-standards took 1.9624032974243164s
Availability | SPARQL endpoint availability check for ESD-Toolkit took 8.20159912109375e-05s
Availability | VoID file availability check for ESD-Toolkit took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for ESD-Toolkit took 0.17848777770996094s
Reputation | Calculation of the PageRank for ESD-Toolkit took 0.02045726776123047s
Interlinking | Calculation of Degree of Connection for ESD-Toolkit took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for ESD-Toolkit took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for ESD-Toolkit took 7.05718994140625e-05s
Believability | Calculation of trust value for ESD-Toolkit took 1.0728836059570312e-05s
INFO | --- Analysis for esd-toolkit took 2.0299954414367676s
Availability | SPARQL endpoint availability check for Dataset Esis took 4.029273986816406e-05s
Availability | VoID file availability check for Dataset Esis took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Dataset Esis took 0.17633628845214844s
Reputation | Calculation of the PageRank for Dataset Esis took 0.02230048179626465s
Interlinking | Calculation of Degree of Connection for Dataset Esis took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Dataset Esis took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Dataset Esis took 3.314018249511719e-05s
Believability | Calculation of trust value for Dataset Esis took 6.198883056640625e-06s
INFO | --- Analysis for esislearning took 1.9507708549499512s
Availability | SPARQL endpoint availability check for The European Science Vocabulary (EuroSciVoc) took 8.106231689453125e-05s
Availability | VoID file availability check for The European Science Vocabulary (EuroSciVoc) took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for The European Science Vocabulary (EuroSciVoc) took 0.18341422080993652s
Reputation | Calculation of the PageRank for The European Science Vocabulary (EuroSciVoc) took 0.02214217185974121s
Interlinking | Calculation of Degree of Connection for The European Science Vocabulary (EuroSciVoc) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for The European Science Vocabulary (EuroSciVoc) took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for The European Science Vocabulary (EuroSciVoc) took 3.2901763916015625e-05s
Believability | Calculation of trust value for The European Science Vocabulary (EuroSciVoc) took 1.0013580322265625e-05s
INFO | --- Analysis for ESV took 2.029691696166992s
Availability | SPARQL endpoint availability check for Etymological Dictionary of Latin in LiLa took 8.130073547363281e-05s
Availability | VoID file availability check for Etymological Dictionary of Latin in LiLa took 0.0004341602325439453s
Completeness | Calculation of interlinking completeness for Etymological Dictionary of Latin in LiLa took 0.17442965507507324s
Reputation | Calculation of the PageRank for Etymological Dictionary of Latin in LiLa took 0.02150273323059082s
Interlinking | Calculation of Degree of Connection for Etymological Dictionary of Latin in LiLa took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Etymological Dictionary of Latin in LiLa took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Etymological Dictionary of Latin in LiLa took 3.8623809814453125e-05s
Believability | Calculation of trust value for Etymological Dictionary of Latin in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for EtymologicalDictionaryofLatin took 2.042449712753296s
Availability | SPARQL endpoint availability check for EU Agencies and decentralized bodies (Agencies) took 3.981590270996094e-05s
Availability | VoID file availability check for EU Agencies and decentralized bodies (Agencies) took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for EU Agencies and decentralized bodies (Agencies) took 0.1804518699645996s
Reputation | Calculation of the PageRank for EU Agencies and decentralized bodies (Agencies) took 0.022672653198242188s
Interlinking | Calculation of Degree of Connection for EU Agencies and decentralized bodies (Agencies) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EU Agencies and decentralized bodies (Agencies) took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for EU Agencies and decentralized bodies (Agencies) took 7.295608520507812e-05s
Believability | Calculation of trust value for EU Agencies and decentralized bodies (Agencies) took 1.0251998901367188e-05s
INFO | --- Analysis for eu-agencies-bodies took 1.9938950538635254s
Availability | SPARQL endpoint availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 8.130073547363281e-05s
Availability | VoID file availability check for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.00020384788513183594s
Completeness | Calculation of interlinking completeness for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.17237591743469238s
Reputation | Calculation of the PageRank for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.020945072174072266s
Interlinking | Calculation of Degree of Connection for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 3.147125244140625e-05s
Believability | Calculation of trust value for EU Directorate-General for Translation (DGT) - Acquis Communautaire took 1.0251998901367188e-05s
INFO | --- Analysis for eu-dgt-tm took 1.9526681900024414s
Availability | SPARQL endpoint availability check for Institutions and Bodies of the European Union took 8.130073547363281e-05s
Availability | VoID file availability check for Institutions and Bodies of the European Union took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Institutions and Bodies of the European Union took 0.2738046646118164s
Reputation | Calculation of the PageRank for Institutions and Bodies of the European Union took 0.020525693893432617s
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.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Institutions and Bodies of the European Union took 7.128715515136719e-05s
Believability | Calculation of trust value for Institutions and Bodies of the European Union took 1.1205673217773438e-05s
INFO | --- Analysis for eu-institutions took 2.072467565536499s
Availability | SPARQL endpoint availability check for EU Parliament Media Library took 3.981590270996094e-05s
Availability | VoID file availability check for EU Parliament Media Library took 0.00042748451232910156s
Completeness | Calculation of interlinking completeness for EU Parliament Media Library took 0.1724860668182373s
Reputation | Calculation of the PageRank for EU Parliament Media Library took 0.02033233642578125s
Interlinking | Calculation of Degree of Connection for EU Parliament Media Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EU Parliament Media Library took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for EU Parliament Media Library took 3.504753112792969e-05s
Believability | Calculation of trust value for EU Parliament Media Library took 1.0728836059570312e-05s
INFO | --- Analysis for eu-parliament-media took 1.9808590412139893s
Availability | SPARQL endpoint availability check for EU Who Is Who took 3.9577484130859375e-05s
Availability | VoID file availability check for EU Who Is Who took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for EU Who Is Who took 0.18419599533081055s
Reputation | Calculation of the PageRank for EU Who Is Who took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for EU Who Is Who took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EU Who Is Who took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for EU Who Is Who took 3.6716461181640625e-05s
Believability | Calculation of trust value for EU Who Is Who took 1.0728836059570312e-05s
INFO | --- Analysis for eu-who-is-who took 1.9860355854034424s
Availability | SPARQL endpoint availability check for EUMIDA as Linked Data took 4.00543212890625e-05s
Availability | VoID file availability check for EUMIDA as Linked Data took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for EUMIDA as Linked Data took 0.1783912181854248s
Reputation | Calculation of the PageRank for EUMIDA as Linked Data took 0.020514488220214844s
Interlinking | Calculation of Degree of Connection for EUMIDA as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for EUMIDA as Linked Data took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for EUMIDA as Linked Data took 4.2438507080078125e-05s
Believability | Calculation of trust value for EUMIDA as Linked Data took 1.33514404296875e-05s
INFO | --- Analysis for eumida-linked-data took 1.9949955940246582s
Availability | SPARQL endpoint availability check for European Nature Information System took 0.00010037422180175781s
Availability | VoID file availability check for European Nature Information System took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for European Nature Information System took 0.16817688941955566s
Reputation | Calculation of the PageRank for European Nature Information System took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for European Nature Information System took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for European Nature Information System took 0.0006892681121826172s
Interlinking | Calculation of Clustering coefficient for European Nature Information System took 0.00012540817260742188s
Believability | Calculation of trust value for European Nature Information System took 1.2636184692382812e-05s
INFO | --- Analysis for eunis took 1.9973552227020264s
Availability | SPARQL endpoint availability check for EUR-Lex as Linked Data took 4.220008850097656e-05s
Availability | VoID file availability check for EUR-Lex as Linked Data took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for EUR-Lex as Linked Data took 0.17672204971313477s
Reputation | Calculation of the PageRank for EUR-Lex as Linked Data took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for EUR-Lex as Linked Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EUR-Lex as Linked Data took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for EUR-Lex as Linked Data took 6.985664367675781e-05s
Believability | Calculation of trust value for EUR-Lex as Linked Data took 1.1444091796875e-05s
INFO | --- Analysis for eur-lex-rdf took 1.9743471145629883s
Availability | SPARQL endpoint availability check for Standard Eurobarometer took 8.225440979003906e-05s
Availability | VoID file availability check for Standard Eurobarometer took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Standard Eurobarometer took 0.20620942115783691s
Reputation | Calculation of the PageRank for Standard Eurobarometer took 0.020687103271484375s
Interlinking | Calculation of Degree of Connection for Standard Eurobarometer took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Standard Eurobarometer took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Standard Eurobarometer took 4.4345855712890625e-05s
Believability | Calculation of trust value for Standard Eurobarometer took 1.049041748046875e-05s
INFO | --- Analysis for eurobarometer-standard took 2.033257246017456s
Availability | SPARQL endpoint availability check for European Election Results took 0.00010418891906738281s
Availability | VoID file availability check for European Election Results took 0.00023412704467773438s
Completeness | Calculation of interlinking completeness for European Election Results took 0.18638157844543457s
Reputation | Calculation of the PageRank for European Election Results took 0.020423173904418945s
Interlinking | Calculation of Degree of Connection for European Election Results took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for European Election Results took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for European Election Results took 3.62396240234375e-05s
Believability | Calculation of trust value for European Election Results took 5.9604644775390625e-06s
INFO | --- Analysis for european-election-results took 1.9684209823608398s
Availability | SPARQL endpoint availability check for EPO patents took 8.106231689453125e-05s
Availability | VoID file availability check for EPO patents took 0.0002014636993408203s
Completeness | Calculation of interlinking completeness for EPO patents took 0.1737959384918213s
Reputation | Calculation of the PageRank for EPO patents took 0.02032613754272461s
Interlinking | Calculation of Degree of Connection for EPO patents took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EPO patents took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for EPO patents took 3.719329833984375e-05s
Believability | Calculation of trust value for EPO patents took 1.0728836059570312e-05s
INFO | --- Analysis for European_Patent_Information took 2.002128839492798s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data took 8.058547973632812e-05s
Availability | VoID file availability check for Europeana Linked Open Data took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data took 0.18409395217895508s
Reputation | Calculation of the PageRank for Europeana Linked Open Data took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana Linked Open Data took 0.000766754150390625s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Europeana Linked Open Data took 1.0251998901367188e-05s
INFO | --- Analysis for europeana-lod took 1.9820363521575928s
Availability | SPARQL endpoint availability check for Europeana Linked Open Data V1.0 took 8.893013000488281e-05s
Availability | VoID file availability check for Europeana Linked Open Data V1.0 took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for Europeana Linked Open Data V1.0 took 0.17814898490905762s
Reputation | Calculation of the PageRank for Europeana Linked Open Data V1.0 took 0.02048015594482422s
Interlinking | Calculation of Degree of Connection for Europeana Linked Open Data V1.0 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Europeana Linked Open Data V1.0 took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Europeana Linked Open Data V1.0 took 9.202957153320312e-05s
Believability | Calculation of trust value for Europeana Linked Open Data V1.0 took 9.059906005859375e-06s
INFO | --- Analysis for europeana-lod-v1 took 1.9900751113891602s
Availability | SPARQL endpoint availability check for Europeana SPARQL took 0.39774465560913086s
Availability | VoID file availability check for Europeana SPARQL took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for Europeana SPARQL took 0.17441058158874512s
Reputation | Calculation of the PageRank for Europeana SPARQL took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for Europeana SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Europeana SPARQL took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Europeana SPARQL took 4.863739013671875e-05s
Believability | Calculation of trust value for Europeana SPARQL took 1.1444091796875e-05s
INFO | --- Analysis for europeana-sparql took 2.8208324909210205s
Availability | SPARQL endpoint availability check for EuroSentiment took 8.296966552734375e-05s
Availability | VoID file availability check for EuroSentiment took 0.0001971721649169922s
Completeness | Calculation of interlinking completeness for EuroSentiment took 0.18921208381652832s
Reputation | Calculation of the PageRank for EuroSentiment took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for EuroSentiment took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for EuroSentiment took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for EuroSentiment took 3.790855407714844e-05s
Believability | Calculation of trust value for EuroSentiment took 5.0067901611328125e-06s
INFO | --- Analysis for eurosentiment took 1.977203130722046s
Availability | SPARQL endpoint availability check for Eurostat RDF datasets took 8.106231689453125e-05s
Availability | VoID file availability check for Eurostat RDF datasets took 0.0004906654357910156s
Completeness | Calculation of interlinking completeness for Eurostat RDF datasets took 0.17920923233032227s
Reputation | Calculation of the PageRank for Eurostat RDF datasets took 0.02063918113708496s
Interlinking | Calculation of Degree of Connection for Eurostat RDF datasets took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Eurostat RDF datasets took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Eurostat RDF datasets took 7.653236389160156e-05s
Believability | Calculation of trust value for Eurostat RDF datasets took 1.0251998901367188e-05s
INFO | --- Analysis for eurostat-rdf took 1.986729621887207s
Availability | SPARQL endpoint availability check for EuroVoc took 8.487701416015625e-05s
Availability | VoID file availability check for EuroVoc took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for EuroVoc took 0.19188141822814941s
Reputation | Calculation of the PageRank for EuroVoc took 0.022619247436523438s
Interlinking | Calculation of Degree of Connection for EuroVoc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EuroVoc took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for EuroVoc took 6.961822509765625e-05s
Believability | Calculation of trust value for EuroVoc took 1.0251998901367188e-05s
INFO | --- Analysis for eurovoc took 2.0602760314941406s
Availability | SPARQL endpoint availability check for EUROVOC in SKOS took 3.8623809814453125e-05s
Availability | VoID file availability check for EUROVOC in SKOS took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for EUROVOC in SKOS took 0.1741170883178711s
Reputation | Calculation of the PageRank for EUROVOC in SKOS took 0.022472620010375977s
Interlinking | Calculation of Degree of Connection for EUROVOC in SKOS took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for EUROVOC in SKOS took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for EUROVOC in SKOS took 4.00543212890625e-05s
Believability | Calculation of trust value for EUROVOC in SKOS took 1.049041748046875e-05s
INFO | --- Analysis for eurovoc-in-skos took 1.9706695079803467s
Availability | SPARQL endpoint availability check for European Television Heritage took 8.058547973632812e-05s
Availability | VoID file availability check for European Television Heritage took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for European Television Heritage took 0.18278765678405762s
Reputation | Calculation of the PageRank for European Television Heritage took 0.02029561996459961s
Interlinking | Calculation of Degree of Connection for European Television Heritage took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Television Heritage took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for European Television Heritage took 3.075599670410156e-05s
Believability | Calculation of trust value for European Television Heritage took 1.0728836059570312e-05s
INFO | --- Analysis for euscreen took 2.038376808166504s
Availability | SPARQL endpoint availability check for Farmacias en Euskadi took 4.673004150390625e-05s
Availability | VoID file availability check for Farmacias en Euskadi took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Farmacias en Euskadi took 0.18320560455322266s
Reputation | Calculation of the PageRank for Farmacias en Euskadi took 0.020509719848632812s
Interlinking | Calculation of Degree of Connection for Farmacias en Euskadi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Farmacias en Euskadi took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Farmacias en Euskadi took 4.696846008300781e-05s
Believability | Calculation of trust value for Farmacias en Euskadi took 1.0251998901367188e-05s
INFO | --- Analysis for euskadi-farmacias took 2.0226738452911377s
Availability | SPARQL endpoint availability check for Research outputs of Eastern University Sri Lanka took 3.8623809814453125e-05s
Availability | VoID file availability check for Research outputs of Eastern University Sri Lanka took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Research outputs of Eastern University Sri Lanka took 0.18590211868286133s
Reputation | Calculation of the PageRank for Research outputs of Eastern University Sri Lanka took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for Research outputs of Eastern University Sri Lanka took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research outputs of Eastern University Sri Lanka took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Research outputs of Eastern University Sri Lanka took 3.170967102050781e-05s
Believability | Calculation of trust value for Research outputs of Eastern University Sri Lanka took 1.1682510375976562e-05s
INFO | --- Analysis for EUSL-Research-Data-Sri_Lanka took 1.9850966930389404s
Availability | SPARQL endpoint availability check for Edinburgh University Theatre Company Productions took 0.00010013580322265625s
Availability | VoID file availability check for Edinburgh University Theatre Company Productions took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for Edinburgh University Theatre Company Productions took 0.17258214950561523s
Reputation | Calculation of the PageRank for Edinburgh University Theatre Company Productions took 0.02022075653076172s
Interlinking | Calculation of Degree of Connection for Edinburgh University Theatre Company Productions took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Edinburgh University Theatre Company Productions took 0.0006997585296630859s
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 1.049041748046875e-05s
INFO | --- Analysis for eutc-productions took 2.0174036026000977s
Availability | SPARQL endpoint availability check for EventMedia took 0.34318065643310547s
Availability | VoID file availability check for EventMedia took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for EventMedia took 0.18366479873657227s
Reputation | Calculation of the PageRank for EventMedia took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for EventMedia took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for EventMedia took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for EventMedia took 0.00010514259338378906s
Believability | Calculation of trust value for EventMedia took 1.0251998901367188e-05s
INFO | --- Analysis for event-media took 2.6051182746887207s
Availability | SPARQL endpoint availability check for EventKG took 8.249282836914062e-05s
Availability | VoID file availability check for EventKG took 0.0005340576171875s
Completeness | Calculation of interlinking completeness for EventKG took 0.17530012130737305s
Reputation | Calculation of the PageRank for EventKG took 0.020485401153564453s
Interlinking | Calculation of Degree of Connection for EventKG took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for EventKG took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for EventKG took 8.20159912109375e-05s
Believability | Calculation of trust value for EventKG took 1.049041748046875e-05s
INFO | --- Analysis for eventkg took 3.3842756748199463s
Availability | SPARQL endpoint availability check for Eventseer took 4.00543212890625e-05s
Availability | VoID file availability check for Eventseer took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for Eventseer took 0.18120861053466797s
Reputation | Calculation of the PageRank for Eventseer took 0.02214956283569336s
Interlinking | Calculation of Degree of Connection for Eventseer took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Eventseer took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Eventseer took 4.887580871582031e-05s
Believability | Calculation of trust value for Eventseer took 7.3909759521484375e-06s
INFO | --- Analysis for eventseer took 2.033550977706909s
Availability | SPARQL endpoint availability check for Face Link took 3.8623809814453125e-05s
Availability | VoID file availability check for Face Link took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Face Link took 0.1755537986755371s
Reputation | Calculation of the PageRank for Face Link took 0.021564960479736328s
Interlinking | Calculation of Degree of Connection for Face Link took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Face Link took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Face Link took 3.5762786865234375e-05s
Believability | Calculation of trust value for Face Link took 1.0728836059570312e-05s
INFO | --- Analysis for Face_Link took 2.000175714492798s
Availability | SPARQL endpoint availability check for Facebook Linked Data Service took 8.225440979003906e-05s
Availability | VoID file availability check for Facebook Linked Data Service took 0.0004200935363769531s
Completeness | Calculation of interlinking completeness for Facebook Linked Data Service took 0.1781928539276123s
Reputation | Calculation of the PageRank for Facebook Linked Data Service took 0.021428585052490234s
Interlinking | Calculation of Degree of Connection for Facebook Linked Data Service took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Facebook Linked Data Service took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Facebook Linked Data Service took 3.3855438232421875e-05s
Believability | Calculation of trust value for Facebook Linked Data Service took 1.049041748046875e-05s
INFO | --- Analysis for facebook-lids took 1.9820270538330078s
Availability | SPARQL endpoint availability check for Fact Forge took 4.076957702636719e-05s
Availability | VoID file availability check for Fact Forge took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for Fact Forge took 0.18212461471557617s
Reputation | Calculation of the PageRank for Fact Forge took 0.020726919174194336s
Interlinking | Calculation of Degree of Connection for Fact Forge took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fact Forge took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Fact Forge took 3.1948089599609375e-05s
Believability | Calculation of trust value for Fact Forge took 9.5367431640625e-06s
INFO | --- Analysis for fact-forge took 1.9790117740631104s
Availability | SPARQL endpoint availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 8.344650268554688e-05s
Availability | VoID file availability check for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.1735057830810547s
Reputation | Calculation of the PageRank for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.020655155181884766s
Interlinking | Calculation of Degree of Connection for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 4.00543212890625e-05s
Believability | Calculation of trust value for Farm Accountancy Data Network (FADN) linked dataset from 2019 @PSNC took 1.0728836059570312e-05s
INFO | --- Analysis for FADN_(2019) took 2.009855270385742s
Availability | SPARQL endpoint availability check for FAMEData took 8.153915405273438e-05s
Availability | VoID file availability check for FAMEData took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for FAMEData took 0.17958426475524902s
Reputation | Calculation of the PageRank for FAMEData took 0.022089242935180664s
Interlinking | Calculation of Degree of Connection for FAMEData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAMEData took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for FAMEData took 3.361701965332031e-05s
Believability | Calculation of trust value for FAMEData took 1.1205673217773438e-05s
INFO | --- Analysis for famedata took 1.990534782409668s
Availability | SPARQL endpoint availability check for FAO geopolitical ontology took 8.463859558105469e-05s
Availability | VoID file availability check for FAO geopolitical ontology took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for FAO geopolitical ontology took 0.18106389045715332s
Reputation | Calculation of the PageRank for FAO geopolitical ontology took 0.021704673767089844s
Interlinking | Calculation of Degree of Connection for FAO geopolitical ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FAO geopolitical ontology took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for FAO geopolitical ontology took 9.894371032714844e-05s
Believability | Calculation of trust value for FAO geopolitical ontology took 1.3828277587890625e-05s
INFO | --- Analysis for fao-geopolitical-ontology took 1.9828803539276123s
Availability | SPARQL endpoint availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00010585784912109375s
Availability | VoID file availability check for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.17611050605773926s
Reputation | Calculation of the PageRank for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 9.989738464355469e-05s
Believability | Calculation of trust value for Food and Agriculture Organization of the United Nations (FAO) Linked Data took 1.3113021850585938e-05s
INFO | --- Analysis for fao-linked-data took 1.9850478172302246s
Availability | SPARQL endpoint availability check for FAO ASFIS classification of biological entities @PSNC took 0.00011682510375976562s
Availability | VoID file availability check for FAO ASFIS classification of biological entities @PSNC took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for FAO ASFIS classification of biological entities @PSNC took 0.1787881851196289s
Reputation | Calculation of the PageRank for FAO ASFIS classification of biological entities @PSNC took 0.02013373374938965s
Interlinking | Calculation of Degree of Connection for FAO ASFIS classification of biological entities @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FAO ASFIS classification of biological entities @PSNC took 0.0007383823394775391s
Interlinking | Calculation of Clustering coefficient for FAO ASFIS classification of biological entities @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for FAO ASFIS classification of biological entities @PSNC took 8.344650268554688e-06s
INFO | --- Analysis for FAO_species took 1.98311185836792s
Availability | SPARQL endpoint availability check for ChEMBL-RDF (@ Uppsala University) took 4.029273986816406e-05s
Availability | VoID file availability check for ChEMBL-RDF (@ Uppsala University) took 0.0004832744598388672s
Completeness | Calculation of interlinking completeness for ChEMBL-RDF (@ Uppsala University) took 0.181671142578125s
Reputation | Calculation of the PageRank for ChEMBL-RDF (@ Uppsala University) took 0.02146434783935547s
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.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for ChEMBL-RDF (@ Uppsala University) took 4.5299530029296875e-05s
Believability | Calculation of trust value for ChEMBL-RDF (@ Uppsala University) took 8.344650268554688e-06s
INFO | --- Analysis for farmbio-chembl took 2.021148204803467s
Availability | SPARQL endpoint availability check for Farmers Markets Geographic Data (United States) took 0.0001277923583984375s
Availability | VoID file availability check for Farmers Markets Geographic Data (United States) took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for Farmers Markets Geographic Data (United States) took 0.18378829956054688s
Reputation | Calculation of the PageRank for Farmers Markets Geographic Data (United States) took 0.020437955856323242s
Interlinking | Calculation of Degree of Connection for Farmers Markets Geographic Data (United States) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Farmers Markets Geographic Data (United States) took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Farmers Markets Geographic Data (United States) took 3.147125244140625e-05s
Believability | Calculation of trust value for Farmers Markets Geographic Data (United States) took 1.4066696166992188e-05s
INFO | --- Analysis for farmers-markets-geographic-data-united-states took 2.024221181869507s
Availability | SPARQL endpoint availability check for FarolApp Streetlight Dataset took 8.273124694824219e-05s
Availability | VoID file availability check for FarolApp Streetlight Dataset took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for FarolApp Streetlight Dataset took 0.17707347869873047s
Reputation | Calculation of the PageRank for FarolApp Streetlight Dataset took 0.020434141159057617s
Interlinking | Calculation of Degree of Connection for FarolApp Streetlight Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FarolApp Streetlight Dataset took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for FarolApp Streetlight Dataset took 3.266334533691406e-05s
Believability | Calculation of trust value for FarolApp Streetlight Dataset took 1.3828277587890625e-05s
INFO | --- Analysis for farolapp-dataset took 2.0093514919281006s
Availability | SPARQL endpoint availability check for Fatal Traffic Accidents in greek roads took 4.220008850097656e-05s
Availability | VoID file availability check for Fatal Traffic Accidents in greek roads took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Fatal Traffic Accidents in greek roads took 0.19648337364196777s
Reputation | Calculation of the PageRank for Fatal Traffic Accidents in greek roads took 0.021458864212036133s
Interlinking | Calculation of Degree of Connection for Fatal Traffic Accidents in greek roads took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Fatal Traffic Accidents in greek roads took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Fatal Traffic Accidents in greek roads took 4.744529724121094e-05s
Believability | Calculation of trust value for Fatal Traffic Accidents in greek roads took 1.0728836059570312e-05s
INFO | --- Analysis for fatal-traffic-accidents-in-greek-roads took 2.0587399005889893s
Availability | SPARQL endpoint availability check for I4.0-Onto took 4.100799560546875e-05s
Availability | VoID file availability check for I4.0-Onto took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for I4.0-Onto took 0.1849062442779541s
Reputation | Calculation of the PageRank for I4.0-Onto took 0.02048969268798828s
Interlinking | Calculation of Degree of Connection for I4.0-Onto took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for I4.0-Onto took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for I4.0-Onto took 3.266334533691406e-05s
Believability | Calculation of trust value for I4.0-Onto took 1.6927719116210938e-05s
INFO | --- Analysis for fatimazahra took 1.9899539947509766s
Availability | SPARQL endpoint availability check for Federal Reserve Economic Data RDF took 4.100799560546875e-05s
Availability | VoID file availability check for Federal Reserve Economic Data RDF took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Federal Reserve Economic Data RDF took 0.18290472030639648s
Reputation | Calculation of the PageRank for Federal Reserve Economic Data RDF took 0.020982027053833008s
Interlinking | Calculation of Degree of Connection for Federal Reserve Economic Data RDF took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Federal Reserve Economic Data RDF took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Economic Data RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for Federal Reserve Economic Data RDF took 5.0067901611328125e-06s
INFO | --- Analysis for federal-economic-rdf took 2.02693772315979s
Availability | SPARQL endpoint availability check for Feed Wrapper took 8.416175842285156e-05s
Availability | VoID file availability check for Feed Wrapper took 0.0005533695220947266s
Completeness | Calculation of interlinking completeness for Feed Wrapper took 0.18546199798583984s
Reputation | Calculation of the PageRank for Feed Wrapper took 0.02059650421142578s
Interlinking | Calculation of Degree of Connection for Feed Wrapper took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Feed Wrapper took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for Feed Wrapper took 3.170967102050781e-05s
Believability | Calculation of trust value for Feed Wrapper took 1.0728836059570312e-05s
INFO | --- Analysis for feedwrapper-lids took 2.0319998264312744s
Availability | SPARQL endpoint availability check for FHIR STU3 took 8.416175842285156e-05s
Availability | VoID file availability check for FHIR STU3 took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for FHIR STU3 took 0.1739511489868164s
Reputation | Calculation of the PageRank for FHIR STU3 took 0.02094578742980957s
Interlinking | Calculation of Degree of Connection for FHIR STU3 took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FHIR STU3 took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for FHIR STU3 took 3.266334533691406e-05s
Believability | Calculation of trust value for FHIR STU3 took 6.198883056640625e-06s
INFO | --- Analysis for FHIR_STU3 took 2.0381765365600586s
Availability | SPARQL endpoint availability check for FiESTA took 8.0108642578125e-05s
Availability | VoID file availability check for FiESTA took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for FiESTA took 0.18966436386108398s
Reputation | Calculation of the PageRank for FiESTA took 0.020978450775146484s
Interlinking | Calculation of Degree of Connection for FiESTA took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for FiESTA took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for FiESTA took 4.076957702636719e-05s
Believability | Calculation of trust value for FiESTA took 1.049041748046875e-05s
INFO | --- Analysis for fiesta took 2.0672125816345215s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.034706115722656e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.1820392608642578s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.021862506866455078s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.314018249511719e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0013580322265625e-05s
INFO | --- Analysis for file:C:UsersaDesktopurn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976.owl took 2.082540273666382s
Availability | SPARQL endpoint availability check for Finnish municipalities and regional classifications took 5.6743621826171875e-05s
Availability | VoID file availability check for Finnish municipalities and regional classifications took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Finnish municipalities and regional classifications took 0.17837071418762207s
Reputation | Calculation of the PageRank for Finnish municipalities and regional classifications took 0.020606279373168945s
Interlinking | Calculation of Degree of Connection for Finnish municipalities and regional classifications took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Finnish municipalities and regional classifications took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Finnish municipalities and regional classifications took 7.510185241699219e-05s
Believability | Calculation of trust value for Finnish municipalities and regional classifications took 1.3589859008789062e-05s
INFO | --- Analysis for finnish-municipalities took 2.0207440853118896s
Availability | SPARQL endpoint availability check for firmao took 8.654594421386719e-05s
Availability | VoID file availability check for firmao took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for firmao took 0.1885204315185547s
Reputation | Calculation of the PageRank for firmao took 0.020779132843017578s
Interlinking | Calculation of Degree of Connection for firmao took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for firmao took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for firmao took 3.3855438232421875e-05s
Believability | Calculation of trust value for firmao took 1.430511474609375e-05s
INFO | --- Analysis for firmao took 1.974717378616333s
Availability | SPARQL endpoint availability check for FISH Archaeological Objects Thesaurus took 8.416175842285156e-05s
Availability | VoID file availability check for FISH Archaeological Objects Thesaurus took 0.0010445117950439453s
Completeness | Calculation of interlinking completeness for FISH Archaeological Objects Thesaurus took 0.1867356300354004s
Reputation | Calculation of the PageRank for FISH Archaeological Objects Thesaurus took 0.020535945892333984s
Interlinking | Calculation of Degree of Connection for FISH Archaeological Objects Thesaurus took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FISH Archaeological Objects Thesaurus took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for FISH Archaeological Objects Thesaurus took 3.361701965332031e-05s
Believability | Calculation of trust value for FISH Archaeological Objects Thesaurus took 1.4066696166992188e-05s
INFO | --- Analysis for fish-archaeological-objects-thesaurus took 2.026641845703125s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset @PSNC took 4.100799560546875e-05s
Availability | VoID file availability check for Norway fishery stocks dataset @PSNC took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset @PSNC took 0.18612122535705566s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset @PSNC took 0.022708892822265625s
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.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset @PSNC took 1.33514404296875e-05s
INFO | --- Analysis for Fishery_Stock_Dataset took 2.0263564586639404s
Availability | SPARQL endpoint availability check for Fishes of Texas took 4.3392181396484375e-05s
Availability | VoID file availability check for Fishes of Texas took 0.0002658367156982422s
Completeness | Calculation of interlinking completeness for Fishes of Texas took 0.17196869850158691s
Reputation | Calculation of the PageRank for Fishes of Texas took 0.02176523208618164s
Interlinking | Calculation of Degree of Connection for Fishes of Texas took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Fishes of Texas took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Fishes of Texas took 8.797645568847656e-05s
Believability | Calculation of trust value for Fishes of Texas took 1.2874603271484375e-05s
INFO | --- Analysis for fishes-of-texas took 1.968205213546753s
Availability | SPARQL endpoint availability check for flickr? wrappr took 4.2438507080078125e-05s
Availability | VoID file availability check for flickr? wrappr took 0.00048828125s
Completeness | Calculation of interlinking completeness for flickr? wrappr took 0.172255277633667s
Reputation | Calculation of the PageRank for flickr? wrappr took 0.020580053329467773s
Interlinking | Calculation of Degree of Connection for flickr? wrappr took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for flickr? wrappr took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for flickr? wrappr took 9.465217590332031e-05s
Believability | Calculation of trust value for flickr? wrappr took 1.33514404296875e-05s
INFO | --- Analysis for flickr-wrappr took 1.987250566482544s
Availability | SPARQL endpoint availability check for flickr.person took 0.00013256072998046875s
Availability | VoID file availability check for flickr.person took 0.0004987716674804688s
Completeness | Calculation of interlinking completeness for flickr.person took 0.17819523811340332s
Reputation | Calculation of the PageRank for flickr.person took 0.021884441375732422s
Interlinking | Calculation of Degree of Connection for flickr.person took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr.person took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for flickr.person took 3.409385681152344e-05s
Believability | Calculation of trust value for flickr.person took 1.2874603271484375e-05s
INFO | --- Analysis for flickr_person took 1.9737606048583984s
Availability | SPARQL endpoint availability check for flickr.videoobject took 8.392333984375e-05s
Availability | VoID file availability check for flickr.videoobject took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for flickr.videoobject took 0.17331910133361816s
Reputation | Calculation of the PageRank for flickr.videoobject took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for flickr.videoobject took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flickr.videoobject took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for flickr.videoobject took 3.2901763916015625e-05s
Believability | Calculation of trust value for flickr.videoobject took 1.33514404296875e-05s
INFO | --- Analysis for flickr_videoobject took 2.0197196006774902s
Availability | SPARQL endpoint availability check for Future land use simulation model took 4.1484832763671875e-05s
Availability | VoID file availability check for Future land use simulation model took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for Future land use simulation model took 0.18663597106933594s
Reputation | Calculation of the PageRank for Future land use simulation model took 0.020403623580932617s
Interlinking | Calculation of Degree of Connection for Future land use simulation model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Future land use simulation model took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for Future land use simulation model took 3.719329833984375e-05s
Believability | Calculation of trust value for Future land use simulation model took 1.2874603271484375e-05s
INFO | --- Analysis for FLUS took 2.005669116973877s
Availability | SPARQL endpoint availability check for Fly-TED took 4.0531158447265625e-05s
Availability | VoID file availability check for Fly-TED took 0.00036835670471191406s
Completeness | Calculation of interlinking completeness for Fly-TED took 0.18526840209960938s
Reputation | Calculation of the PageRank for Fly-TED took 0.02249598503112793s
Interlinking | Calculation of Degree of Connection for Fly-TED took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fly-TED took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Fly-TED took 3.075599670410156e-05s
Believability | Calculation of trust value for Fly-TED took 9.775161743164062e-06s
INFO | --- Analysis for fly-ted took 2.022104024887085s
Availability | SPARQL endpoint availability check for FlyAtlas took 8.726119995117188e-05s
Availability | VoID file availability check for FlyAtlas took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for FlyAtlas took 0.1825263500213623s
Reputation | Calculation of the PageRank for FlyAtlas took 0.02166581153869629s
Interlinking | Calculation of Degree of Connection for FlyAtlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for FlyAtlas took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for FlyAtlas took 3.0517578125e-05s
Believability | Calculation of trust value for FlyAtlas took 9.775161743164062e-06s
INFO | --- Analysis for flyatlas took 2.002098560333252s
Availability | SPARQL endpoint availability check for Flybase took 3.910064697265625e-05s
Availability | VoID file availability check for Flybase took 0.00042819976806640625s
Completeness | Calculation of interlinking completeness for Flybase took 0.16944122314453125s
Reputation | Calculation of the PageRank for Flybase took 0.020292043685913086s
Interlinking | Calculation of Degree of Connection for Flybase took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Flybase took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Flybase took 3.552436828613281e-05s
Believability | Calculation of trust value for Flybase took 1.049041748046875e-05s
INFO | --- Analysis for flybase took 1.9524574279785156s
Availability | SPARQL endpoint availability check for Flyted took 4.2438507080078125e-05s
Availability | VoID file availability check for Flyted took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for Flyted took 0.18430352210998535s
Reputation | Calculation of the PageRank for Flyted took 0.021691560745239258s
Interlinking | Calculation of Degree of Connection for Flyted took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Flyted took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Flyted took 3.147125244140625e-05s
Believability | Calculation of trust value for Flyted took 1.049041748046875e-05s
INFO | --- Analysis for flyted took 1.9492881298065186s
Availability | SPARQL endpoint availability check for Foodista took 4.100799560546875e-05s
Availability | VoID file availability check for Foodista took 0.0002071857452392578s
Completeness | Calculation of interlinking completeness for Foodista took 0.1799468994140625s
Reputation | Calculation of the PageRank for Foodista took 0.020387887954711914s
Interlinking | Calculation of Degree of Connection for Foodista took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Foodista took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Foodista took 2.956390380859375e-05s
Believability | Calculation of trust value for Foodista took 5.245208740234375e-06s
INFO | --- Analysis for foodista took 1.9370694160461426s
Availability | SPARQL endpoint availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 4.0531158447265625e-05s
Availability | VoID file availability check for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.17903661727905273s
Reputation | Calculation of the PageRank for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 0.020315170288085938s
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.000698089599609375s
Interlinking | Calculation of Clustering coefficient for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 7.033348083496094e-05s
Believability | Calculation of trust value for FOODpedia - Linked Data Dataset about Food Products and Ingredients took 6.4373016357421875e-06s
INFO | --- Analysis for foodpedia took 1.9888176918029785s
Availability | SPARQL endpoint availability check for FORGE Course information took 8.368492126464844e-05s
Availability | VoID file availability check for FORGE Course information took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for FORGE Course information took 0.1751861572265625s
Reputation | Calculation of the PageRank for FORGE Course information took 0.0224916934967041s
Interlinking | Calculation of Degree of Connection for FORGE Course information took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FORGE Course information took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for FORGE Course information took 3.2901763916015625e-05s
Believability | Calculation of trust value for FORGE Course information took 1.3828277587890625e-05s
INFO | --- Analysis for forge-course-information took 1.964489221572876s
Availability | SPARQL endpoint availability check for FrameBase schema took 4.2438507080078125e-05s
Availability | VoID file availability check for FrameBase schema took 0.0004942417144775391s
Completeness | Calculation of interlinking completeness for FrameBase schema took 0.1683967113494873s
Reputation | Calculation of the PageRank for FrameBase schema took 0.0203704833984375s
Interlinking | Calculation of Degree of Connection for FrameBase schema took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for FrameBase schema took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for FrameBase schema took 4.7206878662109375e-05s
Believability | Calculation of trust value for FrameBase schema took 1.3589859008789062e-05s
INFO | --- Analysis for framebase-schema took 2.0051026344299316s
Availability | SPARQL endpoint availability check for FrameNet took 8.392333984375e-05s
Availability | VoID file availability check for FrameNet took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for FrameNet took 0.18174457550048828s
Reputation | Calculation of the PageRank for FrameNet took 0.020603179931640625s
Interlinking | Calculation of Degree of Connection for FrameNet took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for FrameNet took 0.0007445812225341797s
Interlinking | Calculation of Clustering coefficient for FrameNet took 3.337860107421875e-05s
Believability | Calculation of trust value for FrameNet took 1.2636184692382812e-05s
INFO | --- Analysis for framenet took 2.0042569637298584s
Availability | SPARQL endpoint availability check for Framester took 8.082389831542969e-05s
Availability | VoID file availability check for Framester took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Framester took 0.17819595336914062s
Reputation | Calculation of the PageRank for Framester took 0.020268917083740234s
Interlinking | Calculation of Degree of Connection for Framester took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Framester took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Framester took 7.319450378417969e-05s
Believability | Calculation of trust value for Framester took 1.0251998901367188e-05s
INFO | --- Analysis for framester took 1.9391136169433594s
Availability | SPARQL endpoint availability check for Federal Reserve Board (FRB) Linked Data took 6.890296936035156e-05s
Availability | VoID file availability check for Federal Reserve Board (FRB) Linked Data took 0.0002732276916503906s
Completeness | Calculation of interlinking completeness for Federal Reserve Board (FRB) Linked Data took 0.16681575775146484s
Reputation | Calculation of the PageRank for Federal Reserve Board (FRB) Linked Data took 0.020270824432373047s
Interlinking | Calculation of Degree of Connection for Federal Reserve Board (FRB) Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Federal Reserve Board (FRB) Linked Data took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Federal Reserve Board (FRB) Linked Data took 8.511543273925781e-05s
Believability | Calculation of trust value for Federal Reserve Board (FRB) Linked Data took 5.0067901611328125e-06s
INFO | --- Analysis for frb-linked-data took 1.9187657833099365s
Availability | SPARQL endpoint availability check for Freebase took 3.814697265625e-05s
Availability | VoID file availability check for Freebase took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Freebase took 0.1746361255645752s
Reputation | Calculation of the PageRank for Freebase took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for Freebase took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Freebase took 0.0007617473602294922s
Interlinking | Calculation of Clustering coefficient for Freebase took 0.00027251243591308594s
Believability | Calculation of trust value for Freebase took 4.76837158203125e-06s
INFO | --- Analysis for freebase took 1.9219157695770264s
Availability | SPARQL endpoint availability check for Freeyork took 4.00543212890625e-05s
Availability | VoID file availability check for Freeyork took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for Freeyork took 0.1808607578277588s
Reputation | Calculation of the PageRank for Freeyork took 0.020428895950317383s
Interlinking | Calculation of Degree of Connection for Freeyork took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Freeyork took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Freeyork took 0.00010228157043457031s
Believability | Calculation of trust value for Freeyork took 5.245208740234375e-06s
INFO | --- Analysis for freeyork-org took 1.9278323650360107s
Availability | SPARQL endpoint availability check for French School Program took 4.696846008300781e-05s
Availability | VoID file availability check for French School Program took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for French School Program took 0.17769289016723633s
Reputation | Calculation of the PageRank for French School Program took 0.020229101181030273s
Interlinking | Calculation of Degree of Connection for French School Program took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for French School Program took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for French School Program took 3.075599670410156e-05s
Believability | Calculation of trust value for French School Program took 6.9141387939453125e-06s
INFO | --- Analysis for french-school-program took 1.9464778900146484s
Availability | SPARQL endpoint availability check for French School System took 4.0531158447265625e-05s
Availability | VoID file availability check for French School System took 0.0002052783966064453s
Completeness | Calculation of interlinking completeness for French School System took 0.17900538444519043s
Reputation | Calculation of the PageRank for French School System took 0.020545482635498047s
Interlinking | Calculation of Degree of Connection for French School System took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for French School System took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for French School System took 2.956390380859375e-05s
Believability | Calculation of trust value for French School System took 5.0067901611328125e-06s
INFO | --- Analysis for french-school-system took 1.9530954360961914s
Availability | SPARQL endpoint availability check for French TimeBank took 4.00543212890625e-05s
Availability | VoID file availability check for French TimeBank took 0.00023865699768066406s
Completeness | Calculation of interlinking completeness for French TimeBank took 0.17804479598999023s
Reputation | Calculation of the PageRank for French TimeBank took 0.020502805709838867s
Interlinking | Calculation of Degree of Connection for French TimeBank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for French TimeBank took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for French TimeBank took 3.0040740966796875e-05s
Believability | Calculation of trust value for French TimeBank took 5.9604644775390625e-06s
INFO | --- Analysis for french-timebank took 1.942106008529663s
Availability | SPARQL endpoint availability check for Community Research and Development Information Service (CORDIS) took 3.9577484130859375e-05s
Availability | VoID file availability check for Community Research and Development Information Service (CORDIS) took 0.0002067089080810547s
Completeness | Calculation of interlinking completeness for Community Research and Development Information Service (CORDIS) took 0.17637038230895996s
Reputation | Calculation of the PageRank for Community Research and Development Information Service (CORDIS) took 0.020159244537353516s
Interlinking | Calculation of Degree of Connection for Community Research and Development Information Service (CORDIS) took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Community Research and Development Information Service (CORDIS) took 0.0007627010345458984s
Interlinking | Calculation of Clustering coefficient for Community Research and Development Information Service (CORDIS) took 7.700920104980469e-05s
Believability | Calculation of trust value for Community Research and Development Information Service (CORDIS) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-cordis took 1.9623222351074219s
Availability | SPARQL endpoint availability check for DailyMed took 4.100799560546875e-05s
Availability | VoID file availability check for DailyMed took 0.0002048015594482422s
Completeness | Calculation of interlinking completeness for DailyMed took 0.17590832710266113s
Reputation | Calculation of the PageRank for DailyMed took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for DailyMed took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DailyMed took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for DailyMed took 9.942054748535156e-05s
Believability | Calculation of trust value for DailyMed took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-dailymed took 1.976435899734497s
Availability | SPARQL endpoint availability check for DBLP Bibliography Database in RDF (FU Berlin) took 3.814697265625e-05s
Availability | VoID file availability check for DBLP Bibliography Database in RDF (FU Berlin) took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for DBLP Bibliography Database in RDF (FU Berlin) took 0.16364383697509766s
Reputation | Calculation of the PageRank for DBLP Bibliography Database in RDF (FU Berlin) took 0.020285606384277344s
Interlinking | Calculation of Degree of Connection for DBLP Bibliography Database in RDF (FU Berlin) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for DBLP Bibliography Database in RDF (FU Berlin) took 0.0006899833679199219s
Interlinking | Calculation of Clustering coefficient for DBLP Bibliography Database in RDF (FU Berlin) took 8.726119995117188e-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 1.9071836471557617s
Availability | SPARQL endpoint availability check for Diseasome took 3.933906555175781e-05s
Availability | VoID file availability check for Diseasome took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for Diseasome took 0.16808390617370605s
Reputation | Calculation of the PageRank for Diseasome took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for Diseasome took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Diseasome took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Diseasome took 0.00010418891906738281s
Believability | Calculation of trust value for Diseasome took 6.67572021484375e-06s
INFO | --- Analysis for fu-berlin-diseasome took 1.8954732418060303s
Availability | SPARQL endpoint availability check for DrugBank took 5.221366882324219e-05s
Availability | VoID file availability check for DrugBank took 0.00023698806762695312s
Completeness | Calculation of interlinking completeness for DrugBank took 0.2193751335144043s
Reputation | Calculation of the PageRank for DrugBank took 0.020393848419189453s
Interlinking | Calculation of Degree of Connection for DrugBank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for DrugBank took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for DrugBank took 0.00011777877807617188s
Believability | Calculation of trust value for DrugBank took 6.9141387939453125e-06s
INFO | --- Analysis for fu-berlin-drugbank took 1.996859073638916s
Availability | SPARQL endpoint availability check for European Commission Competition data set (FU Berlin) took 3.814697265625e-05s
Availability | VoID file availability check for European Commission Competition data set (FU Berlin) took 0.00020313262939453125s
Completeness | Calculation of interlinking completeness for European Commission Competition data set (FU Berlin) took 0.17318058013916016s
Reputation | Calculation of the PageRank for European Commission Competition data set (FU Berlin) took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for European Commission Competition data set (FU Berlin) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for European Commission Competition data set (FU Berlin) took 0.0006895065307617188s
Interlinking | Calculation of Clustering coefficient for European Commission Competition data set (FU Berlin) took 2.7894973754882812e-05s
Believability | Calculation of trust value for European Commission Competition data set (FU Berlin) took 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-ec-competition took 1.9443631172180176s
Availability | SPARQL endpoint availability check for EURAXESS - Researchers in Motion took 3.910064697265625e-05s
Availability | VoID file availability check for EURAXESS - Researchers in Motion took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for EURAXESS - Researchers in Motion took 0.18496227264404297s
Reputation | Calculation of the PageRank for EURAXESS - Researchers in Motion took 0.020110607147216797s
Interlinking | Calculation of Degree of Connection for EURAXESS - Researchers in Motion took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for EURAXESS - Researchers in Motion took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for EURAXESS - Researchers in Motion took 7.224082946777344e-05s
Believability | Calculation of trust value for EURAXESS - Researchers in Motion took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-euraxess took 1.945239543914795s
Availability | SPARQL endpoint availability check for European Employment Services (EURES) took 3.886222839355469e-05s
Availability | VoID file availability check for European Employment Services (EURES) took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for European Employment Services (EURES) took 0.17448019981384277s
Reputation | Calculation of the PageRank for European Employment Services (EURES) took 0.02013111114501953s
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.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for European Employment Services (EURES) took 7.05718994140625e-05s
Believability | Calculation of trust value for European Employment Services (EURES) took 5.0067901611328125e-06s
INFO | --- Analysis for fu-berlin-eures took 1.9207546710968018s
Availability | SPARQL endpoint availability check for Eurostat in RDF (FU Berlin) took 3.7670135498046875e-05s
Availability | VoID file availability check for Eurostat in RDF (FU Berlin) took 0.00020432472229003906s
Completeness | Calculation of interlinking completeness for Eurostat in RDF (FU Berlin) took 0.16987967491149902s
Reputation | Calculation of the PageRank for Eurostat in RDF (FU Berlin) took 0.02008819580078125s
Interlinking | Calculation of Degree of Connection for Eurostat in RDF (FU Berlin) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Eurostat in RDF (FU Berlin) took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Eurostat in RDF (FU Berlin) took 9.274482727050781e-05s
Believability | Calculation of trust value for Eurostat in RDF (FU Berlin) took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-eurostat took 1.94533371925354s
Availability | SPARQL endpoint availability check for MediCare took 3.9577484130859375e-05s
Availability | VoID file availability check for MediCare took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for MediCare took 0.1800825595855713s
Reputation | Calculation of the PageRank for MediCare took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for MediCare took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MediCare took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for MediCare took 3.886222839355469e-05s
Believability | Calculation of trust value for MediCare took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-medicare took 1.9144651889801025s
Availability | SPARQL endpoint availability check for Project Gutenberg in RDF (FU Berlin) took 3.910064697265625e-05s
Availability | VoID file availability check for Project Gutenberg in RDF (FU Berlin) took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for Project Gutenberg in RDF (FU Berlin) took 0.17797398567199707s
Reputation | Calculation of the PageRank for Project Gutenberg in RDF (FU Berlin) took 0.02033376693725586s
Interlinking | Calculation of Degree of Connection for Project Gutenberg in RDF (FU Berlin) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Project Gutenberg in RDF (FU Berlin) took 0.0006906986236572266s
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 6.198883056640625e-06s
INFO | --- Analysis for fu-berlin-project-gutenberg took 1.9182722568511963s
Availability | SPARQL endpoint availability check for SIDER: Side Effect Resource took 3.838539123535156e-05s
Availability | VoID file availability check for SIDER: Side Effect Resource took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for SIDER: Side Effect Resource took 0.1758713722229004s
Reputation | Calculation of the PageRank for SIDER: Side Effect Resource took 0.020069599151611328s
Interlinking | Calculation of Degree of Connection for SIDER: Side Effect Resource took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SIDER: Side Effect Resource took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for SIDER: Side Effect Resource took 8.749961853027344e-05s
Believability | Calculation of trust value for SIDER: Side Effect Resource took 5.245208740234375e-06s
INFO | --- Analysis for fu-berlin-sider took 1.9417858123779297s
Availability | SPARQL endpoint availability check for STITCH: Chemical-Protein Interactions took 3.910064697265625e-05s
Availability | VoID file availability check for STITCH: Chemical-Protein Interactions took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for STITCH: Chemical-Protein Interactions took 0.1718463897705078s
Reputation | Calculation of the PageRank for STITCH: Chemical-Protein Interactions took 0.020198583602905273s
Interlinking | Calculation of Degree of Connection for STITCH: Chemical-Protein Interactions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for STITCH: Chemical-Protein Interactions took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for STITCH: Chemical-Protein Interactions took 7.05718994140625e-05s
Believability | Calculation of trust value for STITCH: Chemical-Protein Interactions took 5.4836273193359375e-06s
INFO | --- Analysis for fu-berlin-stitch took 1.9199960231781006s
Availability | SPARQL endpoint availability check for fvdb took 3.933906555175781e-05s
Availability | VoID file availability check for fvdb took 0.0005748271942138672s
Completeness | Calculation of interlinking completeness for fvdb took 0.1826779842376709s
Reputation | Calculation of the PageRank for fvdb took 0.020536184310913086s
Interlinking | Calculation of Degree of Connection for fvdb took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for fvdb took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for fvdb took 3.0994415283203125e-05s
Believability | Calculation of trust value for fvdb took 1.049041748046875e-05s
INFO | --- Analysis for fv took 1.974940299987793s
Availability | SPARQL endpoint availability check for Global Agricultural Concept Space took 4.291534423828125e-05s
Availability | VoID file availability check for Global Agricultural Concept Space took 0.00020575523376464844s
Completeness | Calculation of interlinking completeness for Global Agricultural Concept Space took 0.1793348789215088s
Reputation | Calculation of the PageRank for Global Agricultural Concept Space took 0.021694183349609375s
Interlinking | Calculation of Degree of Connection for Global Agricultural Concept Space took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for Global Agricultural Concept Space took 0.0007464885711669922s
Interlinking | Calculation of Clustering coefficient for Global Agricultural Concept Space took 3.3855438232421875e-05s
Believability | Calculation of trust value for Global Agricultural Concept Space took 5.4836273193359375e-06s
INFO | --- Analysis for GACS took 1.9802355766296387s
Availability | SPARQL endpoint availability check for Galen from co-ode.org took 8.249282836914062e-05s
Availability | VoID file availability check for Galen from co-ode.org took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Galen from co-ode.org took 0.17737722396850586s
Reputation | Calculation of the PageRank for Galen from co-ode.org took 0.020613908767700195s
Interlinking | Calculation of Degree of Connection for Galen from co-ode.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Galen from co-ode.org took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Galen from co-ode.org took 3.170967102050781e-05s
Believability | Calculation of trust value for Galen from co-ode.org took 1.239776611328125e-05s
INFO | --- Analysis for galen_from_co-odeorg took 1.9935214519500732s
Availability | SPARQL endpoint availability check for Galician EuroWordNet-lemon lexicon (3.0) took 8.249282836914062e-05s
Availability | VoID file availability check for Galician EuroWordNet-lemon lexicon (3.0) took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Galician EuroWordNet-lemon lexicon (3.0) took 0.1800518035888672s
Reputation | Calculation of the PageRank for Galician EuroWordNet-lemon lexicon (3.0) took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for Galician EuroWordNet-lemon lexicon (3.0) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Galician EuroWordNet-lemon lexicon (3.0) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Galician EuroWordNet-lemon lexicon (3.0) took 4.291534423828125e-05s
Believability | Calculation of trust value for Galician EuroWordNet-lemon lexicon (3.0) took 8.106231689453125e-06s
INFO | --- Analysis for galician-eurowordnet-lemon-lexicon-3-0 took 1.9837586879730225s
Availability | SPARQL endpoint availability check for Garnica Plywood Catalogue took 7.82012939453125e-05s
Availability | VoID file availability check for Garnica Plywood Catalogue took 0.0004184246063232422s
Completeness | Calculation of interlinking completeness for Garnica Plywood Catalogue took 0.17409372329711914s
Reputation | Calculation of the PageRank for Garnica Plywood Catalogue took 0.020225048065185547s
Interlinking | Calculation of Degree of Connection for Garnica Plywood Catalogue took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Garnica Plywood Catalogue took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Garnica Plywood Catalogue took 9.465217590332031e-05s
Believability | Calculation of trust value for Garnica Plywood Catalogue took 6.67572021484375e-06s
INFO | --- Analysis for garnicaplywood took 1.933746337890625s
Availability | SPARQL endpoint availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 4.076957702636719e-05s
Availability | VoID file availability check for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.18822813034057617s
Reputation | Calculation of the PageRank for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.020676851272583008s
Interlinking | Calculation of Degree of Connection for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 9.465217590332031e-05s
Believability | Calculation of trust value for Gemeenschappelijke Thesaurus Audiovisuele Archieven ? Common Thesaurus Audiovisual Archives took 1.1444091796875e-05s
INFO | --- Analysis for gemeenschappelijke-thesaurus-audiovisuele-archieven took 1.9842989444732666s
Availability | SPARQL endpoint availability check for GEneral Multilingual Environmental Thesaurus took 4.00543212890625e-05s
Availability | VoID file availability check for GEneral Multilingual Environmental Thesaurus took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for GEneral Multilingual Environmental Thesaurus took 0.17310333251953125s
Reputation | Calculation of the PageRank for GEneral Multilingual Environmental Thesaurus took 0.020782947540283203s
Interlinking | Calculation of Degree of Connection for GEneral Multilingual Environmental Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GEneral Multilingual Environmental Thesaurus took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for GEneral Multilingual Environmental Thesaurus took 9.059906005859375e-05s
Believability | Calculation of trust value for GEneral Multilingual Environmental Thesaurus took 1.1920928955078125e-05s
INFO | --- Analysis for gemet took 1.9812800884246826s
Availability | SPARQL endpoint availability check for gemet-annotated took 7.343292236328125e-05s
Availability | VoID file availability check for gemet-annotated took 0.0005140304565429688s
Completeness | Calculation of interlinking completeness for gemet-annotated took 0.17624449729919434s
Reputation | Calculation of the PageRank for gemet-annotated took 0.020363807678222656s
Interlinking | Calculation of Degree of Connection for gemet-annotated took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for gemet-annotated took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for gemet-annotated took 3.838539123535156e-05s
Believability | Calculation of trust value for gemet-annotated took 8.344650268554688e-06s
INFO | --- Analysis for gemet-annotated took 2.1591718196868896s
Availability | SPARQL endpoint availability check for Gene Expression Atlas RDF took 4.100799560546875e-05s
Availability | VoID file availability check for Gene Expression Atlas RDF took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Gene Expression Atlas RDF took 0.18130707740783691s
Reputation | Calculation of the PageRank for Gene Expression Atlas RDF took 0.020409584045410156s
Interlinking | Calculation of Degree of Connection for Gene Expression Atlas RDF took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Gene Expression Atlas RDF took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Gene Expression Atlas RDF took 4.00543212890625e-05s
Believability | Calculation of trust value for Gene Expression Atlas RDF took 1.3113021850585938e-05s
INFO | --- Analysis for gene-expression-atlas-rdf took 1.972846269607544s
Availability | SPARQL endpoint availability check for Super Ontology took 8.249282836914062e-05s
Availability | VoID file availability check for Super Ontology took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.18082284927368164s
Reputation | Calculation of the PageRank for Super Ontology took 0.021863222122192383s
Interlinking | Calculation of Degree of Connection for Super Ontology took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Super Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 3.266334533691406e-05s
Believability | Calculation of trust value for Super Ontology took 1.33514404296875e-05s
INFO | --- Analysis for Generalized_Super_Ontology took 1.9817471504211426s
Availability | SPARQL endpoint availability check for geo.place took 8.106231689453125e-05s
Availability | VoID file availability check for geo.place took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for geo.place took 0.18370914459228516s
Reputation | Calculation of the PageRank for geo.place took 0.020524978637695312s
Interlinking | Calculation of Degree of Connection for geo.place took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for geo.place took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for geo.place took 5.9604644775390625e-05s
Believability | Calculation of trust value for geo.place took 7.3909759521484375e-06s
INFO | --- Analysis for geo_place took 2.037123441696167s
Availability | SPARQL endpoint availability check for Geographic detector model took 4.1484832763671875e-05s
Availability | VoID file availability check for Geographic detector model took 0.0009412765502929688s
Completeness | Calculation of interlinking completeness for Geographic detector model took 0.1828162670135498s
Reputation | Calculation of the PageRank for Geographic detector model took 0.0211789608001709s
Interlinking | Calculation of Degree of Connection for Geographic detector model took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Geographic detector model took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Geographic detector model took 3.218650817871094e-05s
Believability | Calculation of trust value for Geographic detector model took 1.5735626220703125e-05s
INFO | --- Analysis for GeoDetector took 2.020141363143921s
Availability | SPARQL endpoint availability check for geodomainwn took 8.0108642578125e-05s
Availability | VoID file availability check for geodomainwn took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for geodomainwn took 0.18415164947509766s
Reputation | Calculation of the PageRank for geodomainwn took 0.02051711082458496s
Interlinking | Calculation of Degree of Connection for geodomainwn took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for geodomainwn took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for geodomainwn took 4.5299530029296875e-05s
Believability | Calculation of trust value for geodomainwn took 1.049041748046875e-05s
INFO | --- Analysis for geodomainwn took 1.993476152420044s
Availability | SPARQL endpoint availability check for GeoEcuador took 8.296966552734375e-05s
Availability | VoID file availability check for GeoEcuador took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for GeoEcuador took 0.18540668487548828s
Reputation | Calculation of the PageRank for GeoEcuador took 0.02207636833190918s
Interlinking | Calculation of Degree of Connection for GeoEcuador took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for GeoEcuador took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for GeoEcuador took 6.890296936035156e-05s
Believability | Calculation of trust value for GeoEcuador took 1.1920928955078125e-05s
INFO | --- Analysis for geoecuador took 1.9667487144470215s
Availability | SPARQL endpoint availability check for Geographic Names Information System (GNIS) took 3.2419450283050537s
Availability | VoID file availability check for Geographic Names Information System (GNIS) took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Geographic Names Information System (GNIS) took 0.1843268871307373s
Reputation | Calculation of the PageRank for Geographic Names Information System (GNIS) took 0.020106077194213867s
Interlinking | Calculation of Degree of Connection for Geographic Names Information System (GNIS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Geographic Names Information System (GNIS) took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Geographic Names Information System (GNIS) took 6.270408630371094e-05s
Believability | Calculation of trust value for Geographic Names Information System (GNIS) took 1.0251998901367188e-05s
INFO | --- Analysis for geographic-names-information-system-gnis took 6.7327210903167725s
Availability | SPARQL endpoint availability check for OpenUpLabs Geographic took 8.893013000488281e-05s
Availability | VoID file availability check for OpenUpLabs Geographic took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for OpenUpLabs Geographic took 0.18208813667297363s
Reputation | Calculation of the PageRank for OpenUpLabs Geographic took 0.020934581756591797s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Geographic took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Geographic took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Geographic took 3.337860107421875e-05s
Believability | Calculation of trust value for OpenUpLabs Geographic took 1.3113021850585938e-05s
INFO | --- Analysis for geographic-openuplabs took 2.0154483318328857s
Availability | SPARQL endpoint availability check for GeoLinkedData took 4.220008850097656e-05s
Availability | VoID file availability check for GeoLinkedData took 0.0005271434783935547s
Completeness | Calculation of interlinking completeness for GeoLinkedData took 0.17698407173156738s
Reputation | Calculation of the PageRank for GeoLinkedData took 0.020420074462890625s
Interlinking | Calculation of Degree of Connection for GeoLinkedData took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoLinkedData took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for GeoLinkedData took 0.00010991096496582031s
Believability | Calculation of trust value for GeoLinkedData took 1.3828277587890625e-05s
INFO | --- Analysis for geolinkeddata took 2.021068572998047s
Availability | SPARQL endpoint availability check for Geological Survey of Austria (GBA) - Thesaurus took 8.320808410644531e-05s
Availability | VoID file availability check for Geological Survey of Austria (GBA) - Thesaurus took 0.0009026527404785156s
Completeness | Calculation of interlinking completeness for Geological Survey of Austria (GBA) - Thesaurus took 0.1797046661376953s
Reputation | Calculation of the PageRank for Geological Survey of Austria (GBA) - Thesaurus took 0.021326065063476562s
Interlinking | Calculation of Degree of Connection for Geological Survey of Austria (GBA) - Thesaurus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geological Survey of Austria (GBA) - Thesaurus took 0.000736236572265625s
Interlinking | Calculation of Clustering coefficient for Geological Survey of Austria (GBA) - Thesaurus took 8.20159912109375e-05s
Believability | Calculation of trust value for Geological Survey of Austria (GBA) - Thesaurus took 1.3828277587890625e-05s
INFO | --- Analysis for geological-survey-of-austria-thesaurus took 1.9852864742279053s
Availability | SPARQL endpoint availability check for GeoNames Semantic Web took 8.416175842285156e-05s
Availability | VoID file availability check for GeoNames Semantic Web took 0.0005521774291992188s
Completeness | Calculation of interlinking completeness for GeoNames Semantic Web took 0.17107582092285156s
Reputation | Calculation of the PageRank for GeoNames Semantic Web took 0.02166748046875s
Interlinking | Calculation of Degree of Connection for GeoNames Semantic Web took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for GeoNames Semantic Web took 0.0010228157043457031s
Interlinking | Calculation of Clustering coefficient for GeoNames Semantic Web took 0.0005342960357666016s
Believability | Calculation of trust value for GeoNames Semantic Web took 1.2636184692382812e-05s
INFO | --- Analysis for geonames-semantic-web took 1.9441108703613281s
Availability | SPARQL endpoint availability check for Geospatial World  took 4.100799560546875e-05s
Availability | VoID file availability check for Geospatial World  took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Geospatial World  took 0.18266057968139648s
Reputation | Calculation of the PageRank for Geospatial World  took 0.020917177200317383s
Interlinking | Calculation of Degree of Connection for Geospatial World  took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Geospatial World  took 0.0009403228759765625s
Interlinking | Calculation of Clustering coefficient for Geospatial World  took 0.00012612342834472656s
Believability | Calculation of trust value for Geospatial World  took 1.2874603271484375e-05s
INFO | --- Analysis for geospatialworld-net took 1.9594471454620361s
Availability | SPARQL endpoint availability check for GeoSpecies Knowledge Base took 8.106231689453125e-05s
Availability | VoID file availability check for GeoSpecies Knowledge Base took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for GeoSpecies Knowledge Base took 0.18746137619018555s
Reputation | Calculation of the PageRank for GeoSpecies Knowledge Base took 0.022364139556884766s
Interlinking | Calculation of Degree of Connection for GeoSpecies Knowledge Base took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for GeoSpecies Knowledge Base took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for GeoSpecies Knowledge Base took 0.00013685226440429688s
Believability | Calculation of trust value for GeoSpecies Knowledge Base took 1.4781951904296875e-05s
INFO | --- Analysis for geospecies took 1.9868800640106201s
Availability | SPARQL endpoint availability check for GeoWordNet took 7.939338684082031e-05s
Availability | VoID file availability check for GeoWordNet took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for GeoWordNet took 0.18127846717834473s
Reputation | Calculation of the PageRank for GeoWordNet took 0.020112276077270508s
Interlinking | Calculation of Degree of Connection for GeoWordNet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for GeoWordNet took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for GeoWordNet took 4.8160552978515625e-05s
Believability | Calculation of trust value for GeoWordNet took 1.0967254638671875e-05s
INFO | --- Analysis for geowordnet took 1.9699430465698242s
Availability | SPARQL endpoint availability check for German labor law thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for German labor law thesaurus took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for German labor law thesaurus took 0.17776012420654297s
Reputation | Calculation of the PageRank for German labor law thesaurus took 0.02010035514831543s
Interlinking | Calculation of Degree of Connection for German labor law thesaurus took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for German labor law thesaurus took 0.0007340908050537109s
Interlinking | Calculation of Clustering coefficient for German labor law thesaurus took 7.772445678710938e-05s
Believability | Calculation of trust value for German labor law thesaurus took 1.2636184692382812e-05s
INFO | --- Analysis for german-labor-law-thesaurus took 1.9695665836334229s
Availability | SPARQL endpoint availability check for Linked Old Germanic Dictionaries took 8.153915405273438e-05s
Availability | VoID file availability check for Linked Old Germanic Dictionaries took 0.000431060791015625s
Completeness | Calculation of interlinking completeness for Linked Old Germanic Dictionaries took 0.18715953826904297s
Reputation | Calculation of the PageRank for Linked Old Germanic Dictionaries took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for Linked Old Germanic Dictionaries took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Old Germanic Dictionaries took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Linked Old Germanic Dictionaries took 4.0531158447265625e-05s
Believability | Calculation of trust value for Linked Old Germanic Dictionaries took 1.049041748046875e-05s
INFO | --- Analysis for germlex took 2.035325288772583s
Availability | SPARQL endpoint availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 8.130073547363281e-05s
Availability | VoID file availability check for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.17809391021728516s
Reputation | Calculation of the PageRank for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.034374237060546875s
Interlinking | Calculation of Degree of Connection for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.9788742065429688e-05s
Interlinking | Calculation of Centrality for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.0018749237060546875s
Interlinking | Calculation of Clustering coefficient for TheSoz Thesaurus for the Social Sciences (GESIS) took 0.00019598007202148438s
Believability | Calculation of trust value for TheSoz Thesaurus for the Social Sciences (GESIS) took 1.1444091796875e-05s
INFO | --- Analysis for gesis-thesoz took 2.024445056915283s
Availability | SPARQL endpoint availability check for Art & Architecture Thesaurus took 2.870978832244873s
Availability | VoID file availability check for Art & Architecture Thesaurus took 0.0002262592315673828s
Completeness | Calculation of interlinking completeness for Art & Architecture Thesaurus took 0.18869781494140625s
Reputation | Calculation of the PageRank for Art & Architecture Thesaurus took 0.022137880325317383s
Interlinking | Calculation of Degree of Connection for Art & Architecture Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Art & Architecture Thesaurus took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for Art & Architecture Thesaurus took 7.033348083496094e-05s
Believability | Calculation of trust value for Art & Architecture Thesaurus took 9.298324584960938e-06s
INFO | --- Analysis for getty-aat took 7.612590551376343s
Availability | SPARQL endpoint availability check for The Getty Thesaurus of Geographic Names took 1.3721497058868408s
Availability | VoID file availability check for The Getty Thesaurus of Geographic Names took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for The Getty Thesaurus of Geographic Names took 0.1713850498199463s
Reputation | Calculation of the PageRank for The Getty Thesaurus of Geographic Names took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for The Getty Thesaurus of Geographic Names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Getty Thesaurus of Geographic Names took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for The Getty Thesaurus of Geographic Names took 4.982948303222656e-05s
Believability | Calculation of trust value for The Getty Thesaurus of Geographic Names took 1.2159347534179688e-05s
INFO | --- Analysis for getty-tgn took 5.133097887039185s
Availability | SPARQL endpoint availability check for Gipuzkoa Demografia took 8.535385131835938e-05s
Availability | VoID file availability check for Gipuzkoa Demografia took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Gipuzkoa Demografia took 0.18107223510742188s
Reputation | Calculation of the PageRank for Gipuzkoa Demografia took 0.02019810676574707s
Interlinking | Calculation of Degree of Connection for Gipuzkoa Demografia took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Gipuzkoa Demografia took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Gipuzkoa Demografia took 2.86102294921875e-05s
Believability | Calculation of trust value for Gipuzkoa Demografia took 1.239776611328125e-05s
INFO | --- Analysis for gipuzkoademografia took 2.0035746097564697s
Availability | SPARQL endpoint availability check for Glastonbury 2011 Programme took 4.291534423828125e-05s
Availability | VoID file availability check for Glastonbury 2011 Programme took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Glastonbury 2011 Programme took 0.1762230396270752s
Reputation | Calculation of the PageRank for Glastonbury 2011 Programme took 0.02198314666748047s
Interlinking | Calculation of Degree of Connection for Glastonbury 2011 Programme took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Glastonbury 2011 Programme took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Glastonbury 2011 Programme took 3.0040740966796875e-05s
Believability | Calculation of trust value for Glastonbury 2011 Programme took 9.775161743164062e-06s
INFO | --- Analysis for glastonbury-2011 took 1.9855360984802246s
Availability | SPARQL endpoint availability check for Global Change Information System took 8.511543273925781e-05s
Availability | VoID file availability check for Global Change Information System took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for Global Change Information System took 0.18581557273864746s
Reputation | Calculation of the PageRank for Global Change Information System took 0.020998239517211914s
Interlinking | Calculation of Degree of Connection for Global Change Information System took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Global Change Information System took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for Global Change Information System took 2.86102294921875e-05s
Believability | Calculation of trust value for Global Change Information System took 1.239776611328125e-05s
INFO | --- Analysis for global-change-information-system took 1.980381727218628s
Availability | SPARQL endpoint availability check for Global Hunger Index (2011) took 8.344650268554688e-05s
Availability | VoID file availability check for Global Hunger Index (2011) took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Global Hunger Index (2011) took 0.18625617027282715s
Reputation | Calculation of the PageRank for Global Hunger Index (2011) took 0.02035999298095703s
Interlinking | Calculation of Degree of Connection for Global Hunger Index (2011) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Global Hunger Index (2011) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Global Hunger Index (2011) took 4.57763671875e-05s
Believability | Calculation of trust value for Global Hunger Index (2011) took 1.239776611328125e-05s
INFO | --- Analysis for global-hunger-index-2011 took 1.9888572692871094s
Availability | SPARQL endpoint availability check for Glottolog took 8.130073547363281e-05s
Availability | VoID file availability check for Glottolog took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Glottolog took 0.17792487144470215s
Reputation | Calculation of the PageRank for Glottolog took 0.022680044174194336s
Interlinking | Calculation of Degree of Connection for Glottolog took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Glottolog took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Glottolog took 4.76837158203125e-05s
Believability | Calculation of trust value for Glottolog took 6.198883056640625e-06s
INFO | --- Analysis for glottolog took 1.989776372909546s
Availability | SPARQL endpoint availability check for GNOSS.com, a Social and Semantic Platform took 4.100799560546875e-05s
Availability | VoID file availability check for GNOSS.com, a Social and Semantic Platform took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for GNOSS.com, a Social and Semantic Platform took 0.18219852447509766s
Reputation | Calculation of the PageRank for GNOSS.com, a Social and Semantic Platform took 0.020505428314208984s
Interlinking | Calculation of Degree of Connection for GNOSS.com, a Social and Semantic Platform took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GNOSS.com, a Social and Semantic Platform took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for GNOSS.com, a Social and Semantic Platform took 0.00010013580322265625s
Believability | Calculation of trust value for GNOSS.com, a Social and Semantic Platform took 1.1920928955078125e-05s
INFO | --- Analysis for gnoss-com-a-social-and-semantic-platform took 1.9948039054870605s
Availability | SPARQL endpoint availability check for GNUsocial social.umeahackerspace.se took 8.225440979003906e-05s
Availability | VoID file availability check for GNUsocial social.umeahackerspace.se took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for GNUsocial social.umeahackerspace.se took 0.17270231246948242s
Reputation | Calculation of the PageRank for GNUsocial social.umeahackerspace.se took 0.02041172981262207s
Interlinking | Calculation of Degree of Connection for GNUsocial social.umeahackerspace.se took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for GNUsocial social.umeahackerspace.se took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for GNUsocial social.umeahackerspace.se took 2.956390380859375e-05s
Believability | Calculation of trust value for GNUsocial social.umeahackerspace.se took 5.7220458984375e-06s
INFO | --- Analysis for gnusocial-social-umeahackerspace-se took 1.9687087535858154s
Availability | SPARQL endpoint availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 8.249282836914062e-05s
Availability | VoID file availability check for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.17715859413146973s
Reputation | Calculation of the PageRank for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.020144939422607422s
Interlinking | Calculation of Degree of Connection for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 2.7894973754882812e-05s
Believability | Calculation of trust value for GO annotations from National Center for Biotechnology Information (NCBI) and European Bioinformatics Institute (EBI) took 1.049041748046875e-05s
INFO | --- Analysis for go_annotations_from_ncbi_and_ebi took 1.968890905380249s
Availability | SPARQL endpoint availability check for 1121 took 8.130073547363281e-05s
Availability | VoID file availability check for 1121 took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for 1121 took 0.18010616302490234s
Reputation | Calculation of the PageRank for 1121 took 0.02100229263305664s
Interlinking | Calculation of Degree of Connection for 1121 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for 1121 took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for 1121 took 2.9325485229492188e-05s
Believability | Calculation of trust value for 1121 took 1.1920928955078125e-05s
INFO | --- Analysis for God_ took 1.9840412139892578s
Availability | SPARQL endpoint availability check for General Ontology of Linguistic Description took 3.910064697265625e-05s
Availability | VoID file availability check for General Ontology of Linguistic Description took 0.00021696090698242188s
Completeness | Calculation of interlinking completeness for General Ontology of Linguistic Description took 0.1799626350402832s
Reputation | Calculation of the PageRank for General Ontology of Linguistic Description took 0.020130634307861328s
Interlinking | Calculation of Degree of Connection for General Ontology of Linguistic Description took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for General Ontology of Linguistic Description took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for General Ontology of Linguistic Description took 5.054473876953125e-05s
Believability | Calculation of trust value for General Ontology of Linguistic Description took 1.0728836059570312e-05s
INFO | --- Analysis for gold took 1.9568450450897217s
Availability | SPARQL endpoint availability check for GoogleArt wrapper took 0.00010275840759277344s
Availability | VoID file availability check for GoogleArt wrapper took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for GoogleArt wrapper took 0.17371201515197754s
Reputation | Calculation of the PageRank for GoogleArt wrapper took 0.021791934967041016s
Interlinking | Calculation of Degree of Connection for GoogleArt wrapper took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for GoogleArt wrapper took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for GoogleArt wrapper took 7.367134094238281e-05s
Believability | Calculation of trust value for GoogleArt wrapper took 1.0728836059570312e-05s
INFO | --- Analysis for googleart-wrapper took 1.9584665298461914s
Availability | SPARQL endpoint availability check for GovAgriBus Denmark took 8.058547973632812e-05s
Availability | VoID file availability check for GovAgriBus Denmark took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for GovAgriBus Denmark took 0.1783428192138672s
Reputation | Calculation of the PageRank for GovAgriBus Denmark took 0.020252227783203125s
Interlinking | Calculation of Degree of Connection for GovAgriBus Denmark took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for GovAgriBus Denmark took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for GovAgriBus Denmark took 3.147125244140625e-05s
Believability | Calculation of trust value for GovAgriBus Denmark took 5.245208740234375e-06s
INFO | --- Analysis for govagribus-denmark took 1.9646084308624268s
Availability | SPARQL endpoint availability check for GovWILD - Government Web Integration for Linked Data took 8.20159912109375e-05s
Availability | VoID file availability check for GovWILD - Government Web Integration for Linked Data took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for GovWILD - Government Web Integration for Linked Data took 0.18275737762451172s
Reputation | Calculation of the PageRank for GovWILD - Government Web Integration for Linked Data took 0.020011186599731445s
Interlinking | Calculation of Degree of Connection for GovWILD - Government Web Integration for Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for GovWILD - Government Web Integration for Linked Data took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for GovWILD - Government Web Integration for Linked Data took 7.748603820800781e-05s
Believability | Calculation of trust value for GovWILD - Government Web Integration for Linked Data took 1.0251998901367188e-05s
INFO | --- Analysis for government-web-integration-for-linked-data took 1.9711627960205078s
Availability | SPARQL endpoint availability check for GovTrack.us U.S Congress Legislative Data took 3.910064697265625e-05s
Availability | VoID file availability check for GovTrack.us U.S Congress Legislative Data took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for GovTrack.us U.S Congress Legislative Data took 0.23205041885375977s
Reputation | Calculation of the PageRank for GovTrack.us U.S Congress Legislative Data took 0.021695375442504883s
Interlinking | Calculation of Degree of Connection for GovTrack.us U.S Congress Legislative Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for GovTrack.us U.S Congress Legislative Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for GovTrack.us U.S Congress Legislative Data took 8.511543273925781e-05s
Believability | Calculation of trust value for GovTrack.us U.S Congress Legislative Data took 1.0728836059570312e-05s
INFO | --- Analysis for govtrack took 2.001561164855957s
Availability | SPARQL endpoint availability check for greek-administrative-geography took 8.273124694824219e-05s
Availability | VoID file availability check for greek-administrative-geography took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for greek-administrative-geography took 0.173997163772583s
Reputation | Calculation of the PageRank for greek-administrative-geography took 0.021248817443847656s
Interlinking | Calculation of Degree of Connection for greek-administrative-geography took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for greek-administrative-geography took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for greek-administrative-geography took 5.745887756347656e-05s
Believability | Calculation of trust value for greek-administrative-geography took 1.049041748046875e-05s
INFO | --- Analysis for greek-administrative-geography took 1.977189540863037s
Availability | SPARQL endpoint availability check for Greek Wordnet took 9.942054748535156e-05s
Availability | VoID file availability check for Greek Wordnet took 0.0004360675811767578s
Completeness | Calculation of interlinking completeness for Greek Wordnet took 0.18699955940246582s
Reputation | Calculation of the PageRank for Greek Wordnet took 0.022112369537353516s
Interlinking | Calculation of Degree of Connection for Greek Wordnet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Greek Wordnet took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Greek Wordnet took 3.838539123535156e-05s
Believability | Calculation of trust value for Greek Wordnet took 1.0728836059570312e-05s
INFO | --- Analysis for greek-wordnet took 1.9734551906585693s
Availability | SPARQL endpoint availability check for Greek prisons releases Jan 2018 - Dec 2023 took 8.249282836914062e-05s
Availability | VoID file availability check for Greek prisons releases Jan 2018 - Dec 2023 took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Greek prisons releases Jan 2018 - Dec 2023 took 0.17323732376098633s
Reputation | Calculation of the PageRank for Greek prisons releases Jan 2018 - Dec 2023 took 0.021692991256713867s
Interlinking | Calculation of Degree of Connection for Greek prisons releases Jan 2018 - Dec 2023 took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Greek prisons releases Jan 2018 - Dec 2023 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Greek prisons releases Jan 2018 - Dec 2023 took 1.1682510375976562e-05s
Believability | Calculation of trust value for Greek prisons releases Jan 2018 - Dec 2023 took 6.9141387939453125e-06s
INFO | --- Analysis for greek_prisons_releases took 2.0003278255462646s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 1.0029208660125732s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.18183016777038574s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.020134449005126953s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.271766662597656e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.049041748046875e-05s
INFO | --- Analysis for greekchildrensartmuseum took 3.393738031387329s
Availability | SPARQL endpoint availability check for Green Competitiveness (GNOSS) took 8.0108642578125e-05s
Availability | VoID file availability check for Green Competitiveness (GNOSS) took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for Green Competitiveness (GNOSS) took 0.1802382469177246s
Reputation | Calculation of the PageRank for Green Competitiveness (GNOSS) took 0.02012801170349121s
Interlinking | Calculation of Degree of Connection for Green Competitiveness (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Green Competitiveness (GNOSS) took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Green Competitiveness (GNOSS) took 9.489059448242188e-05s
Believability | Calculation of trust value for Green Competitiveness (GNOSS) took 5.7220458984375e-06s
INFO | --- Analysis for green-competitiveness-gnoss took 1.965510368347168s
Availability | SPARQL endpoint availability check for Accommodations in Piedmont (LinkedOpenData.it) took 3.981590270996094e-05s
Availability | VoID file availability check for Accommodations in Piedmont (LinkedOpenData.it) took 0.00043702125549316406s
Completeness | Calculation of interlinking completeness for Accommodations in Piedmont (LinkedOpenData.it) took 0.17828702926635742s
Reputation | Calculation of the PageRank for Accommodations in Piedmont (LinkedOpenData.it) took 0.020253419876098633s
Interlinking | Calculation of Degree of Connection for Accommodations in Piedmont (LinkedOpenData.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Accommodations in Piedmont (LinkedOpenData.it) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Accommodations in Piedmont (LinkedOpenData.it) took 4.4345855712890625e-05s
Believability | Calculation of trust value for Accommodations in Piedmont (LinkedOpenData.it) took 9.5367431640625e-06s
INFO | --- Analysis for grrp took 1.9527533054351807s
Availability | SPARQL endpoint availability check for Accommodations in Tuscany (LinkedOpenData.it) took 8.153915405273438e-05s
Availability | VoID file availability check for Accommodations in Tuscany (LinkedOpenData.it) took 0.0004355907440185547s
Completeness | Calculation of interlinking completeness for Accommodations in Tuscany (LinkedOpenData.it) took 0.18314266204833984s
Reputation | Calculation of the PageRank for Accommodations in Tuscany (LinkedOpenData.it) took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Accommodations in Tuscany (LinkedOpenData.it) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Accommodations in Tuscany (LinkedOpenData.it) took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Accommodations in Tuscany (LinkedOpenData.it) took 6.389617919921875e-05s
Believability | Calculation of trust value for Accommodations in Tuscany (LinkedOpenData.it) took 1.0728836059570312e-05s
INFO | --- Analysis for grrt took 1.9672961235046387s
Availability | SPARQL endpoint availability check for Geological Timescale took 3.933906555175781e-05s
Availability | VoID file availability check for Geological Timescale took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for Geological Timescale took 0.18163418769836426s
Reputation | Calculation of the PageRank for Geological Timescale took 0.020056486129760742s
Interlinking | Calculation of Degree of Connection for Geological Timescale took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Geological Timescale took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Geological Timescale took 6.4849853515625e-05s
Believability | Calculation of trust value for Geological Timescale took 1.049041748046875e-05s
INFO | --- Analysis for GTS took 1.9530634880065918s
Availability | SPARQL endpoint availability check for Geological Timescale Ontology took 9.918212890625e-05s
Availability | VoID file availability check for Geological Timescale Ontology took 0.00021076202392578125s
Completeness | Calculation of interlinking completeness for Geological Timescale Ontology took 0.17882156372070312s
Reputation | Calculation of the PageRank for Geological Timescale Ontology took 0.022192716598510742s
Interlinking | Calculation of Degree of Connection for Geological Timescale Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Geological Timescale Ontology took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Geological Timescale Ontology took 3.147125244140625e-05s
Believability | Calculation of trust value for Geological Timescale Ontology took 7.867813110351562e-06s
INFO | --- Analysis for GTS-ont took 1.9490725994110107s
Availability | SPARQL endpoint availability check for GUTSTOK  took 9.799003601074219e-05s
Availability | VoID file availability check for GUTSTOK  took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for GUTSTOK  took 0.17126154899597168s
Reputation | Calculation of the PageRank for GUTSTOK  took 0.02013230323791504s
Interlinking | Calculation of Degree of Connection for GUTSTOK  took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for GUTSTOK  took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for GUTSTOK  took 2.86102294921875e-05s
Believability | Calculation of trust value for GUTSTOK  took 1.1205673217773438e-05s
INFO | --- Analysis for Guillaume_Forget took 1.9525775909423828s
Availability | SPARQL endpoint availability check for Project Gutenberg took 4.100799560546875e-05s
Availability | VoID file availability check for Project Gutenberg took 0.00036025047302246094s
Completeness | Calculation of interlinking completeness for Project Gutenberg took 0.1848134994506836s
Reputation | Calculation of the PageRank for Project Gutenberg took 0.020678997039794922s
Interlinking | Calculation of Degree of Connection for Project Gutenberg took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Project Gutenberg took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Project Gutenberg took 6.604194641113281e-05s
Believability | Calculation of trust value for Project Gutenberg took 5.245208740234375e-06s
INFO | --- Analysis for gutenberg took 2.735950231552124s
Availability | SPARQL endpoint availability check for Global WordNet Association Interlingual Index took 8.320808410644531e-05s
Availability | VoID file availability check for Global WordNet Association Interlingual Index took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Global WordNet Association Interlingual Index took 0.17638015747070312s
Reputation | Calculation of the PageRank for Global WordNet Association Interlingual Index took 0.02207326889038086s
Interlinking | Calculation of Degree of Connection for Global WordNet Association Interlingual Index took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Global WordNet Association Interlingual Index took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Global WordNet Association Interlingual Index took 3.457069396972656e-05s
Believability | Calculation of trust value for Global WordNet Association Interlingual Index took 1.0967254638671875e-05s
INFO | --- Analysis for gwa-ili took 1.9718916416168213s
Availability | SPARQL endpoint availability check for Geographically Weighted Regression Model took 4.363059997558594e-05s
Availability | VoID file availability check for Geographically Weighted Regression Model took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for Geographically Weighted Regression Model took 0.17014050483703613s
Reputation | Calculation of the PageRank for Geographically Weighted Regression Model took 0.02017807960510254s
Interlinking | Calculation of Degree of Connection for Geographically Weighted Regression Model took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Geographically Weighted Regression Model took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Geographically Weighted Regression Model took 2.9087066650390625e-05s
Believability | Calculation of trust value for Geographically Weighted Regression Model took 5.7220458984375e-06s
INFO | --- Analysis for GWR took 1.9660475254058838s
Availability | SPARQL endpoint availability check for High Accuracy Surface Modeling took 4.076957702636719e-05s
Availability | VoID file availability check for High Accuracy Surface Modeling took 0.0002675056457519531s
Completeness | Calculation of interlinking completeness for High Accuracy Surface Modeling took 0.18049907684326172s
Reputation | Calculation of the PageRank for High Accuracy Surface Modeling took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for High Accuracy Surface Modeling took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for High Accuracy Surface Modeling took 0.0007476806640625s
Interlinking | Calculation of Clustering coefficient for High Accuracy Surface Modeling took 3.123283386230469e-05s
Believability | Calculation of trust value for High Accuracy Surface Modeling took 7.3909759521484375e-06s
INFO | --- Analysis for HASM took 1.9465374946594238s
Availability | SPARQL endpoint availability check for HCLS Knowledge Base took 3.838539123535156e-05s
Availability | VoID file availability check for HCLS Knowledge Base took 0.0005335807800292969s
Completeness | Calculation of interlinking completeness for HCLS Knowledge Base took 0.18096375465393066s
Reputation | Calculation of the PageRank for HCLS Knowledge Base took 0.021829605102539062s
Interlinking | Calculation of Degree of Connection for HCLS Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for HCLS Knowledge Base took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for HCLS Knowledge Base took 2.956390380859375e-05s
Believability | Calculation of trust value for HCLS Knowledge Base took 1.049041748046875e-05s
INFO | --- Analysis for hcls-knowledge-base took 1.9552607536315918s
Availability | SPARQL endpoint availability check for HealthCare Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for HealthCare Ontology took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for HealthCare Ontology took 0.17257952690124512s
Reputation | Calculation of the PageRank for HealthCare Ontology took 0.020395994186401367s
Interlinking | Calculation of Degree of Connection for HealthCare Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for HealthCare Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for HealthCare Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for HealthCare Ontology took 1.1682510375976562e-05s
INFO | --- Analysis for HealthCare_Ontology took 1.9765300750732422s
Availability | SPARQL endpoint availability check for Meriterm Heart Failure Multilingual Terminology took 8.463859558105469e-05s
Availability | VoID file availability check for Meriterm Heart Failure Multilingual Terminology took 0.00021123886108398438s
Completeness | Calculation of interlinking completeness for Meriterm Heart Failure Multilingual Terminology took 0.17921781539916992s
Reputation | Calculation of the PageRank for Meriterm Heart Failure Multilingual Terminology took 0.02016139030456543s
Interlinking | Calculation of Degree of Connection for Meriterm Heart Failure Multilingual Terminology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Meriterm Heart Failure Multilingual Terminology took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Meriterm Heart Failure Multilingual Terminology took 5.6743621826171875e-05s
Believability | Calculation of trust value for Meriterm Heart Failure Multilingual Terminology took 1.1205673217773438e-05s
INFO | --- Analysis for heartfailure took 1.9597408771514893s
Availability | SPARQL endpoint availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 21.659433841705322s
Availability | VoID file availability check for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.00048089027404785156s
Completeness | Calculation of interlinking completeness for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.1842365264892578s
Reputation | Calculation of the PageRank for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.020099401473999023s
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.049041748046875e-05s
Interlinking | Calculation of Centrality for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 3.528594970703125e-05s
Believability | Calculation of trust value for HeBIS - Bibliographic Resources of the Library Union Catalogues of Hessen and parts of the Rhineland Palatinate took 1.0013580322265625e-05s
INFO | --- Analysis for hebis-bibliographic-resources took 53.85541296005249s
Availability | SPARQL endpoint availability check for Hedatuz took 0.3269662857055664s
Availability | VoID file availability check for Hedatuz took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Hedatuz took 0.17469048500061035s
Reputation | Calculation of the PageRank for Hedatuz took 0.021382570266723633s
Interlinking | Calculation of Degree of Connection for Hedatuz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Hedatuz took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Hedatuz took 4.1961669921875e-05s
Believability | Calculation of trust value for Hedatuz took 1.049041748046875e-05s
INFO | --- Analysis for hedatuz took 2.4539084434509277s
Availability | SPARQL endpoint availability check for Hellenic Fire Brigade took 7.963180541992188e-05s
Availability | VoID file availability check for Hellenic Fire Brigade took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Hellenic Fire Brigade took 0.2262558937072754s
Reputation | Calculation of the PageRank for Hellenic Fire Brigade took 0.02020263671875s
Interlinking | Calculation of Degree of Connection for Hellenic Fire Brigade took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Hellenic Fire Brigade took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Hellenic Fire Brigade took 0.00012683868408203125s
Believability | Calculation of trust value for Hellenic Fire Brigade took 1.0967254638671875e-05s
INFO | --- Analysis for hellenic-fire-brigade took 2.087240219116211s
Availability | SPARQL endpoint availability check for Hellenic Police took 3.910064697265625e-05s
Availability | VoID file availability check for Hellenic Police took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Hellenic Police took 0.19365358352661133s
Reputation | Calculation of the PageRank for Hellenic Police took 0.02014899253845215s
Interlinking | Calculation of Degree of Connection for Hellenic Police took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Hellenic Police took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Hellenic Police took 0.00012421607971191406s
Believability | Calculation of trust value for Hellenic Police took 1.1205673217773438e-05s
INFO | --- Analysis for hellenic-police took 1.9789257049560547s
Availability | SPARQL endpoint availability check for Hermos took 0.00010919570922851562s
Availability | VoID file availability check for Hermos took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Hermos took 0.17242026329040527s
Reputation | Calculation of the PageRank for Hermos took 0.021247148513793945s
Interlinking | Calculation of Degree of Connection for Hermos took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Hermos took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Hermos took 2.765655517578125e-05s
Believability | Calculation of trust value for Hermos took 1.0967254638671875e-05s
INFO | --- Analysis for Hermos took 1.9579033851623535s
Availability | SPARQL endpoint availability check for Himanshu Mahawar took 8.225440979003906e-05s
Availability | VoID file availability check for Himanshu Mahawar took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Himanshu Mahawar took 0.1730797290802002s
Reputation | Calculation of the PageRank for Himanshu Mahawar took 0.020102977752685547s
Interlinking | Calculation of Degree of Connection for Himanshu Mahawar took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Himanshu Mahawar took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Himanshu Mahawar took 2.7894973754882812e-05s
Believability | Calculation of trust value for Himanshu Mahawar took 1.0728836059570312e-05s
INFO | --- Analysis for Himanshu_Mahawar took 1.9532241821289062s
Availability | SPARQL endpoint availability check for HITO took 7.295608520507812e-05s
Availability | VoID file availability check for HITO took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for HITO took 0.17118263244628906s
Reputation | Calculation of the PageRank for HITO took 0.02015376091003418s
Interlinking | Calculation of Degree of Connection for HITO took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for HITO took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for HITO took 6.842613220214844e-05s
Believability | Calculation of trust value for HITO took 7.3909759521484375e-06s
INFO | --- Analysis for hito took 2.0922815799713135s
Availability | SPARQL endpoint availability check for Hoa Thịnh Phát took 4.100799560546875e-05s
Availability | VoID file availability check for Hoa Thịnh Phát took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for Hoa Thịnh Phát took 0.1710193157196045s
Reputation | Calculation of the PageRank for Hoa Thịnh Phát took 0.02025580406188965s
Interlinking | Calculation of Degree of Connection for Hoa Thịnh Phát took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Hoa Thịnh Phát took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Hoa Thịnh Phát took 2.86102294921875e-05s
Believability | Calculation of trust value for Hoa Thịnh Phát took 7.62939453125e-06s
INFO | --- Analysis for Hoa_Thinh_Phat took 1.9345510005950928s
Availability | SPARQL endpoint availability check for Homologene took 3.933906555175781e-05s
Availability | VoID file availability check for Homologene took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Homologene took 0.17929697036743164s
Reputation | Calculation of the PageRank for Homologene took 0.0213623046875s
Interlinking | Calculation of Degree of Connection for Homologene took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Homologene took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Homologene took 2.9087066650390625e-05s
Believability | Calculation of trust value for Homologene took 1.1920928955078125e-05s
INFO | --- Analysis for homologene took 2.103717088699341s
Availability | SPARQL endpoint availability check for gseg took 8.296966552734375e-05s
Availability | VoID file availability check for gseg took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for gseg took 0.17981171607971191s
Reputation | Calculation of the PageRank for gseg took 0.021219253540039062s
Interlinking | Calculation of Degree of Connection for gseg took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for gseg took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for gseg took 2.7418136596679688e-05s
Believability | Calculation of trust value for gseg took 1.1444091796875e-05s
INFO | --- Analysis for hongse took 1.96425199508667s
Availability | SPARQL endpoint availability check for Noticias Universia took 3.910064697265625e-05s
Availability | VoID file availability check for Noticias Universia took 0.0002148151397705078s
Completeness | Calculation of interlinking completeness for Noticias Universia took 0.1794741153717041s
Reputation | Calculation of the PageRank for Noticias Universia took 0.022797346115112305s
Interlinking | Calculation of Degree of Connection for Noticias Universia took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Noticias Universia took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Noticias Universia took 5.650520324707031e-05s
Believability | Calculation of trust value for Noticias Universia took 1.1205673217773438e-05s
INFO | --- Analysis for http-data-noticias-universia-net took 1.9927163124084473s
Availability | SPARQL endpoint availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 7.43865966796875e-05s
Availability | VoID file availability check for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.17223691940307617s
Reputation | Calculation of the PageRank for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 2.956390380859375e-05s
Believability | Calculation of trust value for http://www.iwmi.cgiar.org/publications/iwmi-working-papers/ took 9.775161743164062e-06s
INFO | --- Analysis for http-www-iwmi-cgiar-org-publications-iwmi-working-papers took 1.950552225112915s
Availability | SPARQL endpoint availability check for COURAGE Dataset took 1.6360042095184326s
Availability | VoID file availability check for COURAGE Dataset took 0.0003695487976074219s
Completeness | Calculation of interlinking completeness for COURAGE Dataset took 0.18117904663085938s
Reputation | Calculation of the PageRank for COURAGE Dataset took 0.020113468170166016s
Interlinking | Calculation of Degree of Connection for COURAGE Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for COURAGE Dataset took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for COURAGE Dataset took 2.8371810913085938e-05s
Believability | Calculation of trust value for COURAGE Dataset took 1.2636184692382812e-05s
INFO | --- Analysis for http:cultural-opposition.eu took 4.368436574935913s
Availability | SPARQL endpoint availability check for RoadTrb took 8.416175842285156e-05s
Availability | VoID file availability check for RoadTrb took 0.000377655029296875s
Completeness | Calculation of interlinking completeness for RoadTrb took 0.18167710304260254s
Reputation | Calculation of the PageRank for RoadTrb took 0.020041227340698242s
Interlinking | Calculation of Degree of Connection for RoadTrb took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RoadTrb took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for RoadTrb took 2.7418136596679688e-05s
Believability | Calculation of trust value for RoadTrb took 6.198883056640625e-06s
INFO | --- Analysis for http:data.linkedeodata.euroadidStateRoadD010Turkey-1 took 1.9567070007324219s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.7738037109375e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.17836618423461914s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.023138761520385742s
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.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.1444091796875e-05s
INFO | --- Analysis for http:guava.iis.sinica.edu.twr4r took 1.9515986442565918s
Availability | SPARQL endpoint availability check for Polictical History of Pakistan took 3.9577484130859375e-05s
Availability | VoID file availability check for Polictical History of Pakistan took 0.0004532337188720703s
Completeness | Calculation of interlinking completeness for Polictical History of Pakistan took 0.17535972595214844s
Reputation | Calculation of the PageRank for Polictical History of Pakistan took 0.02266407012939453s
Interlinking | Calculation of Degree of Connection for Polictical History of Pakistan took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Polictical History of Pakistan took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Polictical History of Pakistan took 2.7418136596679688e-05s
Believability | Calculation of trust value for Polictical History of Pakistan took 1.1682510375976562e-05s
INFO | --- Analysis for http:pakistan.com took 1.97365403175354s
Availability | SPARQL endpoint availability check for CEDICT took 8.344650268554688e-05s
Availability | VoID file availability check for CEDICT took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for CEDICT took 0.18253636360168457s
Reputation | Calculation of the PageRank for CEDICT took 0.022302865982055664s
Interlinking | Calculation of Degree of Connection for CEDICT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for CEDICT took 0.0007429122924804688s
Interlinking | Calculation of Clustering coefficient for CEDICT took 3.62396240234375e-05s
Believability | Calculation of trust value for CEDICT took 1.0251998901367188e-05s
INFO | --- Analysis for http:rdf.naturallexicon.orgzhontCedict took 2.050783395767212s
Availability | SPARQL endpoint availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 3.933906555175781e-05s
Availability | VoID file availability check for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.19556760787963867s
Reputation | Calculation of the PageRank for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020194292068481445s
Interlinking | Calculation of Degree of Connection for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.29425048828125e-05s
Believability | Calculation of trust value for Naturopathy knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 1.0967254638671875e-05s
INFO | --- Analysis for http:sensormeasurement.appspot.comdatasetnaturopathy-dataset took 2.0034239292144775s
Availability | SPARQL endpoint availability check for Pakistan Stock Market Data took 8.58306884765625e-05s
Availability | VoID file availability check for Pakistan Stock Market Data took 0.0002334117889404297s
Completeness | Calculation of interlinking completeness for Pakistan Stock Market Data took 0.17960667610168457s
Reputation | Calculation of the PageRank for Pakistan Stock Market Data took 0.020916461944580078s
Interlinking | Calculation of Degree of Connection for Pakistan Stock Market Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Pakistan Stock Market Data took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for Pakistan Stock Market Data took 3.457069396972656e-05s
Believability | Calculation of trust value for Pakistan Stock Market Data took 1.0967254638671875e-05s
INFO | --- Analysis for http:www.atif-sajjad.comSemster-Project# took 2.010061025619507s
Availability | SPARQL endpoint availability check for Grand Slam Knowledge Graph took 0.00011491775512695312s
Availability | VoID file availability check for Grand Slam Knowledge Graph took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for Grand Slam Knowledge Graph took 0.1888113021850586s
Reputation | Calculation of the PageRank for Grand Slam Knowledge Graph took 0.020158767700195312s
Interlinking | Calculation of Degree of Connection for Grand Slam Knowledge Graph took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Grand Slam Knowledge Graph took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Grand Slam Knowledge Graph took 2.7179718017578125e-05s
Believability | Calculation of trust value for Grand Slam Knowledge Graph took 1.5020370483398438e-05s
INFO | --- Analysis for http:www.fateh_fahad_adeel.comgrandSlam took 2.018418073654175s
Availability | SPARQL endpoint availability check for Soccer Dataset took 3.910064697265625e-05s
Availability | VoID file availability check for Soccer Dataset took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Soccer Dataset took 0.1828761100769043s
Reputation | Calculation of the PageRank for Soccer Dataset took 0.02142047882080078s
Interlinking | Calculation of Degree of Connection for Soccer Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Soccer Dataset took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Soccer Dataset took 2.8133392333984375e-05s
Believability | Calculation of trust value for Soccer Dataset took 1.1682510375976562e-05s
INFO | --- Analysis for http:www.msm.com took 2.0127615928649902s
Availability | SPARQL endpoint availability check for Game Ontology took 8.440017700195312e-05s
Availability | VoID file availability check for Game Ontology took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for Game Ontology took 0.17595386505126953s
Reputation | Calculation of the PageRank for Game Ontology took 0.020189523696899414s
Interlinking | Calculation of Degree of Connection for Game Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Game Ontology took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Game Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for Game Ontology took 6.198883056640625e-06s
INFO | --- Analysis for http:www.RAG.comgameonto# took 1.9915564060211182s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 8.487701416015625e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.19414329528808594s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.02142810821533203s
Interlinking | Calculation of Degree of Connection for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Covid19 Impact on Banking ontology (Covid19-IBO) took 0.0010898113250732422s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO) took 3.719329833984375e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO) took 1.1920928955078125e-05s
INFO | --- Analysis for http:www.semanticweb.orgambrishontologies202010untitled-ontology-24 took 2.0587337017059326s
Availability | SPARQL endpoint availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 3.9577484130859375e-05s
Availability | VoID file availability check for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.17406749725341797s
Reputation | Calculation of the PageRank for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 0.0201568603515625s
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.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Covid19 Impact on Banking ontology (Covid19-IBO 1.5) took 5.4836273193359375e-06s
INFO | --- Analysis for http:www.semanticweb.orgarchanaontologies20215untitled-ontology-6 took 2.014972686767578s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.58306884765625e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.17281699180603027s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.020376205444335938s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.765655517578125e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.0967254638671875e-05s
INFO | --- Analysis for http:www.semanticweb.orgmcaontologies20188untitled-ontology-47 took 1.9888248443603516s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.440017700195312e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00021028518676757812s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.19695019721984863s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02045917510986328s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2159347534179688e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIO took 2.0176210403442383s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 3.981590270996094e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.17696642875671387s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.021650075912475586s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8371810913085938e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1682510375976562e-05s
INFO | --- Analysis for https:bioportal.bioontology.orgontologiesIBIOp=summary took 1.9910023212432861s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 8.320808410644531e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.00021529197692871094s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.187333345413208s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.02005147933959961s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.2159347534179688e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBDsubmissions1downloadapikey=8b5b7825-538d-40e0-9e9e-5ab9274a9aeb took 2.0010550022125244s
Availability | SPARQL endpoint availability check for Indian Biodiversity took 3.9577484130859375e-05s
Availability | VoID file availability check for Indian Biodiversity took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for Indian Biodiversity took 0.17798280715942383s
Reputation | Calculation of the PageRank for Indian Biodiversity took 0.022392988204956055s
Interlinking | Calculation of Degree of Connection for Indian Biodiversity took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Indian Biodiversity took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Indian Biodiversity took 2.8133392333984375e-05s
Believability | Calculation of trust value for Indian Biodiversity took 1.1444091796875e-05s
INFO | --- Analysis for https:data.bioontology.orgontologiesIBIOsubmissions1downloadapikey=66c2aec1-4044-4900-979d-6f529857554a took 2.040513277053833s
Availability | SPARQL endpoint availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 3.981590270996094e-05s
Availability | VoID file availability check for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0004799365997314453s
Completeness | Calculation of interlinking completeness for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.18295764923095703s
Reputation | Calculation of the PageRank for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.020249605178833008s
Interlinking | Calculation of Degree of Connection for Diretrizes organizacionais de métodos quantitativos e computação científica took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Diretrizes organizacionais de métodos quantitativos e computação científica took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Diretrizes organizacionais de métodos quantitativos e computação científica took 2.9325485229492188e-05s
Believability | Calculation of trust value for Diretrizes organizacionais de métodos quantitativos e computação científica took 1.0967254638671875e-05s
INFO | --- Analysis for https:orcid.org0000-0002-6194-9354 took 2.0115602016448975s
Availability | SPARQL endpoint availability check for Bookkeeping took 8.344650268554688e-05s
Availability | VoID file availability check for Bookkeeping took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Bookkeeping took 0.17610597610473633s
Reputation | Calculation of the PageRank for Bookkeeping took 0.022762537002563477s
Interlinking | Calculation of Degree of Connection for Bookkeeping took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Bookkeeping took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Bookkeeping took 2.765655517578125e-05s
Believability | Calculation of trust value for Bookkeeping took 5.7220458984375e-06s
INFO | --- Analysis for https:raw.githubusercontent.comGVogelerbookkeepingmasterbookkeeping.ttl took 1.9893255233764648s
Availability | SPARQL endpoint availability check for Legal Ontology took 4.029273986816406e-05s
Availability | VoID file availability check for Legal Ontology took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Legal Ontology took 0.1810450553894043s
Reputation | Calculation of the PageRank for Legal Ontology took 0.02160811424255371s
Interlinking | Calculation of Degree of Connection for Legal Ontology took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Legal Ontology took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Legal Ontology took 3.170967102050781e-05s
Believability | Calculation of trust value for Legal Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for https:w3id.orgdefNyOnLegal# took 1.9773519039154053s
Availability | SPARQL endpoint availability check for Greek Children Art  Museum dataset took 4.100799560546875e-05s
Availability | VoID file availability check for Greek Children Art  Museum dataset took 0.00044655799865722656s
Completeness | Calculation of interlinking completeness for Greek Children Art  Museum dataset took 0.18290114402770996s
Reputation | Calculation of the PageRank for Greek Children Art  Museum dataset took 0.02026057243347168s
Interlinking | Calculation of Degree of Connection for Greek Children Art  Museum dataset took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Greek Children Art  Museum dataset took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Greek Children Art  Museum dataset took 7.462501525878906e-05s
Believability | Calculation of trust value for Greek Children Art  Museum dataset took 1.0013580322265625e-05s
INFO | --- Analysis for https:www.childrensartmuseum.grLD-project took 1.9908995628356934s
Availability | SPARQL endpoint availability check for Writer Luigi Usai took 7.963180541992188e-05s
Availability | VoID file availability check for Writer Luigi Usai took 0.0004305839538574219s
Completeness | Calculation of interlinking completeness for Writer Luigi Usai took 0.17930984497070312s
Reputation | Calculation of the PageRank for Writer Luigi Usai took 0.02038717269897461s
Interlinking | Calculation of Degree of Connection for Writer Luigi Usai took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Writer Luigi Usai took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for Writer Luigi Usai took 2.8133392333984375e-05s
Believability | Calculation of trust value for Writer Luigi Usai took 1.0967254638671875e-05s
INFO | --- Analysis for https:www.luigiusai.itlinked-dataluigiusai took 1.9495737552642822s
Availability | SPARQL endpoint availability check for Hua Hin Health Tourism Data Set took 3.933906555175781e-05s
Availability | VoID file availability check for Hua Hin Health Tourism Data Set took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Hua Hin Health Tourism Data Set took 0.1910569667816162s
Reputation | Calculation of the PageRank for Hua Hin Health Tourism Data Set took 0.021982908248901367s
Interlinking | Calculation of Degree of Connection for Hua Hin Health Tourism Data Set took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Hua Hin Health Tourism Data Set took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Hua Hin Health Tourism Data Set took 2.6464462280273438e-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 1.9906301498413086s
Availability | SPARQL endpoint availability check for University of Huddersfield -- Circulation and Recommendation Data took 3.9577484130859375e-05s
Availability | VoID file availability check for University of Huddersfield -- Circulation and Recommendation Data took 0.0002028942108154297s
Completeness | Calculation of interlinking completeness for University of Huddersfield -- Circulation and Recommendation Data took 0.1808488368988037s
Reputation | Calculation of the PageRank for University of Huddersfield -- Circulation and Recommendation Data took 0.020794391632080078s
Interlinking | Calculation of Degree of Connection for University of Huddersfield -- Circulation and Recommendation Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for University of Huddersfield -- Circulation and Recommendation Data took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for University of Huddersfield -- Circulation and Recommendation Data took 2.6702880859375e-05s
Believability | Calculation of trust value for University of Huddersfield -- Circulation and Recommendation Data took 1.0967254638671875e-05s
INFO | --- Analysis for hud-library-usagedata took 1.9572265148162842s
Availability | SPARQL endpoint availability check for Hungarian National Library (NSZL) catalog took 1.4006462097167969s
Availability | VoID file availability check for Hungarian National Library (NSZL) catalog took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for Hungarian National Library (NSZL) catalog took 0.17419075965881348s
Reputation | Calculation of the PageRank for Hungarian National Library (NSZL) catalog took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for Hungarian National Library (NSZL) catalog took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Hungarian National Library (NSZL) catalog took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Hungarian National Library (NSZL) catalog took 0.0001010894775390625s
Believability | Calculation of trust value for Hungarian National Library (NSZL) catalog took 1.1682510375976562e-05s
INFO | --- Analysis for hungarian-national-library-catalog took 3.897317409515381s
Availability | SPARQL endpoint availability check for IATE RDF took 4.410743713378906e-05s
Availability | VoID file availability check for IATE RDF took 0.00054931640625s
Completeness | Calculation of interlinking completeness for IATE RDF took 0.18538641929626465s
Reputation | Calculation of the PageRank for IATE RDF took 0.02046346664428711s
Interlinking | Calculation of Degree of Connection for IATE RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for IATE RDF took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for IATE RDF took 3.218650817871094e-05s
Believability | Calculation of trust value for IATE RDF took 7.867813110351562e-06s
INFO | --- Analysis for iate-rdf took 2.0202858448028564s
Availability | SPARQL endpoint availability check for IATI as Linked Data took 4.1484832763671875e-05s
Availability | VoID file availability check for IATI as Linked Data took 0.00024271011352539062s
Completeness | Calculation of interlinking completeness for IATI as Linked Data took 0.17772197723388672s
Reputation | Calculation of the PageRank for IATI as Linked Data took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for IATI as Linked Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for IATI as Linked Data took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for IATI as Linked Data took 8.654594421386719e-05s
Believability | Calculation of trust value for IATI as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for iati-as-linked-data took 1.9418401718139648s
Availability | SPARQL endpoint availability check for ICANE took 8.273124694824219e-05s
Availability | VoID file availability check for ICANE took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for ICANE took 0.2876765727996826s
Reputation | Calculation of the PageRank for ICANE took 0.020040512084960938s
Interlinking | Calculation of Degree of Connection for ICANE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ICANE took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for ICANE took 8.273124694824219e-05s
Believability | Calculation of trust value for ICANE took 1.0967254638671875e-05s
INFO | --- Analysis for icane took 2.078679323196411s
Availability | SPARQL endpoint availability check for ichoose took 9.036064147949219e-05s
Availability | VoID file availability check for ichoose took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for ichoose took 0.1809992790222168s
Reputation | Calculation of the PageRank for ichoose took 0.020101547241210938s
Interlinking | Calculation of Degree of Connection for ichoose took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ichoose took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for ichoose took 6.508827209472656e-05s
Believability | Calculation of trust value for ichoose took 1.1205673217773438e-05s
INFO | --- Analysis for ichoose took 1.9884166717529297s
Availability | SPARQL endpoint availability check for The Iconology Dataset took 7.915496826171875e-05s
Availability | VoID file availability check for The Iconology Dataset took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for The Iconology Dataset took 0.18343138694763184s
Reputation | Calculation of the PageRank for The Iconology Dataset took 0.02071237564086914s
Interlinking | Calculation of Degree of Connection for The Iconology Dataset took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for The Iconology Dataset took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for The Iconology Dataset took 1.2159347534179688e-05s
Believability | Calculation of trust value for The Iconology Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for iconology-dataset took 1.9620921611785889s
Availability | SPARQL endpoint availability check for Identifiers.org took 3.8623809814453125e-05s
Availability | VoID file availability check for Identifiers.org took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Identifiers.org took 0.19091796875s
Reputation | Calculation of the PageRank for Identifiers.org took 0.020185232162475586s
Interlinking | Calculation of Degree of Connection for Identifiers.org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Identifiers.org took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Identifiers.org took 3.4809112548828125e-05s
Believability | Calculation of trust value for Identifiers.org took 1.0728836059570312e-05s
INFO | --- Analysis for identifiers-org took 1.984144687652588s
Availability | SPARQL endpoint availability check for IdRef: Sudoc authority data took 8.7738037109375e-05s
Availability | VoID file availability check for IdRef: Sudoc authority data took 0.00047469139099121094s
Completeness | Calculation of interlinking completeness for IdRef: Sudoc authority data took 0.18044543266296387s
Reputation | Calculation of the PageRank for IdRef: Sudoc authority data took 0.02213764190673828s
Interlinking | Calculation of Degree of Connection for IdRef: Sudoc authority data took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for IdRef: Sudoc authority data took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for IdRef: Sudoc authority data took 7.772445678710938e-05s
Believability | Calculation of trust value for IdRef: Sudoc authority data took 7.3909759521484375e-06s
INFO | --- Analysis for idreffr took 1.9928903579711914s
Availability | SPARQL endpoint availability check for Intercontinental Dictionary Series took 0.00012826919555664062s
Availability | VoID file availability check for Intercontinental Dictionary Series took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for Intercontinental Dictionary Series took 0.1726698875427246s
Reputation | Calculation of the PageRank for Intercontinental Dictionary Series took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for Intercontinental Dictionary Series took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Intercontinental Dictionary Series took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Intercontinental Dictionary Series took 4.5299530029296875e-05s
Believability | Calculation of trust value for Intercontinental Dictionary Series took 1.049041748046875e-05s
INFO | --- Analysis for ids took 1.9650630950927734s
Availability | SPARQL endpoint availability check for ietflang took 3.8623809814453125e-05s
Availability | VoID file availability check for ietflang took 0.0004813671112060547s
Completeness | Calculation of interlinking completeness for ietflang took 0.17471981048583984s
Reputation | Calculation of the PageRank for ietflang took 0.02186417579650879s
Interlinking | Calculation of Degree of Connection for ietflang took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ietflang took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for ietflang took 4.3392181396484375e-05s
Believability | Calculation of trust value for ietflang took 1.1444091796875e-05s
INFO | --- Analysis for ietflang took 1.9847543239593506s
Availability | SPARQL endpoint availability check for Index Graecorum Vocabulorum in LiLa took 3.9577484130859375e-05s
Availability | VoID file availability check for Index Graecorum Vocabulorum in LiLa took 0.0004794597625732422s
Completeness | Calculation of interlinking completeness for Index Graecorum Vocabulorum in LiLa took 0.17331957817077637s
Reputation | Calculation of the PageRank for Index Graecorum Vocabulorum in LiLa took 0.02021336555480957s
Interlinking | Calculation of Degree of Connection for Index Graecorum Vocabulorum in LiLa took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Index Graecorum Vocabulorum in LiLa took 0.0006885528564453125s
Interlinking | Calculation of Clustering coefficient for Index Graecorum Vocabulorum in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for Index Graecorum Vocabulorum in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for IGVLL took 1.9647140502929688s
Availability | SPARQL endpoint availability check for 3LGM² IHE Ontology took 8.630752563476562e-05s
Availability | VoID file availability check for 3LGM² IHE Ontology took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for 3LGM² IHE Ontology took 0.17930126190185547s
Reputation | Calculation of the PageRank for 3LGM² IHE Ontology took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for 3LGM² IHE Ontology took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for 3LGM² IHE Ontology took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for 3LGM² IHE Ontology took 2.765655517578125e-05s
Believability | Calculation of trust value for 3LGM² IHE Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for IHE took 1.9822306632995605s
Availability | SPARQL endpoint availability check for Test Site, LOD Lab 317 took 2.7628254890441895s
Availability | VoID file availability check for Test Site, LOD Lab 317 took 0.0002391338348388672s
Extra | Recovery of all triples for Test Site, LOD Lab 317 took 7.114996910095215s
Performance | Total latancy measurement for Test Site, LOD Lab 317 took 8.179847478866577s
Amount of data | Number of triples check for Test Site, LOD Lab 317 took 20.381911754608154s
Interoperability | New terms check for Test Site, LOD Lab 317 took 8.026055097579956s
Versatility | Languages check for Test Site, LOD Lab 317 took 61.62483263015747s
Interpretability | Number of blank nodes check for Test Site, LOD Lab 317 took 1.7847678661346436s
Security | Check HTTPS for Test Site, LOD Lab 317 took 1.0810513496398926s
Interpretability | RDF structures check for Test Site, LOD Lab 317 took 2.1197409629821777s
Versatility | Serialization formats check for Test Site, LOD Lab 317 took 1.8835217952728271s
Availability | RDF dump link check for Test Site, LOD Lab 317 took 1.6452927589416504s
License | MR license check for Test Site, LOD Lab 317 took 1.852996587753296s
License | HR license check for Test Site, LOD Lab 317 took 1.9241118431091309s
Amount of data | Number of property check for Test Site, LOD Lab 317 took 1.7341806888580322s
Understandability | Number of label check for Test Site, LOD Lab 317 took 1.96978759765625s
Understandability | URI regex check for Test Site, LOD Lab 317 took 3.249748945236206s
Understandability | Vocabs check for Test Site, LOD Lab 317 took 1.6275358200073242s
Verifiability | Authors check for Test Site, LOD Lab 317 took 1.8465297222137451s
Verifiability | Publishers check for Test Site, LOD Lab 317 took 1.6221823692321777s
Performance | Throughput check for Test Site, LOD Lab 317 took 16.06044316291809s
Amount of data | Check the number of entities for Test Site, LOD Lab 317 took 8.654594421386719e-05s
Verifiability | Contribs. check for Test Site, LOD Lab 317 took 1.633791446685791s
Interlinking | sameAs chians check for Test Site, LOD Lab 317 took 1.6270060539245605s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.758720874786377s
Interlinking | skos check for Test Site, LOD Lab 317 took 1.6337244510650635s
Timeliness | dataset update frequency check for Test Site, LOD Lab 317 took 1.7400202751159668s
Currency | Creation date check for Test Site, LOD Lab 317 took 3.3485655784606934s
Currency | Modification date check for Test Site, LOD Lab 317 took 3.3092525005340576s
Rep.Conc. | URIs length for Test Site, LOD Lab 317 took 33.6071412563324s
Interoperability | New vocabularies check for Test Site, LOD Lab 317 took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for Test Site, LOD Lab 317 took 1.6807677745819092s
Accuracy | Check Functional Property for Test Site, LOD Lab 317 took 1.6090786457061768s
Accuracy | Check Inverse Functional Property for Test Site, LOD Lab 317 took 1.629401683807373s
Accuracy | Check Empty annotation labels for Test Site, LOD Lab 317 took 3.2176530361175537s
Accuracy | Check White space in annotation for Test Site, LOD Lab 317 took 0.0302431583404541s
Accuracy | Check Datatype consistency for Test Site, LOD Lab 317 took 0.027513980865478516s
Consistency | Disjoint class check for Test Site, LOD Lab 317 took 1.628246545791626s
Consistency | Check Misplaced properties for Test Site, LOD Lab 317 took 23.70899534225464s
Consistency | Misplaced classes for Test Site, LOD Lab 317 took 2.060542106628418s
Consistency | Check Ontology hijacking for Test Site, LOD Lab 317 took 5.1167449951171875s
Consistency | Check Invalid usage of undefined classes for Test Site, LOD Lab 317 took 1.364058256149292s
Consistency | Check Invalid usage of undefined properties for Test Site, LOD Lab 317 took 22.658549308776855s
Conciseness | Check Extensional conciseness for Test Site, LOD Lab 317 took 0.031130313873291016s
Conciseness | Check Intensional conciseness for Test Site, LOD Lab 317 took 2.198446750640869s
Security | Sign check for Test Site, LOD Lab 317 took 1.8150794506072998s
Availability | Check URIs Dereferenciability for Test Site, LOD Lab 317 took 14.352968215942383s
Completeness | Calculation of interlinking completeness for Test Site, LOD Lab 317 took 0.23977875709533691s
Reputation | Calculation of the PageRank for Test Site, LOD Lab 317 took 0.02308177947998047s
Interlinking | Calculation of Degree of Connection for Test Site, LOD Lab 317 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Test Site, LOD Lab 317 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Test Site, LOD Lab 317 took 4.792213439941406e-05s
Interoperability | Check the re-using of existing vocabs for Test Site, LOD Lab 317 took 1.430511474609375e-06s
Believability | Calculation of trust value for Test Site, LOD Lab 317 took 1.1682510375976562e-05s
INFO | --- Analysis for iislod-test took 506.8656892776489s
Availability | SPARQL endpoint availability check for Interpretation of Land Use Data in Ordos City took 4.0531158447265625e-05s
Availability | VoID file availability check for Interpretation of Land Use Data in Ordos City took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Interpretation of Land Use Data in Ordos City took 0.18657708168029785s
Reputation | Calculation of the PageRank for Interpretation of Land Use Data in Ordos City took 0.02006220817565918s
Interlinking | Calculation of Degree of Connection for Interpretation of Land Use Data in Ordos City took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Interpretation of Land Use Data in Ordos City took 0.0006794929504394531s
Interlinking | Calculation of Clustering coefficient for Interpretation of Land Use Data in Ordos City took 2.7179718017578125e-05s
Believability | Calculation of trust value for Interpretation of Land Use Data in Ordos City took 1.1920928955078125e-05s
INFO | --- Analysis for ILUSOC took 1.9830024242401123s
Availability | SPARQL endpoint availability check for im@sparql took 8.225440979003906e-05s
Availability | VoID file availability check for im@sparql took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for im@sparql took 0.17385196685791016s
Reputation | Calculation of the PageRank for im@sparql took 0.020089387893676758s
Interlinking | Calculation of Degree of Connection for im@sparql took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for im@sparql took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for im@sparql took 2.7894973754882812e-05s
Believability | Calculation of trust value for im@sparql took 1.2874603271484375e-05s
INFO | --- Analysis for im@sparql took 1.944153070449829s
Availability | SPARQL endpoint availability check for imagery bailingniao took 3.981590270996094e-05s
Availability | VoID file availability check for imagery bailingniao took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for imagery bailingniao took 0.1729600429534912s
Reputation | Calculation of the PageRank for imagery bailingniao took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for imagery bailingniao took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for imagery bailingniao took 0.0006864070892333984s
Interlinking | Calculation of Clustering coefficient for imagery bailingniao took 2.6464462280273438e-05s
Believability | Calculation of trust value for imagery bailingniao took 1.1682510375976562e-05s
INFO | --- Analysis for imagery_bailingniao took 1.972287654876709s
Availability | SPARQL endpoint availability check for Imagesnippets Image Descriptions took 3.790855407714844e-05s
Availability | VoID file availability check for Imagesnippets Image Descriptions took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Imagesnippets Image Descriptions took 0.1734180450439453s
Reputation | Calculation of the PageRank for Imagesnippets Image Descriptions took 0.020486116409301758s
Interlinking | Calculation of Degree of Connection for Imagesnippets Image Descriptions took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Imagesnippets Image Descriptions took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Imagesnippets Image Descriptions took 8.58306884765625e-05s
Believability | Calculation of trust value for Imagesnippets Image Descriptions took 1.1444091796875e-05s
INFO | --- Analysis for imagesnippets took 1.9651765823364258s
Availability | SPARQL endpoint availability check for International Monetary Fund (IMF) Linked Data took 4.4345855712890625e-05s
Availability | VoID file availability check for International Monetary Fund (IMF) Linked Data took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for International Monetary Fund (IMF) Linked Data took 0.18768835067749023s
Reputation | Calculation of the PageRank for International Monetary Fund (IMF) Linked Data took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for International Monetary Fund (IMF) Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for International Monetary Fund (IMF) Linked Data took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for International Monetary Fund (IMF) Linked Data took 8.463859558105469e-05s
Believability | Calculation of trust value for International Monetary Fund (IMF) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for imf-linked-data took 1.9671807289123535s
Availability | SPARQL endpoint availability check for IMGpedia took 8.320808410644531e-05s
Availability | VoID file availability check for IMGpedia took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for IMGpedia took 0.17557716369628906s
Reputation | Calculation of the PageRank for IMGpedia took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for IMGpedia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for IMGpedia took 0.000827789306640625s
Interlinking | Calculation of Clustering coefficient for IMGpedia took 3.0994415283203125e-05s
Believability | Calculation of trust value for IMGpedia took 1.1444091796875e-05s
INFO | --- Analysis for imgpedia took 1.9639203548431396s
Availability | SPARQL endpoint availability check for Import Status of GMO Crops took 0.00011205673217773438s
Availability | VoID file availability check for Import Status of GMO Crops took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Import Status of GMO Crops took 0.17889809608459473s
Reputation | Calculation of the PageRank for Import Status of GMO Crops took 0.02271246910095215s
Interlinking | Calculation of Degree of Connection for Import Status of GMO Crops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Import Status of GMO Crops took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for Import Status of GMO Crops took 2.86102294921875e-05s
Believability | Calculation of trust value for Import Status of GMO Crops took 1.049041748046875e-05s
INFO | --- Analysis for import-status-of-gmo-crops took 1.955357551574707s
Availability | SPARQL endpoint availability check for MD Imtiaz Ahammad took 8.273124694824219e-05s
Availability | VoID file availability check for MD Imtiaz Ahammad took 0.0002307891845703125s
Completeness | Calculation of interlinking completeness for MD Imtiaz Ahammad took 0.18174052238464355s
Reputation | Calculation of the PageRank for MD Imtiaz Ahammad took 0.0214996337890625s
Interlinking | Calculation of Degree of Connection for MD Imtiaz Ahammad took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for MD Imtiaz Ahammad took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for MD Imtiaz Ahammad took 1.1682510375976562e-05s
Believability | Calculation of trust value for MD Imtiaz Ahammad took 1.239776611328125e-05s
INFO | --- Analysis for Imtiaz took 2.055680751800537s
Availability | SPARQL endpoint availability check for Royalty Free Music took 8.630752563476562e-05s
Availability | VoID file availability check for Royalty Free Music took 0.00025153160095214844s
Completeness | Calculation of interlinking completeness for Royalty Free Music took 0.17194485664367676s
Reputation | Calculation of the PageRank for Royalty Free Music took 0.0201108455657959s
Interlinking | Calculation of Degree of Connection for Royalty Free Music took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Royalty Free Music took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Royalty Free Music took 2.765655517578125e-05s
Believability | Calculation of trust value for Royalty Free Music took 5.7220458984375e-06s
INFO | --- Analysis for inaudio.org took 1.9913439750671387s
Availability | SPARQL endpoint availability check for Income and production cost of grape by year took 4.0531158447265625e-05s
Availability | VoID file availability check for Income and production cost of grape by year took 0.00025200843811035156s
Completeness | Calculation of interlinking completeness for Income and production cost of grape by year took 0.17647004127502441s
Reputation | Calculation of the PageRank for Income and production cost of grape by year took 0.020026683807373047s
Interlinking | Calculation of Degree of Connection for Income and production cost of grape by year took 1.8596649169921875e-05s
Interlinking | Calculation of Centrality for Income and production cost of grape by year took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Income and production cost of grape by year took 2.7894973754882812e-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 1.9481432437896729s
Availability | SPARQL endpoint availability check for Income and production cost of pear by year took 3.981590270996094e-05s
Availability | VoID file availability check for Income and production cost of pear by year took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Income and production cost of pear by year took 0.1759638786315918s
Reputation | Calculation of the PageRank for Income and production cost of pear by year took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Income and production cost of pear by year took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Income and production cost of pear by year took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Income and production cost of pear by year took 2.8371810913085938e-05s
Believability | Calculation of trust value for Income and production cost of pear by year took 7.3909759521484375e-06s
INFO | --- Analysis for income-and-production-cost-of-pear-by-year took 1.9436540603637695s
Availability | SPARQL endpoint availability check for Index Thomisticus Treebank in LiLa took 4.029273986816406e-05s
Availability | VoID file availability check for Index Thomisticus Treebank in LiLa took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for Index Thomisticus Treebank in LiLa took 0.17277264595031738s
Reputation | Calculation of the PageRank for Index Thomisticus Treebank in LiLa took 0.02057957649230957s
Interlinking | Calculation of Degree of Connection for Index Thomisticus Treebank in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Index Thomisticus Treebank in LiLa took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Index Thomisticus Treebank in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Index Thomisticus Treebank in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for IndexThomisticusTreebank took 1.9415841102600098s
Availability | SPARQL endpoint availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 3.981590270996094e-05s
Availability | VoID file availability check for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0002765655517578125s
Completeness | Calculation of interlinking completeness for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.1694936752319336s
Reputation | Calculation of the PageRank for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.02016925811767578s
Interlinking | Calculation of Degree of Connection for INERTIA (INERTIA Energy Consumption Example Linked Data) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for INERTIA (INERTIA Energy Consumption Example Linked Data) took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for INERTIA (INERTIA Energy Consumption Example Linked Data) took 2.8133392333984375e-05s
Believability | Calculation of trust value for INERTIA (INERTIA Energy Consumption Example Linked Data) took 7.3909759521484375e-06s
INFO | --- Analysis for inertia-energy-consumption-example-linked-data took 1.9229183197021484s
Availability | SPARQL endpoint availability check for IneveryCREA, la comunidad de la creatividad educativa took 5.125999450683594e-05s
Availability | VoID file availability check for IneveryCREA, la comunidad de la creatividad educativa took 0.0002665519714355469s
Completeness | Calculation of interlinking completeness for IneveryCREA, la comunidad de la creatividad educativa took 0.17799162864685059s
Reputation | Calculation of the PageRank for IneveryCREA, la comunidad de la creatividad educativa took 0.020220279693603516s
Interlinking | Calculation of Degree of Connection for IneveryCREA, la comunidad de la creatividad educativa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for IneveryCREA, la comunidad de la creatividad educativa took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for IneveryCREA, la comunidad de la creatividad educativa took 9.846687316894531e-05s
Believability | Calculation of trust value for IneveryCREA, la comunidad de la creatividad educativa took 7.867813110351562e-06s
INFO | --- Analysis for ineverycrea took 1.9540038108825684s
Availability | SPARQL endpoint availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 6.771087646484375e-05s
Availability | VoID file availability check for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.00032019615173339844s
Completeness | Calculation of interlinking completeness for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.1704871654510498s
Reputation | Calculation of the PageRank for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for IneveryCREA Argentina, la comunidad de la creatividad educativa took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for IneveryCREA Argentina, la comunidad de la creatividad educativa took 8.749961853027344e-05s
Believability | Calculation of trust value for IneveryCREA Argentina, la comunidad de la creatividad educativa took 7.62939453125e-06s
INFO | --- Analysis for ineverycrea-argentina took 1.9604027271270752s
Availability | SPARQL endpoint availability check for Influence Tracker Dataset took 4.0531158447265625e-05s
Availability | VoID file availability check for Influence Tracker Dataset took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Influence Tracker Dataset took 0.17419791221618652s
Reputation | Calculation of the PageRank for Influence Tracker Dataset took 0.02027130126953125s
Interlinking | Calculation of Degree of Connection for Influence Tracker Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Influence Tracker Dataset took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Influence Tracker Dataset took 6.4849853515625e-05s
Believability | Calculation of trust value for Influence Tracker Dataset took 7.152557373046875e-06s
INFO | --- Analysis for influence-tracker-dataset took 1.923065185546875s
Availability | SPARQL endpoint availability check for INSEMTIVES took 3.9577484130859375e-05s
Availability | VoID file availability check for INSEMTIVES took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for INSEMTIVES took 0.20967769622802734s
Reputation | Calculation of the PageRank for INSEMTIVES took 0.020119428634643555s
Interlinking | Calculation of Degree of Connection for INSEMTIVES took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for INSEMTIVES took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for INSEMTIVES took 2.8371810913085938e-05s
Believability | Calculation of trust value for INSEMTIVES took 7.3909759521484375e-06s
INFO | --- Analysis for insemtives took 1.9880783557891846s
Availability | SPARQL endpoint availability check for instagram.person took 8.416175842285156e-05s
Availability | VoID file availability check for instagram.person took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for instagram.person took 0.17407846450805664s
Reputation | Calculation of the PageRank for instagram.person took 0.02021336555480957s
Interlinking | Calculation of Degree of Connection for instagram.person took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for instagram.person took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for instagram.person took 2.8371810913085938e-05s
Believability | Calculation of trust value for instagram.person took 1.2159347534179688e-05s
INFO | --- Analysis for instagram_person took 1.9926197528839111s
Availability | SPARQL endpoint availability check for instagram.videoobject took 8.440017700195312e-05s
Availability | VoID file availability check for instagram.videoobject took 0.0005905628204345703s
Completeness | Calculation of interlinking completeness for instagram.videoobject took 0.17828679084777832s
Reputation | Calculation of the PageRank for instagram.videoobject took 0.020385026931762695s
Interlinking | Calculation of Degree of Connection for instagram.videoobject took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for instagram.videoobject took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for instagram.videoobject took 3.147125244140625e-05s
Believability | Calculation of trust value for instagram.videoobject took 1.2874603271484375e-05s
INFO | --- Analysis for instagram_videoobject took 2.0021657943725586s
Availability | SPARQL endpoint availability check for Instance Hub Countries took 8.440017700195312e-05s
Availability | VoID file availability check for Instance Hub Countries took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for Instance Hub Countries took 0.1803147792816162s
Reputation | Calculation of the PageRank for Instance Hub Countries took 0.02193164825439453s
Interlinking | Calculation of Degree of Connection for Instance Hub Countries took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub Countries took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Instance Hub Countries took 2.9087066650390625e-05s
Believability | Calculation of trust value for Instance Hub Countries took 1.2159347534179688e-05s
INFO | --- Analysis for instance-hub-countries took 1.9970242977142334s
Availability | SPARQL endpoint availability check for Instance Hub Fiscal Years took 7.939338684082031e-05s
Availability | VoID file availability check for Instance Hub Fiscal Years took 0.000457763671875s
Completeness | Calculation of interlinking completeness for Instance Hub Fiscal Years took 0.17589974403381348s
Reputation | Calculation of the PageRank for Instance Hub Fiscal Years took 0.020798444747924805s
Interlinking | Calculation of Degree of Connection for Instance Hub Fiscal Years took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Instance Hub Fiscal Years took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Instance Hub Fiscal Years took 2.8848648071289062e-05s
Believability | Calculation of trust value for Instance Hub Fiscal Years took 1.0251998901367188e-05s
INFO | --- Analysis for instance-hub-fiscal-years took 1.9622137546539307s
Availability | SPARQL endpoint availability check for Instance Hub Organizations took 7.748603820800781e-05s
Availability | VoID file availability check for Instance Hub Organizations took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Instance Hub Organizations took 0.17154359817504883s
Reputation | Calculation of the PageRank for Instance Hub Organizations took 0.020569801330566406s
Interlinking | Calculation of Degree of Connection for Instance Hub Organizations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub Organizations took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Instance Hub Organizations took 3.123283386230469e-05s
Believability | Calculation of trust value for Instance Hub Organizations took 1.4543533325195312e-05s
INFO | --- Analysis for instance-hub-organizations took 1.98280668258667s
Availability | SPARQL endpoint availability check for Instance Hub People took 8.249282836914062e-05s
Availability | VoID file availability check for Instance Hub People took 0.0005249977111816406s
Completeness | Calculation of interlinking completeness for Instance Hub People took 0.17980051040649414s
Reputation | Calculation of the PageRank for Instance Hub People took 0.021808385848999023s
Interlinking | Calculation of Degree of Connection for Instance Hub People took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Instance Hub People took 0.0006933212280273438s
Interlinking | Calculation of Clustering coefficient for Instance Hub People took 3.361701965332031e-05s
Believability | Calculation of trust value for Instance Hub People took 1.3113021850585938e-05s
INFO | --- Analysis for instance-hub-people took 2.0112733840942383s
Availability | SPARQL endpoint availability check for Instance Hub US Civil Servants took 5.602836608886719e-05s
Availability | VoID file availability check for Instance Hub US Civil Servants took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Instance Hub US Civil Servants took 0.18561458587646484s
Reputation | Calculation of the PageRank for Instance Hub US Civil Servants took 0.020244359970092773s
Interlinking | Calculation of Degree of Connection for Instance Hub US Civil Servants took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Instance Hub US Civil Servants took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Civil Servants took 3.24249267578125e-05s
Believability | Calculation of trust value for Instance Hub US Civil Servants took 8.106231689453125e-06s
INFO | --- Analysis for instance-hub-us-civil-servants took 2.0400681495666504s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Committees took 5.1975250244140625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Committees took 0.0005366802215576172s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Committees took 0.17464590072631836s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Committees took 0.021791934967041016s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Committees took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Committees took 0.0008673667907714844s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Committees took 3.647804260253906e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Committees took 1.2159347534179688e-05s
INFO | --- Analysis for instance-hub-us-congressional-committees took 2.0584075450897217s
Availability | SPARQL endpoint availability check for Instance Hub US Congressional Districts took 3.910064697265625e-05s
Availability | VoID file availability check for Instance Hub US Congressional Districts took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Instance Hub US Congressional Districts took 0.18060946464538574s
Reputation | Calculation of the PageRank for Instance Hub US Congressional Districts took 0.021257400512695312s
Interlinking | Calculation of Degree of Connection for Instance Hub US Congressional Districts took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Congressional Districts took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Congressional Districts took 3.147125244140625e-05s
Believability | Calculation of trust value for Instance Hub US Congressional Districts took 1.3113021850585938e-05s
INFO | --- Analysis for instance-hub-us-congressional-districts took 2.0295891761779785s
Availability | SPARQL endpoint availability check for Instance Hub US Crops took 9.751319885253906e-05s
Availability | VoID file availability check for Instance Hub US Crops took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Instance Hub US Crops took 0.18671059608459473s
Reputation | Calculation of the PageRank for Instance Hub US Crops took 0.020537376403808594s
Interlinking | Calculation of Degree of Connection for Instance Hub US Crops took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Instance Hub US Crops took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Crops took 3.0279159545898438e-05s
Believability | Calculation of trust value for Instance Hub US Crops took 7.62939453125e-06s
INFO | --- Analysis for instance-hub-us-crops took 2.0028438568115234s
Availability | SPARQL endpoint availability check for Instance Hub US Federal Agencies took 8.392333984375e-05s
Availability | VoID file availability check for Instance Hub US Federal Agencies took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Instance Hub US Federal Agencies took 0.18259310722351074s
Reputation | Calculation of the PageRank for Instance Hub US Federal Agencies took 0.021111011505126953s
Interlinking | Calculation of Degree of Connection for Instance Hub US Federal Agencies took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Instance Hub US Federal Agencies took 0.0008282661437988281s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Federal Agencies took 3.743171691894531e-05s
Believability | Calculation of trust value for Instance Hub US Federal Agencies took 1.2636184692382812e-05s
INFO | --- Analysis for instance-hub-us-federal-agencies took 1.997049331665039s
Availability | SPARQL endpoint availability check for Instance Hub US States and Territories took 8.344650268554688e-05s
Availability | VoID file availability check for Instance Hub US States and Territories took 0.0005121231079101562s
Completeness | Calculation of interlinking completeness for Instance Hub US States and Territories took 0.17623090744018555s
Reputation | Calculation of the PageRank for Instance Hub US States and Territories took 0.0205228328704834s
Interlinking | Calculation of Degree of Connection for Instance Hub US States and Territories took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Instance Hub US States and Territories took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Instance Hub US States and Territories took 3.218650817871094e-05s
Believability | Calculation of trust value for Instance Hub US States and Territories took 1.2874603271484375e-05s
INFO | --- Analysis for instance-hub-us-states-and-territories took 1.9635024070739746s
Availability | SPARQL endpoint availability check for Instance Hub US Toxic Chemicals took 4.839897155761719e-05s
Availability | VoID file availability check for Instance Hub US Toxic Chemicals took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Instance Hub US Toxic Chemicals took 0.17993569374084473s
Reputation | Calculation of the PageRank for Instance Hub US Toxic Chemicals took 0.020430326461791992s
Interlinking | Calculation of Degree of Connection for Instance Hub US Toxic Chemicals took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Instance Hub US Toxic Chemicals took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Instance Hub US Toxic Chemicals took 3.1948089599609375e-05s
Believability | Calculation of trust value for Instance Hub US Toxic Chemicals took 1.239776611328125e-05s
INFO | --- Analysis for instance-hub-us-toxic-chemicals took 1.9733567237854004s
Availability | SPARQL endpoint availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 5.555152893066406e-05s
Availability | VoID file availability check for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.1796433925628662s
Reputation | Calculation of the PageRank for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.020411968231201172s
Interlinking | Calculation of Degree of Connection for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 3.1948089599609375e-05s
Believability | Calculation of trust value for Integrated Human Geography Service for LOD by National Geographic Information Institute, Korea took 1.33514404296875e-05s
INFO | --- Analysis for integrated-human-geography-service-for-lod took 1.977095365524292s
Availability | SPARQL endpoint availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 4.0531158447265625e-05s
Availability | VoID file availability check for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.17581653594970703s
Reputation | Calculation of the PageRank for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Interactive Maps, a collection of interactive flash maps (GNOSS) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Interactive Maps, a collection of interactive flash maps (GNOSS) took 0.00010037422180175781s
Believability | Calculation of trust value for Interactive Maps, a collection of interactive flash maps (GNOSS) took 1.3113021850585938e-05s
INFO | --- Analysis for interactivemaps-gnoss took 1.9713034629821777s
Availability | SPARQL endpoint availability check for Interakce mezi účinnými látkami took 8.797645568847656e-05s
Availability | VoID file availability check for Interakce mezi účinnými látkami took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Interakce mezi účinnými látkami took 0.17319941520690918s
Reputation | Calculation of the PageRank for Interakce mezi účinnými látkami took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for Interakce mezi účinnými látkami took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Interakce mezi účinnými látkami took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Interakce mezi účinnými látkami took 3.147125244140625e-05s
Believability | Calculation of trust value for Interakce mezi účinnými látkami took 1.33514404296875e-05s
INFO | --- Analysis for interakce-mezi---inn-mi-l-tkami took 1.9586308002471924s
Availability | SPARQL endpoint availability check for intervalue took 4.100799560546875e-05s
Availability | VoID file availability check for intervalue took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for intervalue took 0.17970585823059082s
Reputation | Calculation of the PageRank for intervalue took 0.020453453063964844s
Interlinking | Calculation of Degree of Connection for intervalue took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for intervalue took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for intervalue took 6.699562072753906e-05s
Believability | Calculation of trust value for intervalue took 1.2159347534179688e-05s
INFO | --- Analysis for intervalue took 2.0221893787384033s
Availability | SPARQL endpoint availability check for Inztrow took 8.559226989746094e-05s
Availability | VoID file availability check for Inztrow took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Inztrow took 0.17493748664855957s
Reputation | Calculation of the PageRank for Inztrow took 0.020162105560302734s
Interlinking | Calculation of Degree of Connection for Inztrow took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Inztrow took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Inztrow took 2.9087066650390625e-05s
Believability | Calculation of trust value for Inztrow took 1.239776611328125e-05s
INFO | --- Analysis for Inztrow took 2.014309883117676s
Availability | SPARQL endpoint availability check for IPBES Assessments Ontology took 8.535385131835938e-05s
Availability | VoID file availability check for IPBES Assessments Ontology took 0.00048041343688964844s
Completeness | Calculation of interlinking completeness for IPBES Assessments Ontology took 0.1733684539794922s
Reputation | Calculation of the PageRank for IPBES Assessments Ontology took 0.02255415916442871s
Interlinking | Calculation of Degree of Connection for IPBES Assessments Ontology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for IPBES Assessments Ontology took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for IPBES Assessments Ontology took 2.86102294921875e-05s
Believability | Calculation of trust value for IPBES Assessments Ontology took 1.1920928955078125e-05s
INFO | --- Analysis for ipbes took 1.9865303039550781s
Availability | SPARQL endpoint availability check for IPTC NewsCodes took 4.0531158447265625e-05s
Availability | VoID file availability check for IPTC NewsCodes took 0.0002391338348388672s
Completeness | Calculation of interlinking completeness for IPTC NewsCodes took 0.1729412078857422s
Reputation | Calculation of the PageRank for IPTC NewsCodes took 0.020807504653930664s
Interlinking | Calculation of Degree of Connection for IPTC NewsCodes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IPTC NewsCodes took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for IPTC NewsCodes took 4.172325134277344e-05s
Believability | Calculation of trust value for IPTC NewsCodes took 7.62939453125e-06s
INFO | --- Analysis for iptc-newscodes took 1.9635193347930908s
Availability | SPARQL endpoint availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 4.124641418457031e-05s
Availability | VoID file availability check for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.17539072036743164s
Reputation | Calculation of the PageRank for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for Irstea Weather Dataset of the Montoldre Experimental Farm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Irstea Weather Dataset of the Montoldre Experimental Farm took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Irstea Weather Dataset of the Montoldre Experimental Farm took 2.86102294921875e-05s
Believability | Calculation of trust value for Irstea Weather Dataset of the Montoldre Experimental Farm took 1.3113021850585938e-05s
INFO | --- Analysis for irstea-weather-dataset-of-the-montoldre-experimental-farm took 1.9611525535583496s
Availability | SPARQL endpoint availability check for iServe: Linked Services Registry took 4.0531158447265625e-05s
Availability | VoID file availability check for iServe: Linked Services Registry took 0.0005323886871337891s
Completeness | Calculation of interlinking completeness for iServe: Linked Services Registry took 0.18846893310546875s
Reputation | Calculation of the PageRank for iServe: Linked Services Registry took 0.021149635314941406s
Interlinking | Calculation of Degree of Connection for iServe: Linked Services Registry took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for iServe: Linked Services Registry took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for iServe: Linked Services Registry took 9.584426879882812e-05s
Believability | Calculation of trust value for iServe: Linked Services Registry took 1.0967254638671875e-05s
INFO | --- Analysis for iserve took 2.0270752906799316s
Availability | SPARQL endpoint availability check for ISIC V4 took 8.440017700195312e-05s
Availability | VoID file availability check for ISIC V4 took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for ISIC V4 took 0.18012714385986328s
Reputation | Calculation of the PageRank for ISIC V4 took 0.020091533660888672s
Interlinking | Calculation of Degree of Connection for ISIC V4 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ISIC V4 took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for ISIC V4 took 3.3855438232421875e-05s
Believability | Calculation of trust value for ISIC V4 took 1.1682510375976562e-05s
INFO | --- Analysis for isic-v4 took 1.976940393447876s
Availability | SPARQL endpoint availability check for Isidore took 8.249282836914062e-05s
Availability | VoID file availability check for Isidore took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for Isidore took 0.18253064155578613s
Reputation | Calculation of the PageRank for Isidore took 0.022731304168701172s
Interlinking | Calculation of Degree of Connection for Isidore took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Isidore took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Isidore took 3.075599670410156e-05s
Believability | Calculation of trust value for Isidore took 1.0967254638671875e-05s
INFO | --- Analysis for isidore took 1.9892561435699463s
Availability | SPARQL endpoint availability check for ISIL->DBpedia took 8.225440979003906e-05s
Availability | VoID file availability check for ISIL->DBpedia took 0.0005202293395996094s
Completeness | Calculation of interlinking completeness for ISIL->DBpedia took 0.17906832695007324s
Reputation | Calculation of the PageRank for ISIL->DBpedia took 0.020358562469482422s
Interlinking | Calculation of Degree of Connection for ISIL->DBpedia took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for ISIL->DBpedia took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for ISIL->DBpedia took 6.532669067382812e-05s
Believability | Calculation of trust value for ISIL->DBpedia took 1.1682510375976562e-05s
INFO | --- Analysis for isil-dbpedia took 1.9457669258117676s
Availability | SPARQL endpoint availability check for Linked ISO 3166-2 Data took 8.296966552734375e-05s
Availability | VoID file availability check for Linked ISO 3166-2 Data took 0.0005030632019042969s
Completeness | Calculation of interlinking completeness for Linked ISO 3166-2 Data took 0.18016624450683594s
Reputation | Calculation of the PageRank for Linked ISO 3166-2 Data took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for Linked ISO 3166-2 Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked ISO 3166-2 Data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Linked ISO 3166-2 Data took 2.765655517578125e-05s
Believability | Calculation of trust value for Linked ISO 3166-2 Data took 1.0967254638671875e-05s
INFO | --- Analysis for iso-3166-2-data took 1.973949670791626s
Availability | SPARQL endpoint availability check for Published subjects for languages in ISO 639 took 3.9577484130859375e-05s
Availability | VoID file availability check for Published subjects for languages in ISO 639 took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Published subjects for languages in ISO 639 took 0.18157029151916504s
Reputation | Calculation of the PageRank for Published subjects for languages in ISO 639 took 0.022815465927124023s
Interlinking | Calculation of Degree of Connection for Published subjects for languages in ISO 639 took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Published subjects for languages in ISO 639 took 0.0008344650268554688s
Interlinking | Calculation of Clustering coefficient for Published subjects for languages in ISO 639 took 3.886222839355469e-05s
Believability | Calculation of trust value for Published subjects for languages in ISO 639 took 1.1920928955078125e-05s
INFO | --- Analysis for iso-639-oasis took 1.9963300228118896s
Availability | SPARQL endpoint availability check for ISOcat took 0.00010228157043457031s
Availability | VoID file availability check for ISOcat took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for ISOcat took 0.18402695655822754s
Reputation | Calculation of the PageRank for ISOcat took 0.022631168365478516s
Interlinking | Calculation of Degree of Connection for ISOcat took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISOcat took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for ISOcat took 5.8650970458984375e-05s
Believability | Calculation of trust value for ISOcat took 1.239776611328125e-05s
INFO | --- Analysis for isocat took 2.062209367752075s
Availability | SPARQL endpoint availability check for ISOcat-metadata took 3.981590270996094e-05s
Availability | VoID file availability check for ISOcat-metadata took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for ISOcat-metadata took 0.18273615837097168s
Reputation | Calculation of the PageRank for ISOcat-metadata took 0.0209958553314209s
Interlinking | Calculation of Degree of Connection for ISOcat-metadata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ISOcat-metadata took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for ISOcat-metadata took 3.314018249511719e-05s
Believability | Calculation of trust value for ISOcat-metadata took 1.33514404296875e-05s
INFO | --- Analysis for isocat-metadata took 1.9736175537109375s
Availability | SPARQL endpoint availability check for ISPRA - Mitigation measures in Italy for national soil protection took 9.965896606445312e-05s
Availability | VoID file availability check for ISPRA - Mitigation measures in Italy for national soil protection took 0.000514984130859375s
Completeness | Calculation of interlinking completeness for ISPRA - Mitigation measures in Italy for national soil protection took 0.18045592308044434s
Reputation | Calculation of the PageRank for ISPRA - Mitigation measures in Italy for national soil protection took 0.02189946174621582s
Interlinking | Calculation of Degree of Connection for ISPRA - Mitigation measures in Italy for national soil protection took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ISPRA - Mitigation measures in Italy for national soil protection took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for ISPRA - Mitigation measures in Italy for national soil protection took 3.5762786865234375e-05s
Believability | Calculation of trust value for ISPRA - Mitigation measures in Italy for national soil protection took 7.62939453125e-06s
INFO | --- Analysis for ispra-lod-ihi took 1.9919638633728027s
Availability | SPARQL endpoint availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 4.00543212890625e-05s
Availability | VoID file availability check for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.17853832244873047s
Reputation | Calculation of the PageRank for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for ISPRA - The administrative divisions of Italy (regions/provinces/municipalities) took 9.036064147949219e-05s
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 1.9734926223754883s
Availability | SPARQL endpoint availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 8.225440979003906e-05s
Availability | VoID file availability check for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.18320155143737793s
Reputation | Calculation of the PageRank for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.020821332931518555s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian National Tide Gauge Network (RMN) took 0.0008075237274169922s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian National Tide Gauge Network (RMN) took 3.5762786865234375e-05s
Believability | Calculation of trust value for ISPRA - The Italian National Tide Gauge Network (RMN) took 1.2874603271484375e-05s
INFO | --- Analysis for ispra-lod-rmn took 2.0014050006866455s
Availability | SPARQL endpoint availability check for ISPRA - The Italian Data Buoy Network (RON) took 8.96453857421875e-05s
Availability | VoID file availability check for ISPRA - The Italian Data Buoy Network (RON) took 0.00024056434631347656s
Completeness | Calculation of interlinking completeness for ISPRA - The Italian Data Buoy Network (RON) took 0.18216848373413086s
Reputation | Calculation of the PageRank for ISPRA - The Italian Data Buoy Network (RON) took 0.020766735076904297s
Interlinking | Calculation of Degree of Connection for ISPRA - The Italian Data Buoy Network (RON) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISPRA - The Italian Data Buoy Network (RON) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for ISPRA - The Italian Data Buoy Network (RON) took 3.361701965332031e-05s
Believability | Calculation of trust value for ISPRA - The Italian Data Buoy Network (RON) took 1.33514404296875e-05s
INFO | --- Analysis for ispra-lod-ron took 1.969153881072998s
Availability | SPARQL endpoint availability check for ISPRA - Soil Consumption Indicators in Italy took 8.320808410644531e-05s
Availability | VoID file availability check for ISPRA - Soil Consumption Indicators in Italy took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for ISPRA - Soil Consumption Indicators in Italy took 0.19173216819763184s
Reputation | Calculation of the PageRank for ISPRA - Soil Consumption Indicators in Italy took 0.021805524826049805s
Interlinking | Calculation of Degree of Connection for ISPRA - Soil Consumption Indicators in Italy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ISPRA - Soil Consumption Indicators in Italy took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for ISPRA - Soil Consumption Indicators in Italy took 3.123283386230469e-05s
Believability | Calculation of trust value for ISPRA - Soil Consumption Indicators in Italy took 1.3589859008789062e-05s
INFO | --- Analysis for ispra-lod-sc took 1.9944117069244385s
Availability | SPARQL endpoint availability check for ISSA Agritrop Dataset took 8.344650268554688e-05s
Availability | VoID file availability check for ISSA Agritrop Dataset took 0.0005168914794921875s
Completeness | Calculation of interlinking completeness for ISSA Agritrop Dataset took 0.17438077926635742s
Reputation | Calculation of the PageRank for ISSA Agritrop Dataset took 0.020309925079345703s
Interlinking | Calculation of Degree of Connection for ISSA Agritrop Dataset took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for ISSA Agritrop Dataset took 0.0009284019470214844s
Interlinking | Calculation of Clustering coefficient for ISSA Agritrop Dataset took 0.00010395050048828125s
Believability | Calculation of trust value for ISSA Agritrop Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for issa-agritrop took 2.029385805130005s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 8.916854858398438e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.18187427520751953s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02004694938659668s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007295608520507812s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 2.7179718017578125e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 7.152557373046875e-06s
INFO | --- Analysis for ISSN:0080-3626 took 2.0057637691497803s
Availability | SPARQL endpoint availability check for Pierwszy polski podręcznik bibliotekarski took 4.220008850097656e-05s
Availability | VoID file availability check for Pierwszy polski podręcznik bibliotekarski took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Pierwszy polski podręcznik bibliotekarski took 0.17573952674865723s
Reputation | Calculation of the PageRank for Pierwszy polski podręcznik bibliotekarski took 0.02280449867248535s
Interlinking | Calculation of Degree of Connection for Pierwszy polski podręcznik bibliotekarski took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Pierwszy polski podręcznik bibliotekarski took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Pierwszy polski podręcznik bibliotekarski took 3.2901763916015625e-05s
Believability | Calculation of trust value for Pierwszy polski podręcznik bibliotekarski took 1.2159347534179688e-05s
INFO | --- Analysis for ISSN:_0080-3626 took 1.9704699516296387s
Availability | SPARQL endpoint availability check for Aktualne zagadnienia klasyfikacji map took 5.3882598876953125e-05s
Availability | VoID file availability check for Aktualne zagadnienia klasyfikacji map took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Aktualne zagadnienia klasyfikacji map took 0.17804265022277832s
Reputation | Calculation of the PageRank for Aktualne zagadnienia klasyfikacji map took 0.020250320434570312s
Interlinking | Calculation of Degree of Connection for Aktualne zagadnienia klasyfikacji map took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Aktualne zagadnienia klasyfikacji map took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Aktualne zagadnienia klasyfikacji map took 3.24249267578125e-05s
Believability | Calculation of trust value for Aktualne zagadnienia klasyfikacji map took 7.62939453125e-06s
INFO | --- Analysis for ISSN:_0080-3626. took 1.9972097873687744s
Availability | SPARQL endpoint availability check for ISTAT Immigration (LinkedOpenData.it) took 8.320808410644531e-05s
Availability | VoID file availability check for ISTAT Immigration (LinkedOpenData.it) took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for ISTAT Immigration (LinkedOpenData.it) took 0.18596220016479492s
Reputation | Calculation of the PageRank for ISTAT Immigration (LinkedOpenData.it) took 0.02067875862121582s
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.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigration (LinkedOpenData.it) took 8.916854858398438e-05s
Believability | Calculation of trust value for ISTAT Immigration (LinkedOpenData.it) took 1.3828277587890625e-05s
INFO | --- Analysis for istat-immigration took 2.0407025814056396s
Availability | SPARQL endpoint availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.00010776519775390625s
Availability | VoID file availability check for ISTAT Immigrazione (Linkedopendata.it) took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for ISTAT Immigrazione (Linkedopendata.it) took 0.1854417324066162s
Reputation | Calculation of the PageRank for ISTAT Immigrazione (Linkedopendata.it) took 0.021920442581176758s
Interlinking | Calculation of Degree of Connection for ISTAT Immigrazione (Linkedopendata.it) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ISTAT Immigrazione (Linkedopendata.it) took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for ISTAT Immigrazione (Linkedopendata.it) took 2.7418136596679688e-05s
Believability | Calculation of trust value for ISTAT Immigrazione (Linkedopendata.it) took 1.239776611328125e-05s
INFO | --- Analysis for istat-immigrazione took 2.00178861618042s
Availability | SPARQL endpoint availability check for List of prices of medicinal products marketed in Italian Republic took 8.392333984375e-05s
Availability | VoID file availability check for List of prices of medicinal products marketed in Italian Republic took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for List of prices of medicinal products marketed in Italian Republic took 0.174241304397583s
Reputation | Calculation of the PageRank for List of prices of medicinal products marketed in Italian Republic took 0.020609617233276367s
Interlinking | Calculation of Degree of Connection for List of prices of medicinal products marketed in Italian Republic took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for List of prices of medicinal products marketed in Italian Republic took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for List of prices of medicinal products marketed in Italian Republic took 2.8133392333984375e-05s
Believability | Calculation of trust value for List of prices of medicinal products marketed in Italian Republic took 1.1920928955078125e-05s
INFO | --- Analysis for it-aifa-drug-prices took 2.0044727325439453s
Availability | SPARQL endpoint availability check for Italian public schools (LinkedOpenData.it) took 3.981590270996094e-05s
Availability | VoID file availability check for Italian public schools (LinkedOpenData.it) took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for Italian public schools (LinkedOpenData.it) took 0.18988704681396484s
Reputation | Calculation of the PageRank for Italian public schools (LinkedOpenData.it) took 0.020693063735961914s
Interlinking | Calculation of Degree of Connection for Italian public schools (LinkedOpenData.it) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Italian public schools (LinkedOpenData.it) took 0.0008697509765625s
Interlinking | Calculation of Clustering coefficient for Italian public schools (LinkedOpenData.it) took 8.106231689453125e-05s
Believability | Calculation of trust value for Italian public schools (LinkedOpenData.it) took 1.33514404296875e-05s
INFO | --- Analysis for italian-public-schools-linkedopendata-it took 2.0015180110931396s
Availability | SPARQL endpoint availability check for Academic Bibliography data available from Acta Cryst E took 8.368492126464844e-05s
Availability | VoID file availability check for Academic Bibliography data available from Acta Cryst E took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Academic Bibliography data available from Acta Cryst E took 0.17709755897521973s
Reputation | Calculation of the PageRank for Academic Bibliography data available from Acta Cryst E took 0.020230531692504883s
Interlinking | Calculation of Degree of Connection for Academic Bibliography data available from Acta Cryst E took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Academic Bibliography data available from Acta Cryst E took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for Academic Bibliography data available from Acta Cryst E took 2.8848648071289062e-05s
Believability | Calculation of trust value for Academic Bibliography data available from Acta Cryst E took 1.33514404296875e-05s
INFO | --- Analysis for iucr-acta-cryst-e took 1.9943583011627197s
Availability | SPARQL endpoint availability check for IWMI Research Reports took 4.076957702636719e-05s
Availability | VoID file availability check for IWMI Research Reports took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for IWMI Research Reports took 0.20055675506591797s
Reputation | Calculation of the PageRank for IWMI Research Reports took 0.028903484344482422s
Interlinking | Calculation of Degree of Connection for IWMI Research Reports took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for IWMI Research Reports took 0.0008645057678222656s
Interlinking | Calculation of Clustering coefficient for IWMI Research Reports took 3.933906555175781e-05s
Believability | Calculation of trust value for IWMI Research Reports took 1.3589859008789062e-05s
INFO | --- Analysis for iwmi-research-reports took 2.0310637950897217s
Availability | SPARQL endpoint availability check for IWN took 7.963180541992188e-05s
Availability | VoID file availability check for IWN took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for IWN took 0.1747441291809082s
Reputation | Calculation of the PageRank for IWN took 0.02018260955810547s
Interlinking | Calculation of Degree of Connection for IWN took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IWN took 0.000782012939453125s
Interlinking | Calculation of Clustering coefficient for IWN took 3.743171691894531e-05s
Believability | Calculation of trust value for IWN took 1.2874603271484375e-05s
INFO | --- Analysis for iwn took 1.9871034622192383s
Availability | SPARQL endpoint availability check for J-GLOBAL knowledge took 6.031990051269531e-05s
Availability | VoID file availability check for J-GLOBAL knowledge took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for J-GLOBAL knowledge took 0.18732333183288574s
Reputation | Calculation of the PageRank for J-GLOBAL knowledge took 0.02027153968811035s
Interlinking | Calculation of Degree of Connection for J-GLOBAL knowledge took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for J-GLOBAL knowledge took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for J-GLOBAL knowledge took 2.8848648071289062e-05s
Believability | Calculation of trust value for J-GLOBAL knowledge took 1.2874603271484375e-05s
INFO | --- Analysis for j-global-knowledge took 1.9682857990264893s
Availability | SPARQL endpoint availability check for J.UCS Journal of Universal Computer Science took 8.368492126464844e-05s
Availability | VoID file availability check for J.UCS Journal of Universal Computer Science took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for J.UCS Journal of Universal Computer Science took 0.1830604076385498s
Reputation | Calculation of the PageRank for J.UCS Journal of Universal Computer Science took 0.020953893661499023s
Interlinking | Calculation of Degree of Connection for J.UCS Journal of Universal Computer Science took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for J.UCS Journal of Universal Computer Science took 0.0009310245513916016s
Interlinking | Calculation of Clustering coefficient for J.UCS Journal of Universal Computer Science took 3.218650817871094e-05s
Believability | Calculation of trust value for J.UCS Journal of Universal Computer Science took 1.33514404296875e-05s
INFO | --- Analysis for j-ucs-journal-of-universal-computer-science took 2.0148849487304688s
Availability | SPARQL endpoint availability check for DBTune.org Jamendo RDF Server took 5.711743593215942s
Availability | VoID file availability check for DBTune.org Jamendo RDF Server took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for DBTune.org Jamendo RDF Server took 0.17459726333618164s
Reputation | Calculation of the PageRank for DBTune.org Jamendo RDF Server took 0.020386457443237305s
Interlinking | Calculation of Degree of Connection for DBTune.org Jamendo RDF Server took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for DBTune.org Jamendo RDF Server took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for DBTune.org Jamendo RDF Server took 5.91278076171875e-05s
Believability | Calculation of trust value for DBTune.org Jamendo RDF Server took 1.1682510375976562e-05s
INFO | --- Analysis for jamendo-dbtune took 8.06216311454773s
Availability | SPARQL endpoint availability check for National Radioactivity Stat as Linked Data took 3.981590270996094e-05s
Availability | VoID file availability check for National Radioactivity Stat as Linked Data took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for National Radioactivity Stat as Linked Data took 0.17347335815429688s
Reputation | Calculation of the PageRank for National Radioactivity Stat as Linked Data took 0.020238161087036133s
Interlinking | Calculation of Degree of Connection for National Radioactivity Stat as Linked Data took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for National Radioactivity Stat as Linked Data took 0.0008091926574707031s
Interlinking | Calculation of Clustering coefficient for National Radioactivity Stat as Linked Data took 4.9591064453125e-05s
Believability | Calculation of trust value for National Radioactivity Stat as Linked Data took 1.4066696166992188e-05s
INFO | --- Analysis for japan-radioactivity-stat took 1.9761614799499512s
Availability | SPARQL endpoint availability check for JEL Classification took 5.1975250244140625e-05s
Availability | VoID file availability check for JEL Classification took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for JEL Classification took 0.18748903274536133s
Reputation | Calculation of the PageRank for JEL Classification took 0.020952939987182617s
Interlinking | Calculation of Degree of Connection for JEL Classification took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JEL Classification took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for JEL Classification took 3.1948089599609375e-05s
Believability | Calculation of trust value for JEL Classification took 1.2874603271484375e-05s
INFO | --- Analysis for jel-classification took 2.027677059173584s
Availability | SPARQL endpoint availability check for JISC Open Bibliography British National Bibliography dataset took 1.0802438259124756s
Availability | VoID file availability check for JISC Open Bibliography British National Bibliography dataset took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for JISC Open Bibliography British National Bibliography dataset took 0.1822035312652588s
Reputation | Calculation of the PageRank for JISC Open Bibliography British National Bibliography dataset took 0.020458698272705078s
Interlinking | Calculation of Degree of Connection for JISC Open Bibliography British National Bibliography dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for JISC Open Bibliography British National Bibliography dataset took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for JISC Open Bibliography British National Bibliography dataset took 3.62396240234375e-05s
Believability | Calculation of trust value for JISC Open Bibliography British National Bibliography dataset took 1.2159347534179688e-05s
INFO | --- Analysis for jiscopenbib-bl_bnb-1 took 3.2745208740234375s
Availability | SPARQL endpoint availability check for JITA Classification System of Library and Information Science took 260.938369512558s
Availability | VoID file availability check for JITA Classification System of Library and Information Science took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for JITA Classification System of Library and Information Science took 0.18310236930847168s
Reputation | Calculation of the PageRank for JITA Classification System of Library and Information Science took 0.022298574447631836s
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.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for JITA Classification System of Library and Information Science took 8.678436279296875e-05s
Believability | Calculation of trust value for JITA Classification System of Library and Information Science took 9.059906005859375e-06s
INFO | --- Analysis for jita took 535.4915447235107s
Availability | SPARQL endpoint availability check for The JMdict (Japanese-Multilingual Dictionary) project took 8.821487426757812e-05s
Availability | VoID file availability check for The JMdict (Japanese-Multilingual Dictionary) project took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for The JMdict (Japanese-Multilingual Dictionary) project took 0.17841672897338867s
Reputation | Calculation of the PageRank for The JMdict (Japanese-Multilingual Dictionary) project took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for The JMdict (Japanese-Multilingual Dictionary) project took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for The JMdict (Japanese-Multilingual Dictionary) project took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for The JMdict (Japanese-Multilingual Dictionary) project took 2.6941299438476562e-05s
Believability | Calculation of trust value for The JMdict (Japanese-Multilingual Dictionary) project took 1.1682510375976562e-05s
INFO | --- Analysis for jmdict took 2.038755416870117s
Availability | SPARQL endpoint availability check for John Goodwin's Family Tree took 20.05391764640808s
Availability | VoID file availability check for John Goodwin's Family Tree took 0.0005180835723876953s
Completeness | Calculation of interlinking completeness for John Goodwin's Family Tree took 0.1744701862335205s
Reputation | Calculation of the PageRank for John Goodwin's Family Tree took 0.021994590759277344s
Interlinking | Calculation of Degree of Connection for John Goodwin's Family Tree took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for John Goodwin's Family Tree took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for John Goodwin's Family Tree took 8.320808410644531e-05s
Believability | Calculation of trust value for John Goodwin's Family Tree took 1.2636184692382812e-05s
INFO | --- Analysis for john-goodwins-family-tree took 22.056023836135864s
Availability | SPARQL endpoint availability check for Japanese Course of Study LOD took 4.00543212890625e-05s
Availability | VoID file availability check for Japanese Course of Study LOD took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for Japanese Course of Study LOD took 0.18282151222229004s
Reputation | Calculation of the PageRank for Japanese Course of Study LOD took 0.020343542098999023s
Interlinking | Calculation of Degree of Connection for Japanese Course of Study LOD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Japanese Course of Study LOD took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for Japanese Course of Study LOD took 3.361701965332031e-05s
Believability | Calculation of trust value for Japanese Course of Study LOD took 8.58306884765625e-06s
INFO | --- Analysis for jp-cos took 2.019726037979126s
Availability | SPARQL endpoint availability check for Japanese Textbook LOD took 4.0531158447265625e-05s
Availability | VoID file availability check for Japanese Textbook LOD took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Japanese Textbook LOD took 0.18245673179626465s
Reputation | Calculation of the PageRank for Japanese Textbook LOD took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Japanese Textbook LOD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Japanese Textbook LOD took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Japanese Textbook LOD took 3.910064697265625e-05s
Believability | Calculation of trust value for Japanese Textbook LOD took 1.2874603271484375e-05s
INFO | --- Analysis for jp-textbook took 1.994433879852295s
Availability | SPARQL endpoint availability check for JRC-Names took 4.029273986816406e-05s
Availability | VoID file availability check for JRC-Names took 0.00047397613525390625s
Completeness | Calculation of interlinking completeness for JRC-Names took 0.18769025802612305s
Reputation | Calculation of the PageRank for JRC-Names took 0.020699024200439453s
Interlinking | Calculation of Degree of Connection for JRC-Names took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for JRC-Names took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for JRC-Names took 3.409385681152344e-05s
Believability | Calculation of trust value for JRC-Names took 1.3589859008789062e-05s
INFO | --- Analysis for jrc-names-ec took 1.9822404384613037s
Availability | SPARQL endpoint availability check for JRC-Names-MLODE took 8.392333984375e-05s
Availability | VoID file availability check for JRC-Names-MLODE took 0.0004744529724121094s
Completeness | Calculation of interlinking completeness for JRC-Names-MLODE took 0.18822979927062988s
Reputation | Calculation of the PageRank for JRC-Names-MLODE took 0.021732807159423828s
Interlinking | Calculation of Degree of Connection for JRC-Names-MLODE took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for JRC-Names-MLODE took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for JRC-Names-MLODE took 6.389617919921875e-05s
Believability | Calculation of trust value for JRC-Names-MLODE took 1.3828277587890625e-05s
INFO | --- Analysis for jrc-names-mlode took 2.0033600330352783s
Availability | SPARQL endpoint availability check for JudaicaLink took 8.440017700195312e-05s
Availability | VoID file availability check for JudaicaLink took 0.00026297569274902344s
Completeness | Calculation of interlinking completeness for JudaicaLink took 0.19826149940490723s
Reputation | Calculation of the PageRank for JudaicaLink took 0.020327329635620117s
Interlinking | Calculation of Degree of Connection for JudaicaLink took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for JudaicaLink took 0.0006866455078125s
Interlinking | Calculation of Clustering coefficient for JudaicaLink took 0.000102996826171875s
Believability | Calculation of trust value for JudaicaLink took 1.2636184692382812e-05s
INFO | --- Analysis for judaicalink took 2.0235071182250977s
Availability | SPARQL endpoint availability check for KAIST silver standard corpus took 8.177757263183594e-05s
Availability | VoID file availability check for KAIST silver standard corpus took 0.00022745132446289062s
Completeness | Calculation of interlinking completeness for KAIST silver standard corpus took 0.17656445503234863s
Reputation | Calculation of the PageRank for KAIST silver standard corpus took 0.023408889770507812s
Interlinking | Calculation of Degree of Connection for KAIST silver standard corpus took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for KAIST silver standard corpus took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for KAIST silver standard corpus took 3.075599670410156e-05s
Believability | Calculation of trust value for KAIST silver standard corpus took 1.1444091796875e-05s
INFO | --- Analysis for kaist-silver-standard-corpus took 2.021717071533203s
Availability | SPARQL endpoint availability check for KAKEN took 4.100799560546875e-05s
Availability | VoID file availability check for KAKEN took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for KAKEN took 0.1837158203125s
Reputation | Calculation of the PageRank for KAKEN took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for KAKEN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KAKEN took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for KAKEN took 3.0994415283203125e-05s
Believability | Calculation of trust value for KAKEN took 1.3828277587890625e-05s
INFO | --- Analysis for kaken took 1.982818365097046s
Availability | SPARQL endpoint availability check for Kallikratis municipalities took 8.821487426757812e-05s
Availability | VoID file availability check for Kallikratis municipalities took 0.0005090236663818359s
Completeness | Calculation of interlinking completeness for Kallikratis municipalities took 0.17345356941223145s
Reputation | Calculation of the PageRank for Kallikratis municipalities took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for Kallikratis municipalities took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Kallikratis municipalities took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Kallikratis municipalities took 8.916854858398438e-05s
Believability | Calculation of trust value for Kallikratis municipalities took 1.2874603271484375e-05s
INFO | --- Analysis for kallikratis-municipalities took 1.996847152709961s
Availability | SPARQL endpoint availability check for Openflights Routes took 8.296966552734375e-05s
Availability | VoID file availability check for Openflights Routes took 0.00020647048950195312s
Completeness | Calculation of interlinking completeness for Openflights Routes took 0.17345833778381348s
Reputation | Calculation of the PageRank for Openflights Routes took 0.0202329158782959s
Interlinking | Calculation of Degree of Connection for Openflights Routes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Openflights Routes took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Openflights Routes took 2.86102294921875e-05s
Believability | Calculation of trust value for Openflights Routes took 1.0728836059570312e-05s
INFO | --- Analysis for kasabi-openflights-routes took 1.9564604759216309s
Availability | SPARQL endpoint availability check for EU Soccer League took 3.981590270996094e-05s
Availability | VoID file availability check for EU Soccer League took 0.00045680999755859375s
Completeness | Calculation of interlinking completeness for EU Soccer League took 0.17620062828063965s
Reputation | Calculation of the PageRank for EU Soccer League took 0.020943641662597656s
Interlinking | Calculation of Degree of Connection for EU Soccer League took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for EU Soccer League took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for EU Soccer League took 3.1948089599609375e-05s
Believability | Calculation of trust value for EU Soccer League took 1.049041748046875e-05s
INFO | --- Analysis for KG:Course_Submission took 1.9529802799224854s
Availability | SPARQL endpoint availability check for Legal Knowledge Graph took 3.886222839355469e-05s
Availability | VoID file availability check for Legal Knowledge Graph took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for Legal Knowledge Graph took 0.17565155029296875s
Reputation | Calculation of the PageRank for Legal Knowledge Graph took 0.02012157440185547s
Interlinking | Calculation of Degree of Connection for Legal Knowledge Graph took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Legal Knowledge Graph took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Legal Knowledge Graph took 1.1682510375976562e-05s
Believability | Calculation of trust value for Legal Knowledge Graph took 1.2636184692382812e-05s
INFO | --- Analysis for KING took 1.9818053245544434s
Availability | SPARQL endpoint availability check for Klappstuhlclub took 8.416175842285156e-05s
Availability | VoID file availability check for Klappstuhlclub took 0.00048422813415527344s
Completeness | Calculation of interlinking completeness for Klappstuhlclub took 0.18454742431640625s
Reputation | Calculation of the PageRank for Klappstuhlclub took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for Klappstuhlclub took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Klappstuhlclub took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Klappstuhlclub took 6.4849853515625e-05s
Believability | Calculation of trust value for Klappstuhlclub took 1.4066696166992188e-05s
INFO | --- Analysis for klappstuhlclub took 2.020874500274658s
Availability | SPARQL endpoint availability check for Linked Sensor Data (Kno.e.sis) took 8.487701416015625e-05s
Availability | VoID file availability check for Linked Sensor Data (Kno.e.sis) took 0.0005345344543457031s
Completeness | Calculation of interlinking completeness for Linked Sensor Data (Kno.e.sis) took 0.17330431938171387s
Reputation | Calculation of the PageRank for Linked Sensor Data (Kno.e.sis) took 0.020664691925048828s
Interlinking | Calculation of Degree of Connection for Linked Sensor Data (Kno.e.sis) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Linked Sensor Data (Kno.e.sis) took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for Linked Sensor Data (Kno.e.sis) took 6.198883056640625e-05s
Believability | Calculation of trust value for Linked Sensor Data (Kno.e.sis) took 1.33514404296875e-05s
INFO | --- Analysis for knoesis-linked-sensor-data took 2.218714475631714s
Availability | SPARQL endpoint availability check for Knowledge Forest took 3.981590270996094e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.1752758026123047s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 3.0279159545898438e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.1682510375976562e-05s
INFO | --- Analysis for knowledge-map took 1.9517672061920166s
Availability | SPARQL endpoint availability check for Knowledge Forest took 4.0531158447265625e-05s
Availability | VoID file availability check for Knowledge Forest took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Knowledge Forest took 0.18445801734924316s
Reputation | Calculation of the PageRank for Knowledge Forest took 0.020958423614501953s
Interlinking | Calculation of Degree of Connection for Knowledge Forest took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Knowledge Forest took 0.0006897449493408203s
Interlinking | Calculation of Clustering coefficient for Knowledge Forest took 2.9802322387695312e-05s
Believability | Calculation of trust value for Knowledge Forest took 1.049041748046875e-05s
INFO | --- Analysis for KnowledgeFusion took 2.00571346282959s
Availability | SPARQL endpoint availability check for KORE 50 NIF NER Corpus took 4.172325134277344e-05s
Availability | VoID file availability check for KORE 50 NIF NER Corpus took 0.00046372413635253906s
Completeness | Calculation of interlinking completeness for KORE 50 NIF NER Corpus took 0.18586087226867676s
Reputation | Calculation of the PageRank for KORE 50 NIF NER Corpus took 0.02163219451904297s
Interlinking | Calculation of Degree of Connection for KORE 50 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for KORE 50 NIF NER Corpus took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for KORE 50 NIF NER Corpus took 6.341934204101562e-05s
Believability | Calculation of trust value for KORE 50 NIF NER Corpus took 1.049041748046875e-05s
INFO | --- Analysis for kore-50-nif-ner-corpus took 1.9612674713134766s
Availability | SPARQL endpoint availability check for Korea Intellectual Propert Office(KIPO) took 8.344650268554688e-05s
Availability | VoID file availability check for Korea Intellectual Propert Office(KIPO) took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for Korea Intellectual Propert Office(KIPO) took 0.17799997329711914s
Reputation | Calculation of the PageRank for Korea Intellectual Propert Office(KIPO) took 0.02122211456298828s
Interlinking | Calculation of Degree of Connection for Korea Intellectual Propert Office(KIPO) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Korea Intellectual Propert Office(KIPO) took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Korea Intellectual Propert Office(KIPO) took 3.0994415283203125e-05s
Believability | Calculation of trust value for Korea Intellectual Propert Office(KIPO) took 5.4836273193359375e-06s
INFO | --- Analysis for korea-intellectual-propert-office-kipo took 1.9705214500427246s
Availability | SPARQL endpoint availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0001049041748046875s
Availability | VoID file availability check for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.17702746391296387s
Reputation | Calculation of the PageRank for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.021085500717163086s
Interlinking | Calculation of Degree of Connection for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 3.218650817871094e-05s
Believability | Calculation of trust value for Kronika naukowa Biblioteki Uniwersyteckiej w Łodzi took 1.3113021850585938e-05s
INFO | --- Analysis for Kronika_naukowa_Biblioteki_Jagiellońskiej took 2.0002009868621826s
Availability | SPARQL endpoint availability check for Korean Traditional Recipes took 8.273124694824219e-05s
Availability | VoID file availability check for Korean Traditional Recipes took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for Korean Traditional Recipes took 0.1786198616027832s
Reputation | Calculation of the PageRank for Korean Traditional Recipes took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for Korean Traditional Recipes took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Korean Traditional Recipes took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Korean Traditional Recipes took 2.8848648071289062e-05s
Believability | Calculation of trust value for Korean Traditional Recipes took 1.049041748046875e-05s
INFO | --- Analysis for ktr took 1.9598362445831299s
Availability | SPARQL endpoint availability check for Informatics Studies took 4.220008850097656e-05s
Availability | VoID file availability check for Informatics Studies took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Informatics Studies took 0.1794896125793457s
Reputation | Calculation of the PageRank for Informatics Studies took 0.02037954330444336s
Interlinking | Calculation of Degree of Connection for Informatics Studies took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Informatics Studies took 0.0007169246673583984s
Interlinking | Calculation of Clustering coefficient for Informatics Studies took 2.9325485229492188e-05s
Believability | Calculation of trust value for Informatics Studies took 9.298324584960938e-06s
INFO | --- Analysis for Kumar,_Gireesh__and_Singh,_Anand took 2.0019657611846924s
Availability | SPARQL endpoint availability check for Kidney and Urinary Pathway Knowledge Base took 8.416175842285156e-05s
Availability | VoID file availability check for Kidney and Urinary Pathway Knowledge Base took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Kidney and Urinary Pathway Knowledge Base took 0.17713403701782227s
Reputation | Calculation of the PageRank for Kidney and Urinary Pathway Knowledge Base took 0.021775245666503906s
Interlinking | Calculation of Degree of Connection for Kidney and Urinary Pathway Knowledge Base took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Kidney and Urinary Pathway Knowledge Base took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Kidney and Urinary Pathway Knowledge Base took 3.504753112792969e-05s
Believability | Calculation of trust value for Kidney and Urinary Pathway Knowledge Base took 5.9604644775390625e-06s
INFO | --- Analysis for kupkb took 1.9833290576934814s
Availability | SPARQL endpoint availability check for Léčivé přípravky ze SÚKL took 4.363059997558594e-05s
Availability | VoID file availability check for Léčivé přípravky ze SÚKL took 0.0005559921264648438s
Completeness | Calculation of interlinking completeness for Léčivé přípravky ze SÚKL took 0.1780989170074463s
Reputation | Calculation of the PageRank for Léčivé přípravky ze SÚKL took 0.02252674102783203s
Interlinking | Calculation of Degree of Connection for Léčivé přípravky ze SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Léčivé přípravky ze SÚKL took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Léčivé přípravky ze SÚKL took 4.410743713378906e-05s
Believability | Calculation of trust value for Léčivé přípravky ze SÚKL took 1.049041748046875e-05s
INFO | --- Analysis for l--iv--p--pravky-ze-s-kl took 1.9987914562225342s
Availability | SPARQL endpoint availability check for DBLP in RDF (L3S) took 8.559226989746094e-05s
Availability | VoID file availability check for DBLP in RDF (L3S) took 0.00045371055603027344s
Completeness | Calculation of interlinking completeness for DBLP in RDF (L3S) took 0.1803758144378662s
Reputation | Calculation of the PageRank for DBLP in RDF (L3S) took 0.02005457878112793s
Interlinking | Calculation of Degree of Connection for DBLP in RDF (L3S) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for DBLP in RDF (L3S) took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for DBLP in RDF (L3S) took 7.128715515136719e-05s
Believability | Calculation of trust value for DBLP in RDF (L3S) took 1.049041748046875e-05s
INFO | --- Analysis for l3s-dblp took 1.972320556640625s
Availability | SPARQL endpoint availability check for Learning Analytics and Knowledge (LAK) Dataset took 3.9577484130859375e-05s
Availability | VoID file availability check for Learning Analytics and Knowledge (LAK) Dataset took 0.0004951953887939453s
Completeness | Calculation of interlinking completeness for Learning Analytics and Knowledge (LAK) Dataset took 0.18131089210510254s
Reputation | Calculation of the PageRank for Learning Analytics and Knowledge (LAK) Dataset took 0.02066636085510254s
Interlinking | Calculation of Degree of Connection for Learning Analytics and Knowledge (LAK) Dataset took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Learning Analytics and Knowledge (LAK) Dataset took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Learning Analytics and Knowledge (LAK) Dataset took 6.842613220214844e-05s
Believability | Calculation of trust value for Learning Analytics and Knowledge (LAK) Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for lak-dataset took 1.956831455230713s
Availability | SPARQL endpoint availability check for  Language Name Authority List  took 4.124641418457031e-05s
Availability | VoID file availability check for  Language Name Authority List  took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for  Language Name Authority List  took 0.17402982711791992s
Reputation | Calculation of the PageRank for  Language Name Authority List  took 0.020280122756958008s
Interlinking | Calculation of Degree of Connection for  Language Name Authority List  took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for  Language Name Authority List  took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for  Language Name Authority List  took 8.034706115722656e-05s
Believability | Calculation of trust value for  Language Name Authority List  took 1.1682510375976562e-05s
INFO | --- Analysis for language-authority-list took 1.9754061698913574s
Availability | SPARQL endpoint availability check for Lark took 4.100799560546875e-05s
Availability | VoID file availability check for Lark took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Lark took 0.17260098457336426s
Reputation | Calculation of the PageRank for Lark took 0.02042245864868164s
Interlinking | Calculation of Degree of Connection for Lark took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Lark took 0.0009920597076416016s
Interlinking | Calculation of Clustering coefficient for Lark took 7.677078247070312e-05s
Believability | Calculation of trust value for Lark took 1.1444091796875e-05s
INFO | --- Analysis for LARK took 1.9891886711120605s
Availability | SPARQL endpoint availability check for LASLA corpus in LiLa took 8.082389831542969e-05s
Availability | VoID file availability check for LASLA corpus in LiLa took 0.0002224445343017578s
Completeness | Calculation of interlinking completeness for LASLA corpus in LiLa took 0.2677285671234131s
Reputation | Calculation of the PageRank for LASLA corpus in LiLa took 0.022319793701171875s
Interlinking | Calculation of Degree of Connection for LASLA corpus in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LASLA corpus in LiLa took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for LASLA corpus in LiLa took 3.314018249511719e-05s
Believability | Calculation of trust value for LASLA corpus in LiLa took 4.76837158203125e-06s
INFO | --- Analysis for LASLA took 2.0841636657714844s
Availability | SPARQL endpoint availability check for LATC Linksets took 3.9577484130859375e-05s
Availability | VoID file availability check for LATC Linksets took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for LATC Linksets took 0.1764378547668457s
Reputation | Calculation of the PageRank for LATC Linksets took 0.02021193504333496s
Interlinking | Calculation of Degree of Connection for LATC Linksets took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LATC Linksets took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for LATC Linksets took 2.765655517578125e-05s
Believability | Calculation of trust value for LATC Linksets took 1.2636184692382812e-05s
INFO | --- Analysis for latc-linksets took 2.0633699893951416s
Availability | SPARQL endpoint availability check for Latin Vallex 2.0 in LiLa took 8.440017700195312e-05s
Availability | VoID file availability check for Latin Vallex 2.0 in LiLa took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Latin Vallex 2.0 in LiLa took 0.18176579475402832s
Reputation | Calculation of the PageRank for Latin Vallex 2.0 in LiLa took 0.02004408836364746s
Interlinking | Calculation of Degree of Connection for Latin Vallex 2.0 in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Latin Vallex 2.0 in LiLa took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Latin Vallex 2.0 in LiLa took 3.5762786865234375e-05s
Believability | Calculation of trust value for Latin Vallex 2.0 in LiLa took 1.1920928955078125e-05s
INFO | --- Analysis for Latin_Vallex2.0 took 1.9648065567016602s
Availability | SPARQL endpoint availability check for LatinAffectus in LiLa took 4.1484832763671875e-05s
Availability | VoID file availability check for LatinAffectus in LiLa took 0.00020647048950195312s
Completeness | Calculation of interlinking completeness for LatinAffectus in LiLa took 0.17265963554382324s
Reputation | Calculation of the PageRank for LatinAffectus in LiLa took 0.02090144157409668s
Interlinking | Calculation of Degree of Connection for LatinAffectus in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LatinAffectus in LiLa took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for LatinAffectus in LiLa took 3.457069396972656e-05s
Believability | Calculation of trust value for LatinAffectus in LiLa took 1.2159347534179688e-05s
INFO | --- Analysis for LatinAffectus took 2.0016422271728516s
Availability | SPARQL endpoint availability check for Latin WordNet Revision in LiLa took 0.00011038780212402344s
Availability | VoID file availability check for Latin WordNet Revision in LiLa took 0.0002014636993408203s
Completeness | Calculation of interlinking completeness for Latin WordNet Revision in LiLa took 0.1773984432220459s
Reputation | Calculation of the PageRank for Latin WordNet Revision in LiLa took 0.021116256713867188s
Interlinking | Calculation of Degree of Connection for Latin WordNet Revision in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Latin WordNet Revision in LiLa took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Latin WordNet Revision in LiLa took 4.220008850097656e-05s
Believability | Calculation of trust value for Latin WordNet Revision in LiLa took 1.0967254638671875e-05s
INFO | --- Analysis for LatinWordnetLiLa took 1.9927654266357422s
Availability | SPARQL endpoint availability check for Leipzig Corpora Collection (LCC) took 8.177757263183594e-05s
Availability | VoID file availability check for Leipzig Corpora Collection (LCC) took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Leipzig Corpora Collection (LCC) took 0.17602992057800293s
Reputation | Calculation of the PageRank for Leipzig Corpora Collection (LCC) took 0.020153045654296875s
Interlinking | Calculation of Degree of Connection for Leipzig Corpora Collection (LCC) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Leipzig Corpora Collection (LCC) took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Leipzig Corpora Collection (LCC) took 2.8371810913085938e-05s
Believability | Calculation of trust value for Leipzig Corpora Collection (LCC) took 1.2636184692382812e-05s
INFO | --- Analysis for lcc took 1.9779818058013916s
Availability | SPARQL endpoint availability check for Library of Congress Subject Headings took 8.559226989746094e-05s
Availability | VoID file availability check for Library of Congress Subject Headings took 0.0005855560302734375s
Completeness | Calculation of interlinking completeness for Library of Congress Subject Headings took 0.17994952201843262s
Reputation | Calculation of the PageRank for Library of Congress Subject Headings took 0.02018904685974121s
Interlinking | Calculation of Degree of Connection for Library of Congress Subject Headings took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Library of Congress Subject Headings took 0.0006914138793945312s
Interlinking | Calculation of Clustering coefficient for Library of Congress Subject Headings took 0.00011396408081054688s
Believability | Calculation of trust value for Library of Congress Subject Headings took 1.1682510375976562e-05s
INFO | --- Analysis for lcsh took 2.735731840133667s
Availability | SPARQL endpoint availability check for LCSubjects.org Library of Congress Subject Headings took 4.1484832763671875e-05s
Availability | VoID file availability check for LCSubjects.org Library of Congress Subject Headings took 0.0005457401275634766s
Completeness | Calculation of interlinking completeness for LCSubjects.org Library of Congress Subject Headings took 0.18190765380859375s
Reputation | Calculation of the PageRank for LCSubjects.org Library of Congress Subject Headings took 0.021538257598876953s
Interlinking | Calculation of Degree of Connection for LCSubjects.org Library of Congress Subject Headings took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LCSubjects.org Library of Congress Subject Headings took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for LCSubjects.org Library of Congress Subject Headings took 7.748603820800781e-05s
Believability | Calculation of trust value for LCSubjects.org Library of Congress Subject Headings took 1.33514404296875e-05s
INFO | --- Analysis for lcsubjects took 2.5314888954162598s
Availability | SPARQL endpoint availability check for LDQM - Accessibility of DBpedia resources took 8.606910705566406e-05s
Availability | VoID file availability check for LDQM - Accessibility of DBpedia resources took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for LDQM - Accessibility of DBpedia resources took 0.18534564971923828s
Reputation | Calculation of the PageRank for LDQM - Accessibility of DBpedia resources took 0.020836830139160156s
Interlinking | Calculation of Degree of Connection for LDQM - Accessibility of DBpedia resources took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LDQM - Accessibility of DBpedia resources took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for LDQM - Accessibility of DBpedia resources took 3.2901763916015625e-05s
Believability | Calculation of trust value for LDQM - Accessibility of DBpedia resources took 1.2636184692382812e-05s
INFO | --- Analysis for ldqm-dbpedia-2016 took 1.9880211353302002s
Availability | SPARQL endpoint availability check for Linked Open Data Taiwan @ Library took 8.509697198867798s
Availability | VoID file availability check for Linked Open Data Taiwan @ Library took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for Linked Open Data Taiwan @ Library took 0.1853466033935547s
Reputation | Calculation of the PageRank for Linked Open Data Taiwan @ Library took 0.020384788513183594s
Interlinking | Calculation of Degree of Connection for Linked Open Data Taiwan @ Library took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Open Data Taiwan @ Library took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Linked Open Data Taiwan @ Library took 4.363059997558594e-05s
Believability | Calculation of trust value for Linked Open Data Taiwan @ Library took 1.3113021850585938e-05s
INFO | --- Analysis for ldt@library took 14.968742847442627s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Eng took 8.249282836914062e-05s
Availability | VoID file availability check for Learned Genre Ontology Eng took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Eng took 0.17928481101989746s
Reputation | Calculation of the PageRank for Learned Genre Ontology Eng took 0.020249128341674805s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Eng took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Learned Genre Ontology Eng took 0.0006930828094482422s
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 1.33514404296875e-05s
INFO | --- Analysis for learned-genre-ontology-eng took 1.9959893226623535s
Availability | SPARQL endpoint availability check for Learned Genre Ontology Intl took 4.076957702636719e-05s
Availability | VoID file availability check for Learned Genre Ontology Intl took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Learned Genre Ontology Intl took 0.1814560890197754s
Reputation | Calculation of the PageRank for Learned Genre Ontology Intl took 0.021340370178222656s
Interlinking | Calculation of Degree of Connection for Learned Genre Ontology Intl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Learned Genre Ontology Intl took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Learned Genre Ontology Intl took 2.9802322387695312e-05s
Believability | Calculation of trust value for Learned Genre Ontology Intl took 1.3589859008789062e-05s
INFO | --- Analysis for learned-genre-ontology-intl took 1.991018533706665s
Availability | SPARQL endpoint availability check for U ime Legije took 8.249282836914062e-05s
Availability | VoID file availability check for U ime Legije took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for U ime Legije took 0.190596342086792s
Reputation | Calculation of the PageRank for U ime Legije took 0.020551204681396484s
Interlinking | Calculation of Degree of Connection for U ime Legije took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for U ime Legije took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for U ime Legije took 3.266334533691406e-05s
Believability | Calculation of trust value for U ime Legije took 1.3589859008789062e-05s
INFO | --- Analysis for LEGIJA_STRANACA took 1.9935920238494873s
Availability | SPARQL endpoint availability check for OpenUpLabs Legislation took 4.315376281738281e-05s
Availability | VoID file availability check for OpenUpLabs Legislation took 0.0002608299255371094s
Completeness | Calculation of interlinking completeness for OpenUpLabs Legislation took 0.17517542839050293s
Reputation | Calculation of the PageRank for OpenUpLabs Legislation took 0.02057814598083496s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Legislation took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for OpenUpLabs Legislation took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Legislation took 3.2901763916015625e-05s
Believability | Calculation of trust value for OpenUpLabs Legislation took 1.430511474609375e-05s
INFO | --- Analysis for legislation-openuplabs took 2.0172786712646484s
Availability | SPARQL endpoint availability check for LiLa Lemma Bank took 4.291534423828125e-05s
Availability | VoID file availability check for LiLa Lemma Bank took 0.0005471706390380859s
Completeness | Calculation of interlinking completeness for LiLa Lemma Bank took 0.17949414253234863s
Reputation | Calculation of the PageRank for LiLa Lemma Bank took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for LiLa Lemma Bank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LiLa Lemma Bank took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for LiLa Lemma Bank took 7.152557373046875e-05s
Believability | Calculation of trust value for LiLa Lemma Bank took 1.3828277587890625e-05s
INFO | --- Analysis for LemmaBank took 1.970794916152954s
Availability | SPARQL endpoint availability check for lemonUby took 8.821487426757812e-05s
Availability | VoID file availability check for lemonUby took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for lemonUby took 0.1722416877746582s
Reputation | Calculation of the PageRank for lemonUby took 0.020420312881469727s
Interlinking | Calculation of Degree of Connection for lemonUby took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for lemonUby took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for lemonUby took 6.723403930664062e-05s
Believability | Calculation of trust value for lemonUby took 8.821487426757812e-06s
INFO | --- Analysis for lemonuby took 1.9674146175384521s
Availability | SPARQL endpoint availability check for LemonWiktionary took 8.130073547363281e-05s
Availability | VoID file availability check for LemonWiktionary took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for LemonWiktionary took 0.17779827117919922s
Reputation | Calculation of the PageRank for LemonWiktionary took 0.021509170532226562s
Interlinking | Calculation of Degree of Connection for LemonWiktionary took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for LemonWiktionary took 0.0010862350463867188s
Interlinking | Calculation of Clustering coefficient for LemonWiktionary took 4.553794860839844e-05s
Believability | Calculation of trust value for LemonWiktionary took 8.58306884765625e-06s
INFO | --- Analysis for lemonwiktionary took 1.9400436878204346s
Availability | SPARQL endpoint availability check for Lewis and Short Latin-English Dictionary in LiLa took 4.0531158447265625e-05s
Availability | VoID file availability check for Lewis and Short Latin-English Dictionary in LiLa took 0.00029778480529785156s
Completeness | Calculation of interlinking completeness for Lewis and Short Latin-English Dictionary in LiLa took 0.1728677749633789s
Reputation | Calculation of the PageRank for Lewis and Short Latin-English Dictionary in LiLa took 0.02040266990661621s
Interlinking | Calculation of Degree of Connection for Lewis and Short Latin-English Dictionary in LiLa took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lewis and Short Latin-English Dictionary in LiLa took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for Lewis and Short Latin-English Dictionary in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Lewis and Short Latin-English Dictionary in LiLa took 6.198883056640625e-06s
INFO | --- Analysis for LewisShort took 1.9775450229644775s
Availability | SPARQL endpoint availability check for LEXIN-RDF took 4.1484832763671875e-05s
Availability | VoID file availability check for LEXIN-RDF took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for LEXIN-RDF took 0.1688551902770996s
Reputation | Calculation of the PageRank for LEXIN-RDF took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for LEXIN-RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LEXIN-RDF took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for LEXIN-RDF took 3.123283386230469e-05s
Believability | Calculation of trust value for LEXIN-RDF took 7.867813110351562e-06s
INFO | --- Analysis for lexin-rdf took 1.9257309436798096s
Availability | SPARQL endpoint availability check for lexinfo took 3.9577484130859375e-05s
Availability | VoID file availability check for lexinfo took 0.00024008750915527344s
Completeness | Calculation of interlinking completeness for lexinfo took 0.169236421585083s
Reputation | Calculation of the PageRank for lexinfo took 0.020195484161376953s
Interlinking | Calculation of Degree of Connection for lexinfo took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for lexinfo took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for lexinfo took 8.916854858398438e-05s
Believability | Calculation of trust value for lexinfo took 7.3909759521484375e-06s
INFO | --- Analysis for lexinfo took 1.938279151916504s
Availability | SPARQL endpoint availability check for Lexvo took 8.034706115722656e-05s
Availability | VoID file availability check for Lexvo took 0.0004394054412841797s
Completeness | Calculation of interlinking completeness for Lexvo took 0.18637299537658691s
Reputation | Calculation of the PageRank for Lexvo took 0.02023172378540039s
Interlinking | Calculation of Degree of Connection for Lexvo took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lexvo took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for Lexvo took 0.0001723766326904297s
Believability | Calculation of trust value for Lexvo took 1.1444091796875e-05s
INFO | --- Analysis for lexvo took 1.9839026927947998s
Availability | SPARQL endpoint availability check for Lexvo.org took 4.57763671875e-05s
Availability | VoID file availability check for Lexvo.org took 0.00024080276489257812s
Completeness | Calculation of interlinking completeness for Lexvo.org took 0.16962432861328125s
Reputation | Calculation of the PageRank for Lexvo.org took 0.020049333572387695s
Interlinking | Calculation of Degree of Connection for Lexvo.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lexvo.org took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Lexvo.org took 7.224082946777344e-05s
Believability | Calculation of trust value for Lexvo.org took 6.9141387939453125e-06s
INFO | --- Analysis for lexvo-org took 1.92262601852417s
Availability | SPARQL endpoint availability check for LIBRIS took 0.37592029571533203s
Availability | VoID file availability check for LIBRIS took 0.0002446174621582031s
Extra | Recovery of all triples for LIBRIS took 6.1809468269348145s
Performance | Total latancy measurement for LIBRIS took 0.8971090316772461s
Amount of data | Number of triples check for LIBRIS took 66.3991003036499s
Interoperability | New terms check for LIBRIS took 14.986340522766113s
Versatility | Languages check for LIBRIS took 0.1918652057647705s
Interpretability | Number of blank nodes check for LIBRIS took 300.08055424690247s
Security | Check HTTPS for LIBRIS took 0.35250353813171387s
Interpretability | RDF structures check for LIBRIS took 0.393308162689209s
Versatility | Serialization formats check for LIBRIS took 0.23198342323303223s
Availability | RDF dump link check for LIBRIS took 0.13778376579284668s
License | MR license check for LIBRIS took 0.20548272132873535s
License | HR license check for LIBRIS took 0.5407974720001221s
Amount of data | Number of property check for LIBRIS took 0.20577740669250488s
Understandability | Number of label check for LIBRIS took 0.4201850891113281s
Understandability | URI regex check for LIBRIS took 0.33006715774536133s
Understandability | Vocabs check for LIBRIS took 0.18891310691833496s
Verifiability | Authors check for LIBRIS took 0.1476728916168213s
Verifiability | Publishers check for LIBRIS took 0.14687347412109375s
Performance | Throughput check for LIBRIS took 10.960245370864868s
Amount of data | Check the number of entities for LIBRIS took 0.00011229515075683594s
Verifiability | Contribs. check for LIBRIS took 0.15016627311706543s
Interlinking | sameAs chians check for LIBRIS took 0.22193503379821777s
Interlinking | skos check for LIBRIS took 0.2952144145965576s
Interlinking | skos check for LIBRIS took 0.13765573501586914s
Timeliness | dataset update frequency check for LIBRIS took 0.14577484130859375s
Currency | Creation date check for LIBRIS took 0.3589026927947998s
Currency | Modification date check for LIBRIS took 0.6658363342285156s
Rep.Conc. | URIs length for LIBRIS took 81.67035245895386s
Interoperability | New vocabularies check for LIBRIS took 5.245208740234375e-06s
Consistency | Deprecated classes/propertiers check for LIBRIS took 0.20525121688842773s
Accuracy | Check Functional Property for LIBRIS took 0.219451904296875s
Accuracy | Check Inverse Functional Property for LIBRIS took 0.19460749626159668s
Accuracy | Check Datatype consistency for LIBRIS took 0.25959181785583496s
Consistency | Disjoint class check for LIBRIS took 0.19481372833251953s
Consistency | Check Misplaced properties for LIBRIS took 61.10782313346863s
Consistency | Misplaced classes for LIBRIS took 1.1143007278442383s
Consistency | Check Ontology hijacking for LIBRIS took 3.6564784049987793s
Consistency | Check Invalid usage of undefined classes for LIBRIS took 1.286728858947754s
Consistency | Check Invalid usage of undefined properties for LIBRIS took 62.092358350753784s
Conciseness | Check Extensional conciseness for LIBRIS took 0.2865273952484131s
Conciseness | Check Intensional conciseness for LIBRIS took 0.4420619010925293s
Security | Sign check for LIBRIS took 0.19498300552368164s
Availability | Check URIs Dereferenciability for LIBRIS took 13.843281984329224s
Completeness | Calculation of interlinking completeness for LIBRIS took 0.29773879051208496s
Reputation | Calculation of the PageRank for LIBRIS took 0.020267963409423828s
Interlinking | Calculation of Degree of Connection for LIBRIS took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for LIBRIS took 0.0006811618804931641s
Interlinking | Calculation of Clustering coefficient for LIBRIS took 8.7738037109375e-05s
Interoperability | Check the re-using of existing vocabs for LIBRIS took 1.1920928955078125e-06s
Believability | Calculation of trust value for LIBRIS took 1.2636184692382812e-05s
INFO | --- Analysis for libris took 1141.1099939346313s
Availability | SPARQL endpoint availability check for Public Library of Veroia took 0.2448732852935791s
Availability | VoID file availability check for Public Library of Veroia took 0.0005123615264892578s
Completeness | Calculation of interlinking completeness for Public Library of Veroia took 0.17560029029846191s
Reputation | Calculation of the PageRank for Public Library of Veroia took 0.021823644638061523s
Interlinking | Calculation of Degree of Connection for Public Library of Veroia took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Public Library of Veroia took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Public Library of Veroia took 7.2479248046875e-05s
Believability | Calculation of trust value for Public Library of Veroia took 1.3113021850585938e-05s
INFO | --- Analysis for libver took 2.3194591999053955s
Availability | SPARQL endpoint availability check for Lichfield District Council - Spending took 4.076957702636719e-05s
Availability | VoID file availability check for Lichfield District Council - Spending took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for Lichfield District Council - Spending took 0.18332481384277344s
Reputation | Calculation of the PageRank for Lichfield District Council - Spending took 0.02025628089904785s
Interlinking | Calculation of Degree of Connection for Lichfield District Council - Spending took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lichfield District Council - Spending took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Lichfield District Council - Spending took 7.653236389160156e-05s
Believability | Calculation of trust value for Lichfield District Council - Spending took 6.198883056640625e-06s
INFO | --- Analysis for lichfield-spending took 2.000291585922241s
Availability | SPARQL endpoint availability check for Linguistic Metadata (LIME) vocabulary took 4.124641418457031e-05s
Availability | VoID file availability check for Linguistic Metadata (LIME) vocabulary took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for Linguistic Metadata (LIME) vocabulary took 0.17688417434692383s
Reputation | Calculation of the PageRank for Linguistic Metadata (LIME) vocabulary took 0.020490169525146484s
Interlinking | Calculation of Degree of Connection for Linguistic Metadata (LIME) vocabulary took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linguistic Metadata (LIME) vocabulary took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Linguistic Metadata (LIME) vocabulary took 3.337860107421875e-05s
Believability | Calculation of trust value for Linguistic Metadata (LIME) vocabulary took 1.0013580322265625e-05s
INFO | --- Analysis for lime took 1.9992754459381104s
Availability | SPARQL endpoint availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 3.8623809814453125e-05s
Availability | VoID file availability check for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.1925671100616455s
Reputation | Calculation of the PageRank for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 0.00010013580322265625s
Believability | Calculation of trust value for lingvoj ? Languages of the World (Multilingual RDF Descriptions) took 1.430511474609375e-05s
INFO | --- Analysis for lingvoj took 2.0559587478637695s
Availability | SPARQL endpoint availability check for Linked Crunchbase took 8.440017700195312e-05s
Availability | VoID file availability check for Linked Crunchbase took 0.00047516822814941406s
Completeness | Calculation of interlinking completeness for Linked Crunchbase took 0.1777970790863037s
Reputation | Calculation of the PageRank for Linked Crunchbase took 0.021557092666625977s
Interlinking | Calculation of Degree of Connection for Linked Crunchbase took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked Crunchbase took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Linked Crunchbase took 7.867813110351562e-05s
Believability | Calculation of trust value for Linked Crunchbase took 1.3589859008789062e-05s
INFO | --- Analysis for linked-crunchbase took 2.0091214179992676s
Availability | SPARQL endpoint availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 4.1961669921875e-05s
Availability | VoID file availability check for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.17875885963439941s
Reputation | Calculation of the PageRank for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.020313262939453125s
Interlinking | Calculation of Degree of Connection for LinkedDrugs: Linked Drug Product Data on a Global Scale took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LinkedDrugs: Linked Drug Product Data on a Global Scale took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for LinkedDrugs: Linked Drug Product Data on a Global Scale took 6.961822509765625e-05s
Believability | Calculation of trust value for LinkedDrugs: Linked Drug Product Data on a Global Scale took 5.4836273193359375e-06s
INFO | --- Analysis for linked-drugs took 1.9817817211151123s
Availability | SPARQL endpoint availability check for Linked EDGAR (OntologyCentral) took 3.886222839355469e-05s
Availability | VoID file availability check for Linked EDGAR (OntologyCentral) took 0.00022602081298828125s
Completeness | Calculation of interlinking completeness for Linked EDGAR (OntologyCentral) took 0.1760103702545166s
Reputation | Calculation of the PageRank for Linked EDGAR (OntologyCentral) took 0.020477771759033203s
Interlinking | Calculation of Degree of Connection for Linked EDGAR (OntologyCentral) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked EDGAR (OntologyCentral) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Linked EDGAR (OntologyCentral) took 9.560585021972656e-05s
Believability | Calculation of trust value for Linked EDGAR (OntologyCentral) took 1.3828277587890625e-05s
INFO | --- Analysis for linked-edgar took 1.9378254413604736s
Availability | SPARQL endpoint availability check for Linked Eurostat (OntologyCentral) took 4.076957702636719e-05s
Availability | VoID file availability check for Linked Eurostat (OntologyCentral) took 0.00020456314086914062s
Completeness | Calculation of interlinking completeness for Linked Eurostat (OntologyCentral) took 0.17307305335998535s
Reputation | Calculation of the PageRank for Linked Eurostat (OntologyCentral) took 0.020728349685668945s
Interlinking | Calculation of Degree of Connection for Linked Eurostat (OntologyCentral) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Eurostat (OntologyCentral) took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Linked Eurostat (OntologyCentral) took 9.274482727050781e-05s
Believability | Calculation of trust value for Linked Eurostat (OntologyCentral) took 1.0728836059570312e-05s
INFO | --- Analysis for linked-eurostat took 1.9493522644042969s
Availability | SPARQL endpoint availability check for linked hypernyms took 4.410743713378906e-05s
Availability | VoID file availability check for linked hypernyms took 0.0009267330169677734s
Completeness | Calculation of interlinking completeness for linked hypernyms took 0.18980717658996582s
Reputation | Calculation of the PageRank for linked hypernyms took 0.02226734161376953s
Interlinking | Calculation of Degree of Connection for linked hypernyms took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for linked hypernyms took 0.0007343292236328125s
Interlinking | Calculation of Clustering coefficient for linked hypernyms took 7.295608520507812e-05s
Believability | Calculation of trust value for linked hypernyms took 1.3113021850585938e-05s
INFO | --- Analysis for linked-hypernyms took 2.257984161376953s
Availability | SPARQL endpoint availability check for Linked Life Data took 4.172325134277344e-05s
Availability | VoID file availability check for Linked Life Data took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Linked Life Data took 0.17543506622314453s
Reputation | Calculation of the PageRank for Linked Life Data took 0.021402597427368164s
Interlinking | Calculation of Degree of Connection for Linked Life Data took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Linked Life Data took 0.0009520053863525391s
Interlinking | Calculation of Clustering coefficient for Linked Life Data took 4.9591064453125e-05s
Believability | Calculation of trust value for Linked Life Data took 1.1920928955078125e-05s
INFO | --- Analysis for linked-life-data took 3.024683713912964s
Availability | SPARQL endpoint availability check for Linked Logainm took 8.749961853027344e-05s
Availability | VoID file availability check for Linked Logainm took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Linked Logainm took 0.17280268669128418s
Reputation | Calculation of the PageRank for Linked Logainm took 0.02030658721923828s
Interlinking | Calculation of Degree of Connection for Linked Logainm took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Logainm took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Linked Logainm took 6.818771362304688e-05s
Believability | Calculation of trust value for Linked Logainm took 1.0728836059570312e-05s
INFO | --- Analysis for linked-logainm took 1.9624476432800293s
Availability | SPARQL endpoint availability check for Linked NUTS took 4.00543212890625e-05s
Availability | VoID file availability check for Linked NUTS took 0.0002200603485107422s
Completeness | Calculation of interlinking completeness for Linked NUTS took 0.18233227729797363s
Reputation | Calculation of the PageRank for Linked NUTS took 0.020322084426879883s
Interlinking | Calculation of Degree of Connection for Linked NUTS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked NUTS took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Linked NUTS took 4.935264587402344e-05s
Believability | Calculation of trust value for Linked NUTS took 1.0013580322265625e-05s
INFO | --- Analysis for linked-nuts took 1.9718687534332275s
Availability | SPARQL endpoint availability check for Linked Open Aalto Data Service took 4.100799560546875e-05s
Availability | VoID file availability check for Linked Open Aalto Data Service took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Linked Open Aalto Data Service took 0.18433856964111328s
Reputation | Calculation of the PageRank for Linked Open Aalto Data Service took 0.020221233367919922s
Interlinking | Calculation of Degree of Connection for Linked Open Aalto Data Service took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Open Aalto Data Service took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Linked Open Aalto Data Service took 2.7894973754882812e-05s
Believability | Calculation of trust value for Linked Open Aalto Data Service took 1.4543533325195312e-05s
INFO | --- Analysis for linked-open-aalto-data-service took 1.9532935619354248s
Availability | SPARQL endpoint availability check for Linked Open Camera (LinkedOpenData.it) took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Camera (LinkedOpenData.it) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Linked Open Camera (LinkedOpenData.it) took 0.18416357040405273s
Reputation | Calculation of the PageRank for Linked Open Camera (LinkedOpenData.it) took 0.02191758155822754s
Interlinking | Calculation of Degree of Connection for Linked Open Camera (LinkedOpenData.it) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Linked Open Camera (LinkedOpenData.it) took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for Linked Open Camera (LinkedOpenData.it) took 3.8623809814453125e-05s
Believability | Calculation of trust value for Linked Open Camera (LinkedOpenData.it) took 1.0967254638671875e-05s
INFO | --- Analysis for linked-open-camera took 2.0012545585632324s
Availability | SPARQL endpoint availability check for Linked Open Commerce took 8.034706115722656e-05s
Availability | VoID file availability check for Linked Open Commerce took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for Linked Open Commerce took 0.17639756202697754s
Reputation | Calculation of the PageRank for Linked Open Commerce took 0.021630048751831055s
Interlinking | Calculation of Degree of Connection for Linked Open Commerce took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Commerce took 0.0007555484771728516s
Interlinking | Calculation of Clustering coefficient for Linked Open Commerce took 2.8848648071289062e-05s
Believability | Calculation of trust value for Linked Open Commerce took 1.0967254638671875e-05s
INFO | --- Analysis for linked-open-commerce took 2.017085075378418s
Availability | SPARQL endpoint availability check for Linked Open Data of Ecology took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Open Data of Ecology took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Linked Open Data of Ecology took 0.18196463584899902s
Reputation | Calculation of the PageRank for Linked Open Data of Ecology took 0.020126819610595703s
Interlinking | Calculation of Degree of Connection for Linked Open Data of Ecology took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Data of Ecology took 0.0007815361022949219s
Interlinking | Calculation of Clustering coefficient for Linked Open Data of Ecology took 0.00010275840759277344s
Believability | Calculation of trust value for Linked Open Data of Ecology took 1.0251998901367188e-05s
INFO | --- Analysis for linked-open-data-of-ecology took 2.00545334815979s
Availability | SPARQL endpoint availability check for Linked Open Numbers took 7.772445678710938e-05s
Availability | VoID file availability check for Linked Open Numbers took 0.0004887580871582031s
Completeness | Calculation of interlinking completeness for Linked Open Numbers took 0.18361973762512207s
Reputation | Calculation of the PageRank for Linked Open Numbers took 0.020275592803955078s
Interlinking | Calculation of Degree of Connection for Linked Open Numbers took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Linked Open Numbers took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Linked Open Numbers took 8.749961853027344e-05s
Believability | Calculation of trust value for Linked Open Numbers took 1.0728836059570312e-05s
INFO | --- Analysis for linked-open-numbers took 1.9647903442382812s
Availability | SPARQL endpoint availability check for Linked Open Piracy took 8.487701416015625e-05s
Availability | VoID file availability check for Linked Open Piracy took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Linked Open Piracy took 0.18056488037109375s
Reputation | Calculation of the PageRank for Linked Open Piracy took 0.022152185440063477s
Interlinking | Calculation of Degree of Connection for Linked Open Piracy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Open Piracy took 0.0007328987121582031s
Interlinking | Calculation of Clustering coefficient for Linked Open Piracy took 2.8371810913085938e-05s
Believability | Calculation of trust value for Linked Open Piracy took 1.049041748046875e-05s
INFO | --- Analysis for linked-open-piracy took 2.0103683471679688s
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.0004742145538330078s
Completeness | Calculation of interlinking completeness for Linked Open Senate (linkedopendata.it) took 0.19376516342163086s
Reputation | Calculation of the PageRank for Linked Open Senate (linkedopendata.it) took 0.020754575729370117s
Interlinking | Calculation of Degree of Connection for Linked Open Senate (linkedopendata.it) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Senate (linkedopendata.it) took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Linked Open Senate (linkedopendata.it) took 3.075599670410156e-05s
Believability | Calculation of trust value for Linked Open Senate (linkedopendata.it) took 1.049041748046875e-05s
INFO | --- Analysis for linked-open-senate took 1.9989047050476074s
Availability | SPARQL endpoint availability check for Linked Open Vocabularies (LOV) took 8.130073547363281e-05s
Availability | VoID file availability check for Linked Open Vocabularies (LOV) took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Linked Open Vocabularies (LOV) took 0.1723308563232422s
Reputation | Calculation of the PageRank for Linked Open Vocabularies (LOV) took 0.020446300506591797s
Interlinking | Calculation of Degree of Connection for Linked Open Vocabularies (LOV) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Open Vocabularies (LOV) took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Linked Open Vocabularies (LOV) took 4.673004150390625e-05s
Believability | Calculation of trust value for Linked Open Vocabularies (LOV) took 1.1205673217773438e-05s
INFO | --- Analysis for linked-open-vocabularies-lov took 1.9520821571350098s
Availability | SPARQL endpoint availability check for Linked Periodicals Database took 4.4345855712890625e-05s
Availability | VoID file availability check for Linked Periodicals Database took 0.00021529197692871094s
Completeness | Calculation of interlinking completeness for Linked Periodicals Database took 0.1677989959716797s
Reputation | Calculation of the PageRank for Linked Periodicals Database took 0.0201718807220459s
Interlinking | Calculation of Degree of Connection for Linked Periodicals Database took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Periodicals Database took 0.0007426738739013672s
Interlinking | Calculation of Clustering coefficient for Linked Periodicals Database took 3.528594970703125e-05s
Believability | Calculation of trust value for Linked Periodicals Database took 5.245208740234375e-06s
INFO | --- Analysis for linked-periodicals took 1.9429552555084229s
Availability | SPARQL endpoint availability check for Linked Index took 3.886222839355469e-05s
Availability | VoID file availability check for Linked Index took 0.00020956993103027344s
Completeness | Calculation of interlinking completeness for Linked Index took 0.1697084903717041s
Reputation | Calculation of the PageRank for Linked Index took 0.020480871200561523s
Interlinking | Calculation of Degree of Connection for Linked Index took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Linked Index took 0.0007288455963134766s
Interlinking | Calculation of Clustering coefficient for Linked Index took 8.273124694824219e-05s
Believability | Calculation of trust value for Linked Index took 7.867813110351562e-06s
INFO | --- Analysis for linked-stockindex took 2.0433461666107178s
Availability | SPARQL endpoint availability check for Linked Structured Product Labels took 4.0531158447265625e-05s
Availability | VoID file availability check for Linked Structured Product Labels took 0.0004525184631347656s
Completeness | Calculation of interlinking completeness for Linked Structured Product Labels took 0.173264741897583s
Reputation | Calculation of the PageRank for Linked Structured Product Labels took 0.022371768951416016s
Interlinking | Calculation of Degree of Connection for Linked Structured Product Labels took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Structured Product Labels took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Linked Structured Product Labels took 3.790855407714844e-05s
Believability | Calculation of trust value for Linked Structured Product Labels took 1.049041748046875e-05s
INFO | --- Analysis for linked-structured-product-labels took 1.9573299884796143s
Availability | SPARQL endpoint availability check for Linked Taiwan Geo-Names took 4.267692565917969e-05s
Availability | VoID file availability check for Linked Taiwan Geo-Names took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for Linked Taiwan Geo-Names took 0.17715692520141602s
Reputation | Calculation of the PageRank for Linked Taiwan Geo-Names took 0.020076513290405273s
Interlinking | Calculation of Degree of Connection for Linked Taiwan Geo-Names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Taiwan Geo-Names took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Linked Taiwan Geo-Names took 3.1948089599609375e-05s
Believability | Calculation of trust value for Linked Taiwan Geo-Names took 9.775161743164062e-06s
INFO | --- Analysis for linked-taiwan-geo-names took 1.9877629280090332s
Availability | SPARQL endpoint availability check for Linked TCGA took 8.416175842285156e-05s
Availability | VoID file availability check for Linked TCGA took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Linked TCGA took 0.17249512672424316s
Reputation | Calculation of the PageRank for Linked TCGA took 0.02093195915222168s
Interlinking | Calculation of Degree of Connection for Linked TCGA took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Linked TCGA took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Linked TCGA took 9.012222290039062e-05s
Believability | Calculation of trust value for Linked TCGA took 1.0967254638671875e-05s
INFO | --- Analysis for linked-tcga took 1.9454171657562256s
Availability | SPARQL endpoint availability check for Linked User Feedback took 0.00010228157043457031s
Availability | VoID file availability check for Linked User Feedback took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Linked User Feedback took 0.1748497486114502s
Reputation | Calculation of the PageRank for Linked User Feedback took 0.02054286003112793s
Interlinking | Calculation of Degree of Connection for Linked User Feedback took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked User Feedback took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Linked User Feedback took 3.814697265625e-05s
Believability | Calculation of trust value for Linked User Feedback took 1.0728836059570312e-05s
INFO | --- Analysis for linked-user-feedback took 1.9825489521026611s
Availability | SPARQL endpoint availability check for USPTO Patent data took 8.034706115722656e-05s
Availability | VoID file availability check for USPTO Patent data took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for USPTO Patent data took 0.1811842918395996s
Reputation | Calculation of the PageRank for USPTO Patent data took 0.020322322845458984s
Interlinking | Calculation of Degree of Connection for USPTO Patent data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for USPTO Patent data took 0.0007276535034179688s
Interlinking | Calculation of Clustering coefficient for USPTO Patent data took 7.653236389160156e-05s
Believability | Calculation of trust value for USPTO Patent data took 1.1682510375976562e-05s
INFO | --- Analysis for linked-uspto-patent-data took 1.949120283126831s
Availability | SPARQL endpoint availability check for Linked Web APIs dataset took 7.987022399902344e-05s
Availability | VoID file availability check for Linked Web APIs dataset took 0.00020265579223632812s
Completeness | Calculation of interlinking completeness for Linked Web APIs dataset took 0.18431735038757324s
Reputation | Calculation of the PageRank for Linked Web APIs dataset took 0.020623207092285156s
Interlinking | Calculation of Degree of Connection for Linked Web APIs dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Linked Web APIs dataset took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Linked Web APIs dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for Linked Web APIs dataset took 1.1205673217773438e-05s
INFO | --- Analysis for linked-web-apis took 1.969789743423462s
Availability | SPARQL endpoint availability check for linkedarc.net archaeological datasets took 0.00010466575622558594s
Availability | VoID file availability check for linkedarc.net archaeological datasets took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for linkedarc.net archaeological datasets took 0.17194557189941406s
Reputation | Calculation of the PageRank for linkedarc.net archaeological datasets took 0.020777463912963867s
Interlinking | Calculation of Degree of Connection for linkedarc.net archaeological datasets took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for linkedarc.net archaeological datasets took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for linkedarc.net archaeological datasets took 3.0279159545898438e-05s
Believability | Calculation of trust value for linkedarc.net archaeological datasets took 1.049041748046875e-05s
INFO | --- Analysis for linkedarc took 1.9861176013946533s
Availability | SPARQL endpoint availability check for Linked Crowdsourced Data took 0.00010085105895996094s
Availability | VoID file availability check for Linked Crowdsourced Data took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Linked Crowdsourced Data took 0.17319822311401367s
Reputation | Calculation of the PageRank for Linked Crowdsourced Data took 0.02057933807373047s
Interlinking | Calculation of Degree of Connection for Linked Crowdsourced Data took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Crowdsourced Data took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for Linked Crowdsourced Data took 3.409385681152344e-05s
Believability | Calculation of trust value for Linked Crowdsourced Data took 1.1920928955078125e-05s
INFO | --- Analysis for linkedcrowdsourceddata took 1.998633623123169s
Availability | SPARQL endpoint availability check for LinkedCT took 4.00543212890625e-05s
Availability | VoID file availability check for LinkedCT took 0.000457763671875s
Completeness | Calculation of interlinking completeness for LinkedCT took 0.17647886276245117s
Reputation | Calculation of the PageRank for LinkedCT took 0.021241426467895508s
Interlinking | Calculation of Degree of Connection for LinkedCT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LinkedCT took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for LinkedCT took 9.632110595703125e-05s
Believability | Calculation of trust value for LinkedCT took 1.0728836059570312e-05s
INFO | --- Analysis for linkedct took 1.9565045833587646s
Availability | SPARQL endpoint availability check for LinkedGeoData took 8.153915405273438e-05s
Availability | VoID file availability check for LinkedGeoData took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for LinkedGeoData took 0.17676806449890137s
Reputation | Calculation of the PageRank for LinkedGeoData took 0.020372390747070312s
Interlinking | Calculation of Degree of Connection for LinkedGeoData took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LinkedGeoData took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData took 0.00011491775512695312s
Believability | Calculation of trust value for LinkedGeoData took 1.1205673217773438e-05s
INFO | --- Analysis for linkedgeodata took 1.9905831813812256s
Availability | SPARQL endpoint availability check for LinkedGeoData: Aerodromes took 8.606910705566406e-05s
Availability | VoID file availability check for LinkedGeoData: Aerodromes took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for LinkedGeoData: Aerodromes took 0.18705177307128906s
Reputation | Calculation of the PageRank for LinkedGeoData: Aerodromes took 0.020321369171142578s
Interlinking | Calculation of Degree of Connection for LinkedGeoData: Aerodromes took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LinkedGeoData: Aerodromes took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for LinkedGeoData: Aerodromes took 3.0040740966796875e-05s
Believability | Calculation of trust value for LinkedGeoData: Aerodromes took 1.0967254638671875e-05s
INFO | --- Analysis for linkedgeodata-aerodromes took 2.0493433475494385s
Availability | SPARQL endpoint availability check for LinkedLCCN took 1.0437114238739014s
Availability | VoID file availability check for LinkedLCCN took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for LinkedLCCN took 0.1750028133392334s
Reputation | Calculation of the PageRank for LinkedLCCN took 0.021801233291625977s
Interlinking | Calculation of Degree of Connection for LinkedLCCN took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LinkedLCCN took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for LinkedLCCN took 0.00010442733764648438s
Believability | Calculation of trust value for LinkedLCCN took 1.0967254638671875e-05s
INFO | --- Analysis for linkedlccn took 3.0539259910583496s
Availability | SPARQL endpoint availability check for LinkedMarkMail took 8.440017700195312e-05s
Availability | VoID file availability check for LinkedMarkMail took 0.000457763671875s
Completeness | Calculation of interlinking completeness for LinkedMarkMail took 0.17817401885986328s
Reputation | Calculation of the PageRank for LinkedMarkMail took 0.021233558654785156s
Interlinking | Calculation of Degree of Connection for LinkedMarkMail took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LinkedMarkMail took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for LinkedMarkMail took 3.5762786865234375e-05s
Believability | Calculation of trust value for LinkedMarkMail took 1.0728836059570312e-05s
INFO | --- Analysis for linkedmarkmail took 1.9619183540344238s
Availability | SPARQL endpoint availability check for Linked Movie DataBase took 1.064359188079834s
Availability | VoID file availability check for Linked Movie DataBase took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for Linked Movie DataBase took 0.17366504669189453s
Reputation | Calculation of the PageRank for Linked Movie DataBase took 0.020701885223388672s
Interlinking | Calculation of Degree of Connection for Linked Movie DataBase took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linked Movie DataBase took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Linked Movie DataBase took 0.0001304149627685547s
Believability | Calculation of trust value for Linked Movie DataBase took 1.430511474609375e-05s
INFO | --- Analysis for linkedmdb took 3.3634588718414307s
Availability | SPARQL endpoint availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 3.910064697265625e-05s
Availability | VoID file availability check for LinkedSpending: OpenSpending becomes Linked Open Data took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for LinkedSpending: OpenSpending becomes Linked Open Data took 0.1979844570159912s
Reputation | Calculation of the PageRank for LinkedSpending: OpenSpending becomes Linked Open Data took 0.02089405059814453s
Interlinking | Calculation of Degree of Connection for LinkedSpending: OpenSpending becomes Linked Open Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LinkedSpending: OpenSpending becomes Linked Open Data took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for LinkedSpending: OpenSpending becomes Linked Open Data took 7.62939453125e-05s
Believability | Calculation of trust value for LinkedSpending: OpenSpending becomes Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for linkedspending took 1.9955246448516846s
Availability | SPARQL endpoint availability check for LinkedStats took 8.082389831542969e-05s
Availability | VoID file availability check for LinkedStats took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for LinkedStats took 0.17558693885803223s
Reputation | Calculation of the PageRank for LinkedStats took 0.02027106285095215s
Interlinking | Calculation of Degree of Connection for LinkedStats took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LinkedStats took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for LinkedStats took 2.86102294921875e-05s
Believability | Calculation of trust value for LinkedStats took 1.0728836059570312e-05s
INFO | --- Analysis for linkedstats took 2.0415384769439697s
Availability | SPARQL endpoint availability check for LinkedUp Catalogue of Educational Datasets took 3.933906555175781e-05s
Availability | VoID file availability check for LinkedUp Catalogue of Educational Datasets took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for LinkedUp Catalogue of Educational Datasets took 0.18521904945373535s
Reputation | Calculation of the PageRank for LinkedUp Catalogue of Educational Datasets took 0.022519350051879883s
Interlinking | Calculation of Degree of Connection for LinkedUp Catalogue of Educational Datasets took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for LinkedUp Catalogue of Educational Datasets took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for LinkedUp Catalogue of Educational Datasets took 3.123283386230469e-05s
Believability | Calculation of trust value for LinkedUp Catalogue of Educational Datasets took 1.1205673217773438e-05s
INFO | --- Analysis for linkedup-catalogue-of-educational-datasets took 2.0063984394073486s
Availability | SPARQL endpoint availability check for Linking Open Drug Data (LODD) took 9.942054748535156e-05s
Availability | VoID file availability check for Linking Open Drug Data (LODD) took 0.0002512931823730469s
Completeness | Calculation of interlinking completeness for Linking Open Drug Data (LODD) took 0.1733112335205078s
Reputation | Calculation of the PageRank for Linking Open Drug Data (LODD) took 0.020166873931884766s
Interlinking | Calculation of Degree of Connection for Linking Open Drug Data (LODD) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linking Open Drug Data (LODD) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Linking Open Drug Data (LODD) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Linking Open Drug Data (LODD) took 1.430511474609375e-05s
INFO | --- Analysis for linking-open-drug-data took 1.9637126922607422s
Availability | SPARQL endpoint availability check for LinkLion - A Link Repository for the Web of Data took 8.153915405273438e-05s
Availability | VoID file availability check for LinkLion - A Link Repository for the Web of Data took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for LinkLion - A Link Repository for the Web of Data took 0.1815333366394043s
Reputation | Calculation of the PageRank for LinkLion - A Link Repository for the Web of Data took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for LinkLion - A Link Repository for the Web of Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for LinkLion - A Link Repository for the Web of Data took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for LinkLion - A Link Repository for the Web of Data took 0.00010347366333007812s
Believability | Calculation of trust value for LinkLion - A Link Repository for the Web of Data took 1.3113021850585938e-05s
INFO | --- Analysis for linklion took 2.0057499408721924s
Availability | SPARQL endpoint availability check for Lion's Den took 4.029273986816406e-05s
Availability | VoID file availability check for Lion's Den took 0.0005142688751220703s
Completeness | Calculation of interlinking completeness for Lion's Den took 0.18361520767211914s
Reputation | Calculation of the PageRank for Lion's Den took 0.020907163619995117s
Interlinking | Calculation of Degree of Connection for Lion's Den took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Lion's Den took 0.001009225845336914s
Interlinking | Calculation of Clustering coefficient for Lion's Den took 3.743171691894531e-05s
Believability | Calculation of trust value for Lion's Den took 1.2874603271484375e-05s
INFO | --- Analysis for lionsden took 1.9708318710327148s
Availability | SPARQL endpoint availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 23.281559944152832s
Availability | VoID file availability check for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for Lista de  Encabezamientos de Materia as Linked Open Data took 0.17812108993530273s
Reputation | Calculation of the PageRank for Lista de  Encabezamientos de Materia as Linked Open Data took 0.022071123123168945s
Interlinking | Calculation of Degree of Connection for Lista de  Encabezamientos de Materia as Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Lista de  Encabezamientos de Materia as Linked Open Data took 0.0006928443908691406s
Interlinking | Calculation of Clustering coefficient for Lista de  Encabezamientos de Materia as Linked Open Data took 4.887580871582031e-05s
Believability | Calculation of trust value for Lista de  Encabezamientos de Materia as Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for lista-encabezamientos-materia took 25.695923805236816s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data took 3.9577484130859375e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data took 0.18711519241333008s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data took 0.021134138107299805s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data took 1.4066696166992188e-05s
INFO | --- Analysis for livtdm took 2.0477492809295654s
Availability | SPARQL endpoint availability check for LIVIVO Text Mining Data 2017 took 8.344650268554688e-05s
Availability | VoID file availability check for LIVIVO Text Mining Data 2017 took 0.0005700588226318359s
Completeness | Calculation of interlinking completeness for LIVIVO Text Mining Data 2017 took 0.1851515769958496s
Reputation | Calculation of the PageRank for LIVIVO Text Mining Data 2017 took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for LIVIVO Text Mining Data 2017 took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for LIVIVO Text Mining Data 2017 took 0.0010232925415039062s
Interlinking | Calculation of Clustering coefficient for LIVIVO Text Mining Data 2017 took 3.5762786865234375e-05s
Believability | Calculation of trust value for LIVIVO Text Mining Data 2017 took 8.58306884765625e-06s
INFO | --- Analysis for livtdm2017 took 1.9987130165100098s
Availability | SPARQL endpoint availability check for Linked Open Biomedical Investigations took 4.291534423828125e-05s
Availability | VoID file availability check for Linked Open Biomedical Investigations took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Linked Open Biomedical Investigations took 0.1852736473083496s
Reputation | Calculation of the PageRank for Linked Open Biomedical Investigations took 0.02092766761779785s
Interlinking | Calculation of Degree of Connection for Linked Open Biomedical Investigations took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked Open Biomedical Investigations took 0.0007963180541992188s
Interlinking | Calculation of Clustering coefficient for Linked Open Biomedical Investigations took 3.9577484130859375e-05s
Believability | Calculation of trust value for Linked Open Biomedical Investigations took 1.2874603271484375e-05s
INFO | --- Analysis for lobi took 2.0199708938598633s
Availability | SPARQL endpoint availability check for lobid-organisations took 8.416175842285156e-05s
Availability | VoID file availability check for lobid-organisations took 0.00048661231994628906s
Completeness | Calculation of interlinking completeness for lobid-organisations took 0.18660306930541992s
Reputation | Calculation of the PageRank for lobid-organisations took 0.021419286727905273s
Interlinking | Calculation of Degree of Connection for lobid-organisations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for lobid-organisations took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for lobid-organisations took 8.940696716308594e-05s
Believability | Calculation of trust value for lobid-organisations took 1.2874603271484375e-05s
INFO | --- Analysis for lobid-organisations took 2.014953374862671s
Availability | SPARQL endpoint availability check for lobid-Bibliographic Resources took 8.416175842285156e-05s
Availability | VoID file availability check for lobid-Bibliographic Resources took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for lobid-Bibliographic Resources took 0.18101930618286133s
Reputation | Calculation of the PageRank for lobid-Bibliographic Resources took 0.020517826080322266s
Interlinking | Calculation of Degree of Connection for lobid-Bibliographic Resources took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for lobid-Bibliographic Resources took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for lobid-Bibliographic Resources took 9.274482727050781e-05s
Believability | Calculation of trust value for lobid-Bibliographic Resources took 1.2159347534179688e-05s
INFO | --- Analysis for lobid-resources took 1.976921558380127s
Availability | SPARQL endpoint availability check for Linked Open Colors took 8.296966552734375e-05s
Availability | VoID file availability check for Linked Open Colors took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for Linked Open Colors took 0.18433713912963867s
Reputation | Calculation of the PageRank for Linked Open Colors took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for Linked Open Colors took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Linked Open Colors took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Linked Open Colors took 6.723403930664062e-05s
Believability | Calculation of trust value for Linked Open Colors took 1.239776611328125e-05s
INFO | --- Analysis for loc took 2.0116488933563232s
Availability | SPARQL endpoint availability check for Location Ontology took 8.702278137207031e-05s
Availability | VoID file availability check for Location Ontology took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Location Ontology took 0.18177175521850586s
Reputation | Calculation of the PageRank for Location Ontology took 0.020205259323120117s
Interlinking | Calculation of Degree of Connection for Location Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Location Ontology took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Location Ontology took 2.956390380859375e-05s
Believability | Calculation of trust value for Location Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Location_Ontology took 1.9711289405822754s
Availability | SPARQL endpoint availability check for Linked Open Computer Vision took 4.029273986816406e-05s
Availability | VoID file availability check for Linked Open Computer Vision took 0.0004992485046386719s
Completeness | Calculation of interlinking completeness for Linked Open Computer Vision took 0.180128812789917s
Reputation | Calculation of the PageRank for Linked Open Computer Vision took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for Linked Open Computer Vision took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Linked Open Computer Vision took 0.0009171962738037109s
Interlinking | Calculation of Clustering coefficient for Linked Open Computer Vision took 3.457069396972656e-05s
Believability | Calculation of trust value for Linked Open Computer Vision took 1.2874603271484375e-05s
INFO | --- Analysis for locv took 2.000816583633423s
Availability | SPARQL endpoint availability check for LOD-a-lot took 8.559226989746094e-05s
Availability | VoID file availability check for LOD-a-lot took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for LOD-a-lot took 0.17797517776489258s
Reputation | Calculation of the PageRank for LOD-a-lot took 0.020015239715576172s
Interlinking | Calculation of Degree of Connection for LOD-a-lot took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for LOD-a-lot took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for LOD-a-lot took 2.765655517578125e-05s
Believability | Calculation of trust value for LOD-a-lot took 1.239776611328125e-05s
INFO | --- Analysis for lod-a-lot took 1.9645957946777344s
Availability | SPARQL endpoint availability check for Scuole Italiane (linkedopendata.it) took 7.891654968261719e-05s
Availability | VoID file availability check for Scuole Italiane (linkedopendata.it) took 0.0002167224884033203s
Completeness | Calculation of interlinking completeness for Scuole Italiane (linkedopendata.it) took 0.17604851722717285s
Reputation | Calculation of the PageRank for Scuole Italiane (linkedopendata.it) took 0.020028114318847656s
Interlinking | Calculation of Degree of Connection for Scuole Italiane (linkedopendata.it) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Scuole Italiane (linkedopendata.it) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Scuole Italiane (linkedopendata.it) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Scuole Italiane (linkedopendata.it) took 8.344650268554688e-06s
INFO | --- Analysis for lod-it_scuole-italiane took 1.9716622829437256s
Availability | SPARQL endpoint availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 3.933906555175781e-05s
Availability | VoID file availability check for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0004405975341796875s
Completeness | Calculation of interlinking completeness for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.18186306953430176s
Reputation | Calculation of the PageRank for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.02225351333618164s
Interlinking | Calculation of Degree of Connection for Open Data Web - a CKAN based linked open data repository in Taiwan took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data Web - a CKAN based linked open data repository in Taiwan took 0.0007252693176269531s
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 5.7220458984375e-06s
INFO | --- Analysis for lod-taiwan took 1.9689841270446777s
Availability | SPARQL endpoint availability check for LOD2 Project Wiki took 8.96453857421875e-05s
Availability | VoID file availability check for LOD2 Project Wiki took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for LOD2 Project Wiki took 0.18983793258666992s
Reputation | Calculation of the PageRank for LOD2 Project Wiki took 0.020237445831298828s
Interlinking | Calculation of Degree of Connection for LOD2 Project Wiki took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for LOD2 Project Wiki took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for LOD2 Project Wiki took 8.153915405273438e-05s
Believability | Calculation of trust value for LOD2 Project Wiki took 1.2874603271484375e-05s
INFO | --- Analysis for lod2-project-wiki took 1.996511697769165s
Availability | SPARQL endpoint availability check for LODAC BDLS took 4.3392181396484375e-05s
Availability | VoID file availability check for LODAC BDLS took 0.00023746490478515625s
Completeness | Calculation of interlinking completeness for LODAC BDLS took 0.17374396324157715s
Reputation | Calculation of the PageRank for LODAC BDLS took 0.020127058029174805s
Interlinking | Calculation of Degree of Connection for LODAC BDLS took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for LODAC BDLS took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for LODAC BDLS took 6.651878356933594e-05s
Believability | Calculation of trust value for LODAC BDLS took 1.2636184692382812e-05s
INFO | --- Analysis for lodac-bdls took 1.9844214916229248s
Availability | SPARQL endpoint availability check for LODRussia Math took 8.082389831542969e-05s
Availability | VoID file availability check for LODRussia Math took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for LODRussia Math took 0.19499516487121582s
Reputation | Calculation of the PageRank for LODRussia Math took 0.02025771141052246s
Interlinking | Calculation of Degree of Connection for LODRussia Math took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LODRussia Math took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for LODRussia Math took 2.7894973754882812e-05s
Believability | Calculation of trust value for LODRussia Math took 1.1205673217773438e-05s
INFO | --- Analysis for lodrussia-math took 2.025371551513672s
Availability | SPARQL endpoint availability check for LODRussia Nano took 3.8623809814453125e-05s
Availability | VoID file availability check for LODRussia Nano took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for LODRussia Nano took 0.1767258644104004s
Reputation | Calculation of the PageRank for LODRussia Nano took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for LODRussia Nano took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LODRussia Nano took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for LODRussia Nano took 2.8133392333984375e-05s
Believability | Calculation of trust value for LODRussia Nano took 1.2874603271484375e-05s
INFO | --- Analysis for lodrussia-nano took 1.9914636611938477s
Availability | SPARQL endpoint availability check for LODStats took 7.915496826171875e-05s
Availability | VoID file availability check for LODStats took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for LODStats took 0.1797959804534912s
Reputation | Calculation of the PageRank for LODStats took 0.022844791412353516s
Interlinking | Calculation of Degree of Connection for LODStats took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LODStats took 0.0007905960083007812s
Interlinking | Calculation of Clustering coefficient for LODStats took 3.1948089599609375e-05s
Believability | Calculation of trust value for LODStats took 1.0967254638671875e-05s
INFO | --- Analysis for lodstats took 2.00498366355896s
Availability | SPARQL endpoint availability check for LODUM took 8.416175842285156e-05s
Availability | VoID file availability check for LODUM took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for LODUM took 0.17476463317871094s
Reputation | Calculation of the PageRank for LODUM took 0.021209001541137695s
Interlinking | Calculation of Degree of Connection for LODUM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for LODUM took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for LODUM took 3.147125244140625e-05s
Believability | Calculation of trust value for LODUM took 1.2874603271484375e-05s
INFO | --- Analysis for lodum took 1.9484083652496338s
Availability | SPARQL endpoint availability check for lofd took 9.1552734375e-05s
Availability | VoID file availability check for lofd took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for lofd took 0.1818525791168213s
Reputation | Calculation of the PageRank for lofd took 0.02086043357849121s
Interlinking | Calculation of Degree of Connection for lofd took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for lofd took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for lofd took 2.6941299438476562e-05s
Believability | Calculation of trust value for lofd took 1.239776611328125e-05s
INFO | --- Analysis for lofd took 2.0032694339752197s
Availability | SPARQL endpoint availability check for Linking Italian University Statistics Project took 8.511543273925781e-05s
Availability | VoID file availability check for Linking Italian University Statistics Project took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Linking Italian University Statistics Project took 0.1823866367340088s
Reputation | Calculation of the PageRank for Linking Italian University Statistics Project took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Linking Italian University Statistics Project took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Linking Italian University Statistics Project took 0.0007393360137939453s
Interlinking | Calculation of Clustering coefficient for Linking Italian University Statistics Project took 5.030632019042969e-05s
Believability | Calculation of trust value for Linking Italian University Statistics Project took 1.2636184692382812e-05s
INFO | --- Analysis for loius took 2.003552198410034s
Availability | SPARQL endpoint availability check for LOIUS project - Linking Italian University Statistics took 8.416175842285156e-05s
Availability | VoID file availability check for LOIUS project - Linking Italian University Statistics took 0.0004458427429199219s
Completeness | Calculation of interlinking completeness for LOIUS project - Linking Italian University Statistics took 0.18356585502624512s
Reputation | Calculation of the PageRank for LOIUS project - Linking Italian University Statistics took 0.02303481101989746s
Interlinking | Calculation of Degree of Connection for LOIUS project - Linking Italian University Statistics took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for LOIUS project - Linking Italian University Statistics took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for LOIUS project - Linking Italian University Statistics took 2.8371810913085938e-05s
Believability | Calculation of trust value for LOIUS project - Linking Italian University Statistics took 1.2636184692382812e-05s
INFO | --- Analysis for loius-linking-italian-university-statistics took 2.0076143741607666s
Availability | SPARQL endpoint availability check for The London Gazette - Gazettes Data took 4.4345855712890625e-05s
Availability | VoID file availability check for The London Gazette - Gazettes Data took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for The London Gazette - Gazettes Data took 0.18046855926513672s
Reputation | Calculation of the PageRank for The London Gazette - Gazettes Data took 0.02258753776550293s
Interlinking | Calculation of Degree of Connection for The London Gazette - Gazettes Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for The London Gazette - Gazettes Data took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for The London Gazette - Gazettes Data took 4.9114227294921875e-05s
Believability | Calculation of trust value for The London Gazette - Gazettes Data took 1.33514404296875e-05s
INFO | --- Analysis for london-gazette took 2.000584363937378s
Availability | SPARQL endpoint availability check for Weather Stations took 8.511543273925781e-05s
Availability | VoID file availability check for Weather Stations took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for Weather Stations took 0.17377638816833496s
Reputation | Calculation of the PageRank for Weather Stations took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for Weather Stations took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Weather Stations took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Weather Stations took 7.510185241699219e-05s
Believability | Calculation of trust value for Weather Stations took 1.2636184692382812e-05s
INFO | --- Analysis for los_metar took 2.0152781009674072s
Availability | SPARQL endpoint availability check for Lotico took 5.1975250244140625e-05s
Availability | VoID file availability check for Lotico took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Lotico took 0.17404484748840332s
Reputation | Calculation of the PageRank for Lotico took 0.022325515747070312s
Interlinking | Calculation of Degree of Connection for Lotico took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Lotico took 0.0008883476257324219s
Interlinking | Calculation of Clustering coefficient for Lotico took 8.821487426757812e-05s
Believability | Calculation of trust value for Lotico took 6.0558319091796875e-05s
INFO | --- Analysis for lotico took 2.0026519298553467s
Availability | SPARQL endpoint availability check for Lower Layer Super Output Areas took 8.392333984375e-05s
Availability | VoID file availability check for Lower Layer Super Output Areas took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Lower Layer Super Output Areas took 0.1738119125366211s
Reputation | Calculation of the PageRank for Lower Layer Super Output Areas took 0.020331144332885742s
Interlinking | Calculation of Degree of Connection for Lower Layer Super Output Areas took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Lower Layer Super Output Areas took 0.0008153915405273438s
Interlinking | Calculation of Clustering coefficient for Lower Layer Super Output Areas took 2.7418136596679688e-05s
Believability | Calculation of trust value for Lower Layer Super Output Areas took 1.2874603271484375e-05s
INFO | --- Analysis for lower-layer-super-output-areas took 2.0037896633148193s
Availability | SPARQL endpoint availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 4.100799560546875e-05s
Availability | VoID file availability check for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0002472400665283203s
Completeness | Calculation of interlinking completeness for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.1755228042602539s
Reputation | Calculation of the PageRank for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.02013540267944336s
Interlinking | Calculation of Degree of Connection for Polish Land Parcel Information System (LPIS) dataset @PSNC took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Polish Land Parcel Information System (LPIS) dataset @PSNC took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Polish Land Parcel Information System (LPIS) dataset @PSNC took 2.6702880859375e-05s
Believability | Calculation of trust value for Polish Land Parcel Information System (LPIS) dataset @PSNC took 1.239776611328125e-05s
INFO | --- Analysis for LPIS_(Poland) took 2.0294203758239746s
Availability | SPARQL endpoint availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 3.9577484130859375e-05s
Availability | VoID file availability check for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.18098902702331543s
Reputation | Calculation of the PageRank for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.020270347595214844s
Interlinking | Calculation of Degree of Connection for Land parcel dataset (LPIS) from Czech Republic @PSNC took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Land parcel dataset (LPIS) from Czech Republic @PSNC took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Land parcel dataset (LPIS) from Czech Republic @PSNC took 2.7894973754882812e-05s
Believability | Calculation of trust value for Land parcel dataset (LPIS) from Czech Republic @PSNC took 1.3828277587890625e-05s
INFO | --- Analysis for LPIS_Czech_Republic took 2.0065762996673584s
Availability | SPARQL endpoint availability check for A collection of Authors for LREC2014 and related Workshops took 3.981590270996094e-05s
Availability | VoID file availability check for A collection of Authors for LREC2014 and related Workshops took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for A collection of Authors for LREC2014 and related Workshops took 0.18015408515930176s
Reputation | Calculation of the PageRank for A collection of Authors for LREC2014 and related Workshops took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for A collection of Authors for LREC2014 and related Workshops took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for A collection of Authors for LREC2014 and related Workshops took 0.0007081031799316406s
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 1.049041748046875e-05s
INFO | --- Analysis for lremap-auth took 1.950883150100708s
Availability | SPARQL endpoint availability check for LREC2014 and related Workshops took 8.177757263183594e-05s
Availability | VoID file availability check for LREC2014 and related Workshops took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for LREC2014 and related Workshops took 0.1908106803894043s
Reputation | Calculation of the PageRank for LREC2014 and related Workshops took 0.02275252342224121s
Interlinking | Calculation of Degree of Connection for LREC2014 and related Workshops took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for LREC2014 and related Workshops took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for LREC2014 and related Workshops took 3.123283386230469e-05s
Believability | Calculation of trust value for LREC2014 and related Workshops took 1.1920928955078125e-05s
INFO | --- Analysis for lremap-conf took 1.9838969707489014s
Availability | SPARQL endpoint availability check for First not-normalized set of language resources from LREC2014 took 8.0108642578125e-05s
Availability | VoID file availability check for First not-normalized set of language resources from LREC2014 took 0.0008389949798583984s
Completeness | Calculation of interlinking completeness for First not-normalized set of language resources from LREC2014 took 0.17582297325134277s
Reputation | Calculation of the PageRank for First not-normalized set of language resources from LREC2014 took 0.02132701873779297s
Interlinking | Calculation of Degree of Connection for First not-normalized set of language resources from LREC2014 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for First not-normalized set of language resources from LREC2014 took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for First not-normalized set of language resources from LREC2014 took 3.075599670410156e-05s
Believability | Calculation of trust value for First not-normalized set of language resources from LREC2014 took 1.3828277587890625e-05s
INFO | --- Analysis for lremap-ri took 1.9961585998535156s
Availability | SPARQL endpoint availability check for A collection of Submissions for LREC2014 and related Workshops took 3.9577484130859375e-05s
Availability | VoID file availability check for A collection of Submissions for LREC2014 and related Workshops took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for A collection of Submissions for LREC2014 and related Workshops took 0.16860389709472656s
Reputation | Calculation of the PageRank for A collection of Submissions for LREC2014 and related Workshops took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for A collection of Submissions for LREC2014 and related Workshops took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for A collection of Submissions for LREC2014 and related Workshops took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for A collection of Submissions for LREC2014 and related Workshops took 3.528594970703125e-05s
Believability | Calculation of trust value for A collection of Submissions for LREC2014 and related Workshops took 7.152557373046875e-06s
INFO | --- Analysis for lremap-sub took 1.9063279628753662s
Availability | SPARQL endpoint availability check for LSQ took 4.1961669921875e-05s
Availability | VoID file availability check for LSQ took 0.00026988983154296875s
Completeness | Calculation of interlinking completeness for LSQ took 0.17455267906188965s
Reputation | Calculation of the PageRank for LSQ took 0.02026653289794922s
Interlinking | Calculation of Degree of Connection for LSQ took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for LSQ took 0.0009338855743408203s
Interlinking | Calculation of Clustering coefficient for LSQ took 3.886222839355469e-05s
Believability | Calculation of trust value for LSQ took 8.106231689453125e-06s
INFO | --- Analysis for lsq took 1.9063270092010498s
Availability | SPARQL endpoint availability check for Lucani Pharsalia in LiLa took 0.6713924407958984s
Availability | VoID file availability check for Lucani Pharsalia in LiLa took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Lucani Pharsalia in LiLa took 0.17159461975097656s
Reputation | Calculation of the PageRank for Lucani Pharsalia in LiLa took 0.020411014556884766s
Interlinking | Calculation of Degree of Connection for Lucani Pharsalia in LiLa took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Lucani Pharsalia in LiLa took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Lucani Pharsalia in LiLa took 4.076957702636719e-05s
Believability | Calculation of trust value for Lucani Pharsalia in LiLa took 7.3909759521484375e-06s
INFO | --- Analysis for LucaniPharsalia took 2.987640380859375s
Availability | SPARQL endpoint availability check for Linked rules took 4.076957702636719e-05s
Availability | VoID file availability check for Linked rules took 0.0002522468566894531s
Completeness | Calculation of interlinking completeness for Linked rules took 0.17010498046875s
Reputation | Calculation of the PageRank for Linked rules took 0.02050638198852539s
Interlinking | Calculation of Degree of Connection for Linked rules took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Linked rules took 0.000858306884765625s
Interlinking | Calculation of Clustering coefficient for Linked rules took 5.14984130859375e-05s
Believability | Calculation of trust value for Linked rules took 8.344650268554688e-06s
INFO | --- Analysis for Luminaires_senlis took 1.9158129692077637s
Availability | SPARQL endpoint availability check for Měnové kurzy vzhledem k EUR took 4.220008850097656e-05s
Availability | VoID file availability check for Měnové kurzy vzhledem k EUR took 0.00021576881408691406s
Completeness | Calculation of interlinking completeness for Měnové kurzy vzhledem k EUR took 0.1717665195465088s
Reputation | Calculation of the PageRank for Měnové kurzy vzhledem k EUR took 0.02021479606628418s
Interlinking | Calculation of Degree of Connection for Měnové kurzy vzhledem k EUR took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Měnové kurzy vzhledem k EUR took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Měnové kurzy vzhledem k EUR took 2.9802322387695312e-05s
Believability | Calculation of trust value for Měnové kurzy vzhledem k EUR took 8.106231689453125e-06s
INFO | --- Analysis for m-nov--kurzy-vzhledem-k-eur took 1.9164855480194092s
Availability | SPARQL endpoint availability check for Microsoft Academic Knowledge Graph took 4.124641418457031e-05s
Availability | VoID file availability check for Microsoft Academic Knowledge Graph took 0.00027751922607421875s
Completeness | Calculation of interlinking completeness for Microsoft Academic Knowledge Graph took 0.17205142974853516s
Reputation | Calculation of the PageRank for Microsoft Academic Knowledge Graph took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for Microsoft Academic Knowledge Graph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Microsoft Academic Knowledge Graph took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Microsoft Academic Knowledge Graph took 2.9325485229492188e-05s
Believability | Calculation of trust value for Microsoft Academic Knowledge Graph took 8.58306884765625e-06s
INFO | --- Analysis for makg took 1.9440150260925293s
Availability | SPARQL endpoint availability check for Manchester University Reading Lists took 4.00543212890625e-05s
Availability | VoID file availability check for Manchester University Reading Lists took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for Manchester University Reading Lists took 0.17998218536376953s
Reputation | Calculation of the PageRank for Manchester University Reading Lists took 0.02059173583984375s
Interlinking | Calculation of Degree of Connection for Manchester University Reading Lists took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Manchester University Reading Lists took 0.0009737014770507812s
Interlinking | Calculation of Clustering coefficient for Manchester University Reading Lists took 4.1961669921875e-05s
Believability | Calculation of trust value for Manchester University Reading Lists took 8.106231689453125e-06s
INFO | --- Analysis for manchester-university-reading-lists took 1.933260202407837s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 4.315376281738281e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00026416778564453125s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.17402935028076172s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0009701251983642578s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.8623809814453125e-05s
Believability | Calculation of trust value for engineering equipment ontology took 8.58306884765625e-06s
INFO | --- Analysis for manish took 1.9411580562591553s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá, Distrito Capital took 4.00543212890625e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá, Distrito Capital took 0.00026869773864746094s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá, Distrito Capital took 0.22046518325805664s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá, Distrito Capital took 0.02005791664123535s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá, Distrito Capital took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá, Distrito Capital took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá, Distrito Capital took 2.7894973754882812e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá, Distrito Capital took 1.1682510375976562e-05s
INFO | --- Analysis for mapa-referencia-bogota took 2.0208282470703125s
Availability | SPARQL endpoint availability check for Mapa de Referencia para Bogotá D.C took 8.702278137207031e-05s
Availability | VoID file availability check for Mapa de Referencia para Bogotá D.C took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Mapa de Referencia para Bogotá D.C took 0.17920851707458496s
Reputation | Calculation of the PageRank for Mapa de Referencia para Bogotá D.C took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for Mapa de Referencia para Bogotá D.C took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mapa de Referencia para Bogotá D.C took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Mapa de Referencia para Bogotá D.C took 2.7418136596679688e-05s
Believability | Calculation of trust value for Mapa de Referencia para Bogotá D.C took 1.1682510375976562e-05s
INFO | --- Analysis for mapa-referencia-bogota-dc took 1.9846057891845703s
Availability | SPARQL endpoint availability check for MARC Codes List took 4.029273986816406e-05s
Availability | VoID file availability check for MARC Codes List took 0.0002593994140625s
Completeness | Calculation of interlinking completeness for MARC Codes List took 0.18093061447143555s
Reputation | Calculation of the PageRank for MARC Codes List took 0.02010345458984375s
Interlinking | Calculation of Degree of Connection for MARC Codes List took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for MARC Codes List took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for MARC Codes List took 0.00011849403381347656s
Believability | Calculation of trust value for MARC Codes List took 8.344650268554688e-06s
INFO | --- Analysis for marc-codes took 1.9268088340759277s
Availability | SPARQL endpoint availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.435943603515625e-05s
Availability | VoID file availability check for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.20084166526794434s
Reputation | Calculation of the PageRank for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.020176410675048828s
Interlinking | Calculation of Degree of Connection for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 4.363059997558594e-05s
Believability | Calculation of trust value for Manually Annotated Sub-Corpus (MASC) of the Open American National Corpus took 5.9604644775390625e-06s
INFO | --- Analysis for masc took 1.9891738891601562s
Availability | SPARQL endpoint availability check for MASC-BN-NIF took 8.392333984375e-05s
Availability | VoID file availability check for MASC-BN-NIF took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for MASC-BN-NIF took 0.1750800609588623s
Reputation | Calculation of the PageRank for MASC-BN-NIF took 0.02030205726623535s
Interlinking | Calculation of Degree of Connection for MASC-BN-NIF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MASC-BN-NIF took 0.0007841587066650391s
Interlinking | Calculation of Clustering coefficient for MASC-BN-NIF took 3.8623809814453125e-05s
Believability | Calculation of trust value for MASC-BN-NIF took 6.4373016357421875e-06s
INFO | --- Analysis for masc-bn-nif took 1.9587225914001465s
Availability | SPARQL endpoint availability check for Mass Observation Archive catalogue took 1.2750048637390137s
Availability | VoID file availability check for Mass Observation Archive catalogue took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Mass Observation Archive catalogue took 0.18363690376281738s
Reputation | Calculation of the PageRank for Mass Observation Archive catalogue took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Mass Observation Archive catalogue took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Mass Observation Archive catalogue took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Mass Observation Archive catalogue took 3.0040740966796875e-05s
Believability | Calculation of trust value for Mass Observation Archive catalogue took 9.5367431640625e-06s
INFO | --- Analysis for massobservationarchivecatalogue took 3.3276054859161377s
Availability | SPARQL endpoint availability check for medline took 3.910064697265625e-05s
Availability | VoID file availability check for medline took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for medline took 0.17500090599060059s
Reputation | Calculation of the PageRank for medline took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for medline took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for medline took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for medline took 3.1948089599609375e-05s
Believability | Calculation of trust value for medline took 1.0013580322265625e-05s
INFO | --- Analysis for medline took 1.9989166259765625s
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.0004553794860839844s
Completeness | Calculation of interlinking completeness for mEducator: Linked Educational Resources took 0.18294548988342285s
Reputation | Calculation of the PageRank for mEducator: Linked Educational Resources took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for mEducator: Linked Educational Resources took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for mEducator: Linked Educational Resources took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for mEducator: Linked Educational Resources took 6.222724914550781e-05s
Believability | Calculation of trust value for mEducator: Linked Educational Resources took 1.1444091796875e-05s
INFO | --- Analysis for meducator took 1.9980816841125488s
Availability | SPARQL endpoint availability check for Finnish translation of mesh took 8.20159912109375e-05s
Availability | VoID file availability check for Finnish translation of mesh took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Finnish translation of mesh took 0.18383574485778809s
Reputation | Calculation of the PageRank for Finnish translation of mesh took 0.020114421844482422s
Interlinking | Calculation of Degree of Connection for Finnish translation of mesh took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Finnish translation of mesh took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for Finnish translation of mesh took 3.0279159545898438e-05s
Believability | Calculation of trust value for Finnish translation of mesh took 1.239776611328125e-05s
INFO | --- Analysis for mesh-finnish took 1.9932756423950195s
Availability | SPARQL endpoint availability check for MeSH headings took 4.00543212890625e-05s
Availability | VoID file availability check for MeSH headings took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for MeSH headings took 0.1821730136871338s
Reputation | Calculation of the PageRank for MeSH headings took 0.020464658737182617s
Interlinking | Calculation of Degree of Connection for MeSH headings took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MeSH headings took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for MeSH headings took 3.886222839355469e-05s
Believability | Calculation of trust value for MeSH headings took 1.1444091796875e-05s
INFO | --- Analysis for mesh_headings took 1.9728236198425293s
Availability | SPARQL endpoint availability check for MeSH, IPSV - SKOS RDF took 4.124641418457031e-05s
Availability | VoID file availability check for MeSH, IPSV - SKOS RDF took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for MeSH, IPSV - SKOS RDF took 0.16949796676635742s
Reputation | Calculation of the PageRank for MeSH, IPSV - SKOS RDF took 0.02059197425842285s
Interlinking | Calculation of Degree of Connection for MeSH, IPSV - SKOS RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for MeSH, IPSV - SKOS RDF took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for MeSH, IPSV - SKOS RDF took 2.8133392333984375e-05s
Believability | Calculation of trust value for MeSH, IPSV - SKOS RDF took 1.1205673217773438e-05s
INFO | --- Analysis for mesh_ipsv_skos_rdf took 1.992980718612671s
Availability | SPARQL endpoint availability check for MeSH pairs took 8.559226989746094e-05s
Availability | VoID file availability check for MeSH pairs took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for MeSH pairs took 0.18314766883850098s
Reputation | Calculation of the PageRank for MeSH pairs took 0.020229816436767578s
Interlinking | Calculation of Degree of Connection for MeSH pairs took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MeSH pairs took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for MeSH pairs took 2.8133392333984375e-05s
Believability | Calculation of trust value for MeSH pairs took 6.9141387939453125e-06s
INFO | --- Analysis for mesh_pairs took 1.994436502456665s
Availability | SPARQL endpoint availability check for MeSH titles took 4.0531158447265625e-05s
Availability | VoID file availability check for MeSH titles took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for MeSH titles took 0.17692279815673828s
Reputation | Calculation of the PageRank for MeSH titles took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for MeSH titles took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MeSH titles took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for MeSH titles took 2.8133392333984375e-05s
Believability | Calculation of trust value for MeSH titles took 1.1920928955078125e-05s
INFO | --- Analysis for mesh_titles took 2.0098934173583984s
Availability | SPARQL endpoint availability check for Metadata k zákonům z psp.cz took 8.416175842285156e-05s
Availability | VoID file availability check for Metadata k zákonům z psp.cz took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Metadata k zákonům z psp.cz took 0.18925976753234863s
Reputation | Calculation of the PageRank for Metadata k zákonům z psp.cz took 0.02035975456237793s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům z psp.cz took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům z psp.cz took 0.0006918907165527344s
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 1.2636184692382812e-05s
INFO | --- Analysis for metadata-k-z-kon-m-z-psp-cz took 1.9905145168304443s
Availability | SPARQL endpoint availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.797645568847656e-05s
Availability | VoID file availability check for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0005412101745605469s
Completeness | Calculation of interlinking completeness for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.17972087860107422s
Reputation | Calculation of the PageRank for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.022300243377685547s
Interlinking | Calculation of Degree of Connection for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 2.956390380859375e-05s
Believability | Calculation of trust value for Metadata k zákonům ze zakonyprolidi.cz - dvě ukázková znění took 1.1205673217773438e-05s
INFO | --- Analysis for metadata-k-z-kon-m-ze-zakonyprolidi-cz---dv--uk-zkov--zn-n- took 2.005110502243042s
Availability | SPARQL endpoint availability check for MetaShare metadata model took 8.392333984375e-05s
Availability | VoID file availability check for MetaShare metadata model took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for MetaShare metadata model took 0.18832635879516602s
Reputation | Calculation of the PageRank for MetaShare metadata model took 0.020263195037841797s
Interlinking | Calculation of Degree of Connection for MetaShare metadata model took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for MetaShare metadata model took 0.0006921291351318359s
Interlinking | Calculation of Clustering coefficient for MetaShare metadata model took 6.699562072753906e-05s
Believability | Calculation of trust value for MetaShare metadata model took 1.1205673217773438e-05s
INFO | --- Analysis for metashare took 2.0070607662200928s
Availability | SPARQL endpoint availability check for MExiCo took 8.58306884765625e-05s
Availability | VoID file availability check for MExiCo took 0.0005176067352294922s
Completeness | Calculation of interlinking completeness for MExiCo took 0.18188834190368652s
Reputation | Calculation of the PageRank for MExiCo took 0.02233147621154785s
Interlinking | Calculation of Degree of Connection for MExiCo took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for MExiCo took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for MExiCo took 5.0067901611328125e-05s
Believability | Calculation of trust value for MExiCo took 1.3589859008789062e-05s
INFO | --- Analysis for mexico took 1.9859819412231445s
Availability | SPARQL endpoint availability check for Coronavirus dataset took 3.910064697265625e-05s
Availability | VoID file availability check for Coronavirus dataset took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Coronavirus dataset took 0.1820509433746338s
Reputation | Calculation of the PageRank for Coronavirus dataset took 0.02100086212158203s
Interlinking | Calculation of Degree of Connection for Coronavirus dataset took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Coronavirus dataset took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Coronavirus dataset took 4.744529724121094e-05s
Believability | Calculation of trust value for Coronavirus dataset took 1.1205673217773438e-05s
INFO | --- Analysis for micro-coronavirus took 1.9837963581085205s
Availability | SPARQL endpoint availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.535385131835938e-05s
Availability | VoID file availability check for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0005171298980712891s
Completeness | Calculation of interlinking completeness for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.1749711036682129s
Reputation | Calculation of the PageRank for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.022340059280395508s
Interlinking | Calculation of Degree of Connection for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 9.870529174804688e-05s
Believability | Calculation of trust value for Mi Guía de Viajes, colección de guías de viaje para viajeros (GNOSS) took 1.2159347534179688e-05s
INFO | --- Analysis for miguiadeviajes-gnoss took 2.0066208839416504s
Availability | SPARQL endpoint availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00010204315185546875s
Availability | VoID file availability check for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.0005064010620117188s
Completeness | Calculation of interlinking completeness for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.18204307556152344s
Reputation | Calculation of the PageRank for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.02107548713684082s
Interlinking | Calculation of Degree of Connection for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 0.00011324882507324219s
Believability | Calculation of trust value for Mis Museos, índice semántico de museos, artistas y obras de arte (GNOSS) took 1.1920928955078125e-05s
INFO | --- Analysis for mismuseos-gnoss took 1.9935657978057861s
Availability | SPARQL endpoint availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 8.320808410644531e-05s
Availability | VoID file availability check for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.0005283355712890625s
Completeness | Calculation of interlinking completeness for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.17422032356262207s
Reputation | Calculation of the PageRank for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 0.020364999771118164s
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.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 4.315376281738281e-05s
Believability | Calculation of trust value for MLSA - A Multi-layered Reference Corpus for German Sentiment Analysis took 1.1682510375976562e-05s
INFO | --- Analysis for mlsa took 1.98268461227417s
Availability | SPARQL endpoint availability check for Atmospheric Correction of High Resolution Optical Images model took 8.869171142578125e-05s
Availability | VoID file availability check for Atmospheric Correction of High Resolution Optical Images model took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Atmospheric Correction of High Resolution Optical Images model took 0.18068909645080566s
Reputation | Calculation of the PageRank for Atmospheric Correction of High Resolution Optical Images model took 0.02156805992126465s
Interlinking | Calculation of Degree of Connection for Atmospheric Correction of High Resolution Optical Images model took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Atmospheric Correction of High Resolution Optical Images model took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Atmospheric Correction of High Resolution Optical Images model took 2.7894973754882812e-05s
Believability | Calculation of trust value for Atmospheric Correction of High Resolution Optical Images model took 1.0967254638671875e-05s
INFO | --- Analysis for model took 1.9800152778625488s
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 8.416175842285156e-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.00021600723266601562s
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.17741703987121582s
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.020113468170166016s
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 8.821487426757812e-06s
Interlinking | Calculation of Centrality for An automatic approach for land-change detection and land updates based on integrated NDVI timing analysis and the CVAPS method with GEE support took 0.0007078647613525391s
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.8133392333984375e-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 5.9604644775390625e-06s
INFO | --- Analysis for model1 took 1.9743382930755615s
Availability | SPARQL endpoint availability check for The MOND modular ontology for NIF data took 9.846687316894531e-05s
Availability | VoID file availability check for The MOND modular ontology for NIF data took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for The MOND modular ontology for NIF data took 0.17507386207580566s
Reputation | Calculation of the PageRank for The MOND modular ontology for NIF data took 0.022655725479125977s
Interlinking | Calculation of Degree of Connection for The MOND modular ontology for NIF data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for The MOND modular ontology for NIF data took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for The MOND modular ontology for NIF data took 3.170967102050781e-05s
Believability | Calculation of trust value for The MOND modular ontology for NIF data took 1.3113021850585938e-05s
INFO | --- Analysis for mond took 2.0074245929718018s
Availability | SPARQL endpoint availability check for MONDIS took 0.00010704994201660156s
Availability | VoID file availability check for MONDIS took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for MONDIS took 0.17964982986450195s
Reputation | Calculation of the PageRank for MONDIS took 0.020159482955932617s
Interlinking | Calculation of Degree of Connection for MONDIS took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for MONDIS took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for MONDIS took 2.9802322387695312e-05s
Believability | Calculation of trust value for MONDIS took 6.67572021484375e-06s
INFO | --- Analysis for mondis took 2.005910634994507s
Availability | SPARQL endpoint availability check for Monumentos took 8.368492126464844e-05s
Availability | VoID file availability check for Monumentos took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Monumentos took 0.17352604866027832s
Reputation | Calculation of the PageRank for Monumentos took 0.020635604858398438s
Interlinking | Calculation of Degree of Connection for Monumentos took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Monumentos took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Monumentos took 2.7894973754882812e-05s
Believability | Calculation of trust value for Monumentos took 1.2159347534179688e-05s
INFO | --- Analysis for monumentos-zaragoza took 1.9711689949035645s
Availability | SPARQL endpoint availability check for MORElab took 8.273124694824219e-05s
Availability | VoID file availability check for MORElab took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for MORElab took 0.17893385887145996s
Reputation | Calculation of the PageRank for MORElab took 0.020098447799682617s
Interlinking | Calculation of Degree of Connection for MORElab took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for MORElab took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for MORElab took 8.153915405273438e-05s
Believability | Calculation of trust value for MORElab took 1.2159347534179688e-05s
INFO | --- Analysis for morelab took 1.9794714450836182s
Availability | SPARQL endpoint availability check for Mathematics Subject Classification took 8.440017700195312e-05s
Availability | VoID file availability check for Mathematics Subject Classification took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for Mathematics Subject Classification took 0.1781933307647705s
Reputation | Calculation of the PageRank for Mathematics Subject Classification took 0.02240729331970215s
Interlinking | Calculation of Degree of Connection for Mathematics Subject Classification took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Mathematics Subject Classification took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Mathematics Subject Classification took 8.130073547363281e-05s
Believability | Calculation of trust value for Mathematics Subject Classification took 1.1682510375976562e-05s
INFO | --- Analysis for msc took 1.9963674545288086s
Availability | SPARQL endpoint availability check for Multext-East took 8.344650268554688e-05s
Availability | VoID file availability check for Multext-East took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Multext-East took 0.17264556884765625s
Reputation | Calculation of the PageRank for Multext-East took 0.022808074951171875s
Interlinking | Calculation of Degree of Connection for Multext-East took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Multext-East took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Multext-East took 3.218650817871094e-05s
Believability | Calculation of trust value for Multext-East took 1.1444091796875e-05s
INFO | --- Analysis for multext-east took 2.127145767211914s
Availability | SPARQL endpoint availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 5.5789947509765625e-05s
Availability | VoID file availability check for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.18206214904785156s
Reputation | Calculation of the PageRank for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for The DGT Multilingual Translation Memory of the Acquis Communautaire took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for The DGT Multilingual Translation Memory of the Acquis Communautaire took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for The DGT Multilingual Translation Memory of the Acquis Communautaire took 2.765655517578125e-05s
Believability | Calculation of trust value for The DGT Multilingual Translation Memory of the Acquis Communautaire took 1.1444091796875e-05s
INFO | --- Analysis for multilingualeulaw took 2.0113320350646973s
Availability | SPARQL endpoint availability check for Multimedia Lab took 4.0531158447265625e-05s
Availability | VoID file availability check for Multimedia Lab took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Multimedia Lab took 0.18013763427734375s
Reputation | Calculation of the PageRank for Multimedia Lab took 0.020194530487060547s
Interlinking | Calculation of Degree of Connection for Multimedia Lab took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Multimedia Lab took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Multimedia Lab took 3.0517578125e-05s
Believability | Calculation of trust value for Multimedia Lab took 1.1444091796875e-05s
INFO | --- Analysis for multimedia-lab took 1.985457420349121s
Availability | SPARQL endpoint availability check for Munich Offener Haushalt took 8.440017700195312e-05s
Availability | VoID file availability check for Munich Offener Haushalt took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Munich Offener Haushalt took 0.17352509498596191s
Reputation | Calculation of the PageRank for Munich Offener Haushalt took 0.020597457885742188s
Interlinking | Calculation of Degree of Connection for Munich Offener Haushalt took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Munich Offener Haushalt took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Munich Offener Haushalt took 2.765655517578125e-05s
Believability | Calculation of trust value for Munich Offener Haushalt took 1.1682510375976562e-05s
INFO | --- Analysis for munich-offener-haushalt took 1.9683375358581543s
Availability | SPARQL endpoint availability check for Muninn World War I took 1.7976710796356201s
Availability | VoID file availability check for Muninn World War I took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for Muninn World War I took 0.18265700340270996s
Reputation | Calculation of the PageRank for Muninn World War I took 0.02062249183654785s
Interlinking | Calculation of Degree of Connection for Muninn World War I took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Muninn World War I took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Muninn World War I took 7.724761962890625e-05s
Believability | Calculation of trust value for Muninn World War I took 1.0967254638671875e-05s
INFO | --- Analysis for muninn-world-war-i took 5.678906679153442s
Availability | SPARQL endpoint availability check for Musei Italiani took 8.678436279296875e-05s
Availability | VoID file availability check for Musei Italiani took 0.0005052089691162109s
Completeness | Calculation of interlinking completeness for Musei Italiani took 0.18017911911010742s
Reputation | Calculation of the PageRank for Musei Italiani took 0.020573139190673828s
Interlinking | Calculation of Degree of Connection for Musei Italiani took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Musei Italiani took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Musei Italiani took 2.86102294921875e-05s
Believability | Calculation of trust value for Musei Italiani took 1.621246337890625e-05s
INFO | --- Analysis for musei-italiani took 1.9908053874969482s
Availability | SPARQL endpoint availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.96453857421875e-05s
Availability | VoID file availability check for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00025391578674316406s
Completeness | Calculation of interlinking completeness for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.18581843376159668s
Reputation | Calculation of the PageRank for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.020260334014892578s
Interlinking | Calculation of Degree of Connection for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 0.00010013580322265625s
Believability | Calculation of trust value for Museos de España, colección de museos públicos y privados españoles (GNOSS) took 1.6450881958007812e-05s
INFO | --- Analysis for museosespania-gnoss took 1.9842729568481445s
Availability | SPARQL endpoint availability check for Italian Museums took 0.449904203414917s
Availability | VoID file availability check for Italian Museums took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for Italian Museums took 0.1775226593017578s
Reputation | Calculation of the PageRank for Italian Museums took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for Italian Museums took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Italian Museums took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Italian Museums took 7.653236389160156e-05s
Believability | Calculation of trust value for Italian Museums took 1.2159347534179688e-05s
INFO | --- Analysis for museums-in-italy took 2.408261775970459s
Availability | SPARQL endpoint availability check for MusicBrainz took 4.2438507080078125e-05s
Availability | VoID file availability check for MusicBrainz took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for MusicBrainz took 0.18260931968688965s
Reputation | Calculation of the PageRank for MusicBrainz took 0.023146629333496094s
Interlinking | Calculation of Degree of Connection for MusicBrainz took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for MusicBrainz took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for MusicBrainz took 3.0040740966796875e-05s
Believability | Calculation of trust value for MusicBrainz took 1.3113021850585938e-05s
INFO | --- Analysis for musicbrainz_ took 1.9865832328796387s
Availability | SPARQL endpoint availability check for MusicNet Codex took 8.368492126464844e-05s
Availability | VoID file availability check for MusicNet Codex took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for MusicNet Codex took 0.17531681060791016s
Reputation | Calculation of the PageRank for MusicNet Codex took 0.0202789306640625s
Interlinking | Calculation of Degree of Connection for MusicNet Codex took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for MusicNet Codex took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for MusicNet Codex took 2.765655517578125e-05s
Believability | Calculation of trust value for MusicNet Codex took 1.239776611328125e-05s
INFO | --- Analysis for musicnet_codex took 1.9875457286834717s
Availability | SPARQL endpoint availability check for Muziekweb took 0.7301540374755859s
Availability | VoID file availability check for Muziekweb took 0.0004775524139404297s
Extra | Recovery of all triples for Muziekweb took 1.6387083530426025s
Performance | Total latancy measurement for Muziekweb took 1.6526715755462646s
Amount of data | Number of triples check for Muziekweb took 0.4033629894256592s
Interoperability | New terms check for Muziekweb took 1.7721173763275146s
Versatility | Languages check for Muziekweb took 55.14350605010986s
Interpretability | Number of blank nodes check for Muziekweb took 0.3455696105957031s
Interpretability | RDF structures check for Muziekweb took 0.3428518772125244s
Versatility | Serialization formats check for Muziekweb took 0.32553601264953613s
Availability | RDF dump link check for Muziekweb took 0.3318450450897217s
License | MR license check for Muziekweb took 0.36243557929992676s
License | HR license check for Muziekweb took 11.291694164276123s
Amount of data | Number of property check for Muziekweb took 0.3092474937438965s
Understandability | Number of label check for Muziekweb took 0.3596501350402832s
Understandability | URI regex check for Muziekweb took 0.6668767929077148s
Understandability | Vocabs check for Muziekweb took 0.32900357246398926s
Verifiability | Authors check for Muziekweb took 0.3333775997161865s
Verifiability | Publishers check for Muziekweb took 0.3316197395324707s
Performance | Throughput check for Muziekweb took 12.596804141998291s
Amount of data | Check the number of entities for Muziekweb took 7.343292236328125e-05s
Verifiability | Contribs. check for Muziekweb took 0.33283567428588867s
Interlinking | sameAs chians check for Muziekweb took 0.3416407108306885s
Interlinking | skos check for Muziekweb took 0.34290170669555664s
Interlinking | skos check for Muziekweb took 0.3291952610015869s
Timeliness | dataset update frequency check for Muziekweb took 0.3304460048675537s
Currency | Creation date check for Muziekweb took 0.9050490856170654s
Currency | Modification date check for Muziekweb took 0.935307502746582s
Rep.Conc. | URIs length for Muziekweb took 1.948880672454834s
Interoperability | New vocabularies check for Muziekweb took 2.6226043701171875e-06s
Consistency | Deprecated classes/propertiers check for Muziekweb took 0.35114240646362305s
Accuracy | Check Functional Property for Muziekweb took 0.558316707611084s
Accuracy | Check Inverse Functional Property for Muziekweb took 0.5905742645263672s
Accuracy | Check Empty annotation labels for Muziekweb took 0.9958980083465576s
Accuracy | Check White space in annotation for Muziekweb took 0.027425289154052734s
Accuracy | Check Datatype consistency for Muziekweb took 0.028472185134887695s
Consistency | Disjoint class check for Muziekweb took 0.5441062450408936s
Consistency | Check Misplaced properties for Muziekweb took 1.213670253753662s
Consistency | Check Ontology hijacking for Muziekweb took 2.1479012966156006s
Consistency | Check Invalid usage of undefined classes for Muziekweb took 1.2883260250091553s
Consistency | Check Invalid usage of undefined properties for Muziekweb took 1.6087260246276855s
Conciseness | Check Extensional conciseness for Muziekweb took 0.031542301177978516s
Conciseness | Check Intensional conciseness for Muziekweb took 0.32215237617492676s
Security | Sign check for Muziekweb took 0.3384847640991211s
Availability | Check URIs Dereferenciability for Muziekweb took 2162.017380952835s
Completeness | Calculation of interlinking completeness for Muziekweb took 0.2975168228149414s
Reputation | Calculation of the PageRank for Muziekweb took 0.021897315979003906s
Interlinking | Calculation of Degree of Connection for Muziekweb took 0.00032067298889160156s
Interlinking | Calculation of Centrality for Muziekweb took 0.0007510185241699219s
Interlinking | Calculation of Clustering coefficient for Muziekweb took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Muziekweb took 1.430511474609375e-06s
Believability | Calculation of trust value for Muziekweb took 1.049041748046875e-05s
INFO | --- Analysis for muziekweb took 2288.9008297920227s
Availability | SPARQL endpoint availability check for myExperiment took 8.511543273925781e-05s
Availability | VoID file availability check for myExperiment took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for myExperiment took 0.17510175704956055s
Reputation | Calculation of the PageRank for myExperiment took 0.020565032958984375s
Interlinking | Calculation of Degree of Connection for myExperiment took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for myExperiment took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for myExperiment took 9.369850158691406e-05s
Believability | Calculation of trust value for myExperiment took 1.1920928955078125e-05s
INFO | --- Analysis for my-experiment took 2.007330894470215s
Availability | SPARQL endpoint availability check for My Family Lineage took 8.606910705566406e-05s
Availability | VoID file availability check for My Family Lineage took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for My Family Lineage took 0.1870882511138916s
Reputation | Calculation of the PageRank for My Family Lineage took 0.020029783248901367s
Interlinking | Calculation of Degree of Connection for My Family Lineage took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for My Family Lineage took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for My Family Lineage took 8.058547973632812e-05s
Believability | Calculation of trust value for My Family Lineage took 1.1682510375976562e-05s
INFO | --- Analysis for my-family-lineage took 2.022233724594116s
Availability | SPARQL endpoint availability check for My ontology test took 3.9577484130859375e-05s
Availability | VoID file availability check for My ontology test took 0.0005137920379638672s
Completeness | Calculation of interlinking completeness for My ontology test took 0.1840348243713379s
Reputation | Calculation of the PageRank for My ontology test took 0.02241039276123047s
Interlinking | Calculation of Degree of Connection for My ontology test took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for My ontology test took 0.0009949207305908203s
Interlinking | Calculation of Clustering coefficient for My ontology test took 3.4332275390625e-05s
Believability | Calculation of trust value for My ontology test took 1.2159347534179688e-05s
INFO | --- Analysis for myontologytest took 2.0032389163970947s
Availability | SPARQL endpoint availability check for myopenlink dataspaces took 3.933906555175781e-05s
Availability | VoID file availability check for myopenlink dataspaces took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for myopenlink dataspaces took 0.17656803131103516s
Reputation | Calculation of the PageRank for myopenlink dataspaces took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for myopenlink dataspaces took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for myopenlink dataspaces took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for myopenlink dataspaces took 9.560585021972656e-05s
Believability | Calculation of trust value for myopenlink dataspaces took 6.67572021484375e-06s
INFO | --- Analysis for myopenlink-dataspaces took 1.9377720355987549s
Availability | SPARQL endpoint availability check for N-Lex as Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for N-Lex as Linked Data took 0.00024247169494628906s
Completeness | Calculation of interlinking completeness for N-Lex as Linked Data took 0.18261384963989258s
Reputation | Calculation of the PageRank for N-Lex as Linked Data took 0.02049088478088379s
Interlinking | Calculation of Degree of Connection for N-Lex as Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for N-Lex as Linked Data took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for N-Lex as Linked Data took 6.4849853515625e-05s
Believability | Calculation of trust value for N-Lex as Linked Data took 6.67572021484375e-06s
INFO | --- Analysis for n-lex-as-linked-data took 1.994187831878662s
Availability | SPARQL endpoint availability check for NAICS 2007 took 0.00010061264038085938s
Availability | VoID file availability check for NAICS 2007 took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for NAICS 2007 took 0.1823258399963379s
Reputation | Calculation of the PageRank for NAICS 2007 took 0.022246599197387695s
Interlinking | Calculation of Degree of Connection for NAICS 2007 took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for NAICS 2007 took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for NAICS 2007 took 3.790855407714844e-05s
Believability | Calculation of trust value for NAICS 2007 took 1.33514404296875e-05s
INFO | --- Analysis for naics-2007 took 2.0054829120635986s
Availability | SPARQL endpoint availability check for NAICS 2012 took 4.1484832763671875e-05s
Availability | VoID file availability check for NAICS 2012 took 0.0005254745483398438s
Completeness | Calculation of interlinking completeness for NAICS 2012 took 0.18868207931518555s
Reputation | Calculation of the PageRank for NAICS 2012 took 0.021782398223876953s
Interlinking | Calculation of Degree of Connection for NAICS 2012 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NAICS 2012 took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for NAICS 2012 took 4.57763671875e-05s
Believability | Calculation of trust value for NAICS 2012 took 1.1920928955078125e-05s
INFO | --- Analysis for naics-2012 took 2.0382883548736572s
Availability | SPARQL endpoint availability check for National Agricultural Library Thesaurus took 4.1484832763671875e-05s
Availability | VoID file availability check for National Agricultural Library Thesaurus took 0.00027251243591308594s
Completeness | Calculation of interlinking completeness for National Agricultural Library Thesaurus took 0.18459463119506836s
Reputation | Calculation of the PageRank for National Agricultural Library Thesaurus took 0.02077651023864746s
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.0008378028869628906s
Interlinking | Calculation of Clustering coefficient for National Agricultural Library Thesaurus took 5.602836608886719e-05s
Believability | Calculation of trust value for National Agricultural Library Thesaurus took 7.867813110351562e-06s
INFO | --- Analysis for nalt took 1.959381103515625s
Availability | SPARQL endpoint availability check for Usernames  took 4.100799560546875e-05s
Availability | VoID file availability check for Usernames  took 0.00023651123046875s
Completeness | Calculation of interlinking completeness for Usernames  took 0.17835760116577148s
Reputation | Calculation of the PageRank for Usernames  took 0.020134449005126953s
Interlinking | Calculation of Degree of Connection for Usernames  took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Usernames  took 0.0007228851318359375s
Interlinking | Calculation of Clustering coefficient for Usernames  took 3.695487976074219e-05s
Believability | Calculation of trust value for Usernames  took 8.344650268554688e-06s
INFO | --- Analysis for Names took 1.9759516716003418s
Availability | SPARQL endpoint availability check for Web NDL Authorities - National Diet Library of Japan took 5.1975250244140625e-05s
Availability | VoID file availability check for Web NDL Authorities - National Diet Library of Japan took 0.00027060508728027344s
Completeness | Calculation of interlinking completeness for Web NDL Authorities - National Diet Library of Japan took 0.17485713958740234s
Reputation | Calculation of the PageRank for Web NDL Authorities - National Diet Library of Japan took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for Web NDL Authorities - National Diet Library of Japan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Web NDL Authorities - National Diet Library of Japan took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Web NDL Authorities - National Diet Library of Japan took 5.3882598876953125e-05s
Believability | Calculation of trust value for Web NDL Authorities - National Diet Library of Japan took 1.2636184692382812e-05s
INFO | --- Analysis for national-diet-library-authorities took 1.9501702785491943s
Availability | SPARQL endpoint availability check for National Diet Library of Japan subject headings took 4.100799560546875e-05s
Availability | VoID file availability check for National Diet Library of Japan subject headings took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for National Diet Library of Japan subject headings took 0.1887495517730713s
Reputation | Calculation of the PageRank for National Diet Library of Japan subject headings took 0.020138978958129883s
Interlinking | Calculation of Degree of Connection for National Diet Library of Japan subject headings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for National Diet Library of Japan subject headings took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for National Diet Library of Japan subject headings took 4.9591064453125e-05s
Believability | Calculation of trust value for National Diet Library of Japan subject headings took 7.3909759521484375e-06s
INFO | --- Analysis for national-diet-library-subject-headings took 1.9556479454040527s
Availability | SPARQL endpoint availability check for National Library of Greece Authority Records took 1.2209300994873047s
Availability | VoID file availability check for National Library of Greece Authority Records took 0.00024437904357910156s
Completeness | Calculation of interlinking completeness for National Library of Greece Authority Records took 0.17180466651916504s
Reputation | Calculation of the PageRank for National Library of Greece Authority Records took 0.02156662940979004s
Interlinking | Calculation of Degree of Connection for National Library of Greece Authority Records took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for National Library of Greece Authority Records took 0.0007867813110351562s
Interlinking | Calculation of Clustering coefficient for National Library of Greece Authority Records took 4.6253204345703125e-05s
Believability | Calculation of trust value for National Library of Greece Authority Records took 6.67572021484375e-06s
INFO | --- Analysis for national-library-of-greece-authority-records took 4.102470397949219s
Availability | SPARQL endpoint availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 8.106231689453125e-05s
Availability | VoID file availability check for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0005266666412353516s
Completeness | Calculation of interlinking completeness for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.17697358131408691s
Reputation | Calculation of the PageRank for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.020850181579589844s
Interlinking | Calculation of Degree of Connection for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for Naturopathy Knowledge Graph (Ontology and Dataset) - RDF distribution of the naturopathy dataset. took 6.365776062011719e-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 Naturopathy took 1.9983656406402588s
Availability | SPARQL endpoint availability check for Naturopathy took 4.0531158447265625e-05s
Availability | VoID file availability check for Naturopathy took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Naturopathy took 0.2083733081817627s
Reputation | Calculation of the PageRank for Naturopathy took 0.0201261043548584s
Interlinking | Calculation of Degree of Connection for Naturopathy took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Naturopathy took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Naturopathy took 2.765655517578125e-05s
Believability | Calculation of trust value for Naturopathy took 1.3113021850585938e-05s
INFO | --- Analysis for naturopathy2 took 2.047208070755005s
Availability | SPARQL endpoint availability check for NCI Thesaurus took 8.392333984375e-05s
Availability | VoID file availability check for NCI Thesaurus took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for NCI Thesaurus took 0.1740097999572754s
Reputation | Calculation of the PageRank for NCI Thesaurus took 0.020656824111938477s
Interlinking | Calculation of Degree of Connection for NCI Thesaurus took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for NCI Thesaurus took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for NCI Thesaurus took 3.0517578125e-05s
Believability | Calculation of trust value for NCI Thesaurus took 1.3589859008789062e-05s
INFO | --- Analysis for nci-thesaurus took 2.0465750694274902s
Availability | SPARQL endpoint availability check for COVID-19 Data took 4.315376281738281e-05s
Availability | VoID file availability check for COVID-19 Data took 0.0005955696105957031s
Completeness | Calculation of interlinking completeness for COVID-19 Data took 0.19017934799194336s
Reputation | Calculation of the PageRank for COVID-19 Data took 0.020546913146972656s
Interlinking | Calculation of Degree of Connection for COVID-19 Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for COVID-19 Data took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for COVID-19 Data took 3.147125244140625e-05s
Believability | Calculation of trust value for COVID-19 Data took 7.62939453125e-06s
INFO | --- Analysis for NCMI-COVID-19 took 2.030921220779419s
Availability | SPARQL endpoint availability check for NCMI-COVID-19 took 4.2438507080078125e-05s
Availability | VoID file availability check for NCMI-COVID-19 took 0.0009369850158691406s
Completeness | Calculation of interlinking completeness for NCMI-COVID-19 took 0.18678641319274902s
Reputation | Calculation of the PageRank for NCMI-COVID-19 took 0.02205204963684082s
Interlinking | Calculation of Degree of Connection for NCMI-COVID-19 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for NCMI-COVID-19 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for NCMI-COVID-19 took 1.3589859008789062e-05s
Believability | Calculation of trust value for NCMI-COVID-19 took 1.3828277587890625e-05s
INFO | --- Analysis for NCMICOVID-19 took 2.0019850730895996s
Availability | SPARQL endpoint availability check for NDF-RT took 4.076957702636719e-05s
Availability | VoID file availability check for NDF-RT took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for NDF-RT took 0.17546892166137695s
Reputation | Calculation of the PageRank for NDF-RT took 0.02056264877319336s
Interlinking | Calculation of Degree of Connection for NDF-RT took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NDF-RT took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for NDF-RT took 3.123283386230469e-05s
Believability | Calculation of trust value for NDF-RT took 1.3113021850585938e-05s
INFO | --- Analysis for ndf-rt took 1.9710421562194824s
Availability | SPARQL endpoint availability check for Near took 6.413459777832031e-05s
Availability | VoID file availability check for Near took 0.0005307197570800781s
Completeness | Calculation of interlinking completeness for Near took 0.1857469081878662s
Reputation | Calculation of the PageRank for Near took 0.022278308868408203s
Interlinking | Calculation of Degree of Connection for Near took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Near took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Near took 9.107589721679688e-05s
Believability | Calculation of trust value for Near took 1.3828277587890625e-05s
INFO | --- Analysis for near took 1.9978346824645996s
Availability | SPARQL endpoint availability check for Neel took 8.678436279296875e-05s
Availability | VoID file availability check for Neel took 0.0005664825439453125s
Completeness | Calculation of interlinking completeness for Neel took 0.17701959609985352s
Reputation | Calculation of the PageRank for Neel took 0.020389318466186523s
Interlinking | Calculation of Degree of Connection for Neel took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neel took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Neel took 2.9325485229492188e-05s
Believability | Calculation of trust value for Neel took 1.4066696166992188e-05s
INFO | --- Analysis for neel took 2.0244245529174805s
Availability | SPARQL endpoint availability check for Neurocommons text mining pilot took 8.177757263183594e-05s
Availability | VoID file availability check for Neurocommons text mining pilot took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for Neurocommons text mining pilot took 0.23038387298583984s
Reputation | Calculation of the PageRank for Neurocommons text mining pilot took 0.020459890365600586s
Interlinking | Calculation of Degree of Connection for Neurocommons text mining pilot took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Neurocommons text mining pilot took 0.0007739067077636719s
Interlinking | Calculation of Clustering coefficient for Neurocommons text mining pilot took 3.123283386230469e-05s
Believability | Calculation of trust value for Neurocommons text mining pilot took 8.344650268554688e-06s
INFO | --- Analysis for neurocommons_text_mining_pilot took 2.082867383956909s
Availability | SPARQL endpoint availability check for NeuroLex Wiki took 4.2438507080078125e-05s
Availability | VoID file availability check for NeuroLex Wiki took 0.0010957717895507812s
Completeness | Calculation of interlinking completeness for NeuroLex Wiki took 0.18554162979125977s
Reputation | Calculation of the PageRank for NeuroLex Wiki took 0.020563125610351562s
Interlinking | Calculation of Degree of Connection for NeuroLex Wiki took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for NeuroLex Wiki took 0.0007236003875732422s
Interlinking | Calculation of Clustering coefficient for NeuroLex Wiki took 3.0279159545898438e-05s
Believability | Calculation of trust value for NeuroLex Wiki took 1.2159347534179688e-05s
INFO | --- Analysis for neurolex-wiki took 2.009221315383911s
Availability | SPARQL endpoint availability check for Shivani Goyal Photography took 4.00543212890625e-05s
Availability | VoID file availability check for Shivani Goyal Photography took 0.000476837158203125s
Completeness | Calculation of interlinking completeness for Shivani Goyal Photography took 0.1782829761505127s
Reputation | Calculation of the PageRank for Shivani Goyal Photography took 0.020154237747192383s
Interlinking | Calculation of Degree of Connection for Shivani Goyal Photography took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Shivani Goyal Photography took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Shivani Goyal Photography took 4.2438507080078125e-05s
Believability | Calculation of trust value for Shivani Goyal Photography took 1.2159347534179688e-05s
INFO | --- Analysis for newborn-photography-maternity-photoshoot-shivani-goyal took 2.0054609775543213s
Availability | SPARQL endpoint availability check for News-100 NIF NER Corpus took 8.320808410644531e-05s
Availability | VoID file availability check for News-100 NIF NER Corpus took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for News-100 NIF NER Corpus took 0.1818854808807373s
Reputation | Calculation of the PageRank for News-100 NIF NER Corpus took 0.022073984146118164s
Interlinking | Calculation of Degree of Connection for News-100 NIF NER Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for News-100 NIF NER Corpus took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for News-100 NIF NER Corpus took 6.842613220214844e-05s
Believability | Calculation of trust value for News-100 NIF NER Corpus took 1.239776611328125e-05s
INFO | --- Analysis for news-100-nif-ner-corpus took 1.988438367843628s
Availability | SPARQL endpoint availability check for Newsweek took 4.2438507080078125e-05s
Availability | VoID file availability check for Newsweek took 0.0003027915954589844s
Completeness | Calculation of interlinking completeness for Newsweek took 0.1799933910369873s
Reputation | Calculation of the PageRank for Newsweek took 0.020199060440063477s
Interlinking | Calculation of Degree of Connection for Newsweek took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Newsweek took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Newsweek took 2.86102294921875e-05s
Believability | Calculation of trust value for Newsweek took 7.867813110351562e-06s
INFO | --- Analysis for newsweek took 1.9955573081970215s
Availability | SPARQL endpoint availability check for neXtProt took 4.076957702636719e-05s
Availability | VoID file availability check for neXtProt took 0.0002598762512207031s
Completeness | Calculation of interlinking completeness for neXtProt took 0.17497992515563965s
Reputation | Calculation of the PageRank for neXtProt took 0.020147323608398438s
Interlinking | Calculation of Degree of Connection for neXtProt took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for neXtProt took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for neXtProt took 3.5762786865234375e-05s
Believability | Calculation of trust value for neXtProt took 7.3909759521484375e-06s
INFO | --- Analysis for nextprot took 1.931474208831787s
Availability | SPARQL endpoint availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 4.00543212890625e-05s
Availability | VoID file availability check for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.17686247825622559s
Reputation | Calculation of the PageRank for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.021758556365966797s
Interlinking | Calculation of Degree of Connection for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.0008149147033691406s
Interlinking | Calculation of Clustering coefficient for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 0.00010561943054199219s
Believability | Calculation of trust value for Next Web, a global knowledge network of semantic technology and Web 3.0 (GNOSS) took 1.1205673217773438e-05s
INFO | --- Analysis for nextweb-gnoss took 2.0165886878967285s
Availability | SPARQL endpoint availability check for NHS Jargon RDF took 8.273124694824219e-05s
Availability | VoID file availability check for NHS Jargon RDF took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for NHS Jargon RDF took 0.18115615844726562s
Reputation | Calculation of the PageRank for NHS Jargon RDF took 0.02060723304748535s
Interlinking | Calculation of Degree of Connection for NHS Jargon RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NHS Jargon RDF took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for NHS Jargon RDF took 7.772445678710938e-05s
Believability | Calculation of trust value for NHS Jargon RDF took 1.33514404296875e-05s
INFO | --- Analysis for nhs-jargon took 2.022498846054077s
Availability | SPARQL endpoint availability check for NIT Patna took 3.981590270996094e-05s
Availability | VoID file availability check for NIT Patna took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for NIT Patna took 0.17281746864318848s
Reputation | Calculation of the PageRank for NIT Patna took 0.020451068878173828s
Interlinking | Calculation of Degree of Connection for NIT Patna took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NIT Patna took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for NIT Patna took 6.628036499023438e-05s
Believability | Calculation of trust value for NIT Patna took 7.3909759521484375e-06s
INFO | --- Analysis for NITP took 2.0328805446624756s
Availability | SPARQL endpoint availability check for NLM 2007 MeSH took 8.845329284667969e-05s
Availability | VoID file availability check for NLM 2007 MeSH took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for NLM 2007 MeSH took 0.18356990814208984s
Reputation | Calculation of the PageRank for NLM 2007 MeSH took 0.02123260498046875s
Interlinking | Calculation of Degree of Connection for NLM 2007 MeSH took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NLM 2007 MeSH took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for NLM 2007 MeSH took 3.457069396972656e-05s
Believability | Calculation of trust value for NLM 2007 MeSH took 1.2636184692382812e-05s
INFO | --- Analysis for nlm_2007_mesh took 2.057199716567993s
Availability | SPARQL endpoint availability check for National Library of Russia BibCore Dataset took 4.38690185546875e-05s
Availability | VoID file availability check for National Library of Russia BibCore Dataset took 0.0002741813659667969s
Completeness | Calculation of interlinking completeness for National Library of Russia BibCore Dataset took 0.19118809700012207s
Reputation | Calculation of the PageRank for National Library of Russia BibCore Dataset took 0.020400047302246094s
Interlinking | Calculation of Degree of Connection for National Library of Russia BibCore Dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for National Library of Russia BibCore Dataset took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for National Library of Russia BibCore Dataset took 3.075599670410156e-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.2789812088012695s
Availability | SPARQL endpoint availability check for Neulateinische Wortliste in LiLa took 8.392333984375e-05s
Availability | VoID file availability check for Neulateinische Wortliste in LiLa took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Neulateinische Wortliste in LiLa took 0.23840928077697754s
Reputation | Calculation of the PageRank for Neulateinische Wortliste in LiLa took 0.020021915435791016s
Interlinking | Calculation of Degree of Connection for Neulateinische Wortliste in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Neulateinische Wortliste in LiLa took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Neulateinische Wortliste in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for Neulateinische Wortliste in LiLa took 7.867813110351562e-06s
INFO | --- Analysis for NLW took 3.3029134273529053s
Availability | SPARQL endpoint availability check for Nobel Prizes took 4.029273986816406e-05s
Availability | VoID file availability check for Nobel Prizes took 0.0002796649932861328s
Completeness | Calculation of interlinking completeness for Nobel Prizes took 0.3557755947113037s
Reputation | Calculation of the PageRank for Nobel Prizes took 0.02019953727722168s
Interlinking | Calculation of Degree of Connection for Nobel Prizes took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Nobel Prizes took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Nobel Prizes took 8.821487426757812e-05s
Believability | Calculation of trust value for Nobel Prizes took 7.3909759521484375e-06s
INFO | --- Analysis for nobelprizes took 3.832331895828247s
Availability | SPARQL endpoint availability check for NoiPA took 4.0531158447265625e-05s
Availability | VoID file availability check for NoiPA took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for NoiPA took 0.3738560676574707s
Reputation | Calculation of the PageRank for NoiPA took 0.020195722579956055s
Interlinking | Calculation of Degree of Connection for NoiPA took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NoiPA took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for NoiPA took 2.9087066650390625e-05s
Believability | Calculation of trust value for NoiPA took 7.867813110351562e-06s
INFO | --- Analysis for NoiPA took 5.4706830978393555s
Availability | SPARQL endpoint availability check for Nomenclature for Museum Cataloging took 2.913120746612549s
Availability | VoID file availability check for Nomenclature for Museum Cataloging took 0.0002551078796386719s
Completeness | Calculation of interlinking completeness for Nomenclature for Museum Cataloging took 0.2862973213195801s
Reputation | Calculation of the PageRank for Nomenclature for Museum Cataloging took 0.02072429656982422s
Interlinking | Calculation of Degree of Connection for Nomenclature for Museum Cataloging took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomenclature for Museum Cataloging took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Nomenclature for Museum Cataloging took 9.417533874511719e-05s
Believability | Calculation of trust value for Nomenclature for Museum Cataloging took 1.2159347534179688e-05s
INFO | --- Analysis for nom took 6.345828056335449s
Availability | SPARQL endpoint availability check for Nomenclator Asturias took 8.177757263183594e-05s
Availability | VoID file availability check for Nomenclator Asturias took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for Nomenclator Asturias took 0.18453454971313477s
Reputation | Calculation of the PageRank for Nomenclator Asturias took 0.02034449577331543s
Interlinking | Calculation of Degree of Connection for Nomenclator Asturias took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Nomenclator Asturias took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Nomenclator Asturias took 7.43865966796875e-05s
Believability | Calculation of trust value for Nomenclator Asturias took 1.239776611328125e-05s
INFO | --- Analysis for nomenclator-asturias took 2.0346202850341797s
Availability | SPARQL endpoint availability check for nomisma took 8.320808410644531e-05s
Availability | VoID file availability check for nomisma took 0.00037217140197753906s
Completeness | Calculation of interlinking completeness for nomisma took 0.18964385986328125s
Reputation | Calculation of the PageRank for nomisma took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for nomisma took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for nomisma took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for nomisma took 2.7894973754882812e-05s
Believability | Calculation of trust value for nomisma took 1.2636184692382812e-05s
INFO | --- Analysis for nomisma took 2.041301965713501s
Availability | SPARQL endpoint availability check for Nomisma.org  took 0.4754204750061035s
Availability | VoID file availability check for Nomisma.org  took 0.0002377033233642578s
Extra | Recovery of all triples for Nomisma.org  took 300.08943581581116s
Performance | Total latancy measurement for Nomisma.org  took 2.096683979034424s
Amount of data | Number of triples check for Nomisma.org  took 38.89096403121948s
Interoperability | New terms check for Nomisma.org  took 11.667658805847168s
Versatility | Languages check for Nomisma.org  took 92.13205766677856s
Interpretability | Number of blank nodes check for Nomisma.org  took 29.18746304512024s
Security | Check HTTPS for Nomisma.org  took 0.8432891368865967s
Interpretability | RDF structures check for Nomisma.org  took 0.4160497188568115s
Versatility | Serialization formats check for Nomisma.org  took 0.4081761837005615s
Availability | RDF dump link check for Nomisma.org  took 829.704247713089s
License | MR license check for Nomisma.org  took 0.5989394187927246s
License | HR license check for Nomisma.org  took 62.81085681915283s
Amount of data | Number of property check for Nomisma.org  took 0.4380955696105957s
Understandability | Number of label check for Nomisma.org  took 6.766193866729736s
Understandability | URI regex check for Nomisma.org  took 0.8243718147277832s
Understandability | Vocabs check for Nomisma.org  took 0.3881947994232178s
Verifiability | Authors check for Nomisma.org  took 0.3855910301208496s
Verifiability | Publishers check for Nomisma.org  took 0.42710328102111816s
Performance | Throughput check for Nomisma.org  took 11.822393417358398s
Amount of data | Check the number of entities for Nomisma.org  took 0.0009765625s
Verifiability | Contribs. check for Nomisma.org  took 0.45345640182495117s
Interlinking | sameAs chians check for Nomisma.org  took 0.42252659797668457s
Interlinking | skos check for Nomisma.org  took 1.1108746528625488s
Interlinking | skos check for Nomisma.org  took 0.5582547187805176s
Timeliness | dataset update frequency check for Nomisma.org  took 0.39211010932922363s
Currency | Creation date check for Nomisma.org  took 0.8719029426574707s
Currency | Modification date check for Nomisma.org  took 0.8500711917877197s
Rep.Conc. | URIs length for Nomisma.org  took 554.5291771888733s
Interoperability | New vocabularies check for Nomisma.org  took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Nomisma.org  took 0.4345724582672119s
Accuracy | Check Functional Property for Nomisma.org  took 0.40993237495422363s
Accuracy | Check Inverse Functional Property for Nomisma.org  took 0.7785341739654541s
Accuracy | Check Empty annotation labels for Nomisma.org  took 567.2455327510834s
Accuracy | Check White space in annotation for Nomisma.org  took 2.720134735107422s
Consistency | Disjoint class check for Nomisma.org  took 1.7502353191375732s
Consistency | Check Misplaced properties for Nomisma.org  took 28.000598907470703s
Consistency | Check Ontology hijacking for Nomisma.org  took 258.69457268714905s
Consistency | Check Invalid usage of undefined properties for Nomisma.org  took 27.803210258483887s
Conciseness | Check Extensional conciseness for Nomisma.org  took 0.0001323223114013672s
Conciseness | Check Intensional conciseness for Nomisma.org  took 0.45535993576049805s
Security | Sign check for Nomisma.org  took 0.46944546699523926s
Availability | Check URIs Dereferenciability for Nomisma.org  took 2103.191138982773s
Completeness | Calculation of interlinking completeness for Nomisma.org  took 0.21391701698303223s
Reputation | Calculation of the PageRank for Nomisma.org  took 0.022498130798339844s
Interlinking | Calculation of Degree of Connection for Nomisma.org  took 6.318092346191406e-05s
Interlinking | Calculation of Centrality for Nomisma.org  took 0.0008044242858886719s
Interlinking | Calculation of Clustering coefficient for Nomisma.org  took 9.775161743164062e-05s
Interoperability | Check the re-using of existing vocabs for Nomisma.org  took 1.6689300537109375e-06s
Believability | Calculation of trust value for Nomisma.org  took 1.1920928955078125e-05s
INFO | --- Analysis for nomisma_org took 8271.37195277214s
Availability | SPARQL endpoint availability check for Curriculum Vitae took 4.0531158447265625e-05s
Availability | VoID file availability check for Curriculum Vitae took 0.0002579689025878906s
Completeness | Calculation of interlinking completeness for Curriculum Vitae took 0.18282008171081543s
Reputation | Calculation of the PageRank for Curriculum Vitae took 0.02031707763671875s
Interlinking | Calculation of Degree of Connection for Curriculum Vitae took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Curriculum Vitae took 0.0007529258728027344s
Interlinking | Calculation of Clustering coefficient for Curriculum Vitae took 2.9802322387695312e-05s
Believability | Calculation of trust value for Curriculum Vitae took 8.344650268554688e-06s
INFO | --- Analysis for Nordine_Bittich took 2.008241653442383s
Availability | SPARQL endpoint availability check for NorPark took 8.082389831542969e-05s
Availability | VoID file availability check for NorPark took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for NorPark took 0.17995452880859375s
Reputation | Calculation of the PageRank for NorPark took 0.022164106369018555s
Interlinking | Calculation of Degree of Connection for NorPark took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for NorPark took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for NorPark took 4.100799560546875e-05s
Believability | Calculation of trust value for NorPark took 7.3909759521484375e-06s
INFO | --- Analysis for norpark took 2.032135486602783s
Availability | SPARQL endpoint availability check for Parking Dataset took 8.487701416015625e-05s
Availability | VoID file availability check for Parking Dataset took 0.00044846534729003906s
Completeness | Calculation of interlinking completeness for Parking Dataset took 0.19241070747375488s
Reputation | Calculation of the PageRank for Parking Dataset took 0.021835803985595703s
Interlinking | Calculation of Degree of Connection for Parking Dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Parking Dataset took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Parking Dataset took 4.2438507080078125e-05s
Believability | Calculation of trust value for Parking Dataset took 1.2159347534179688e-05s
INFO | --- Analysis for norpark2 took 2.024855852127075s
Availability | SPARQL endpoint availability check for Norway fishery stocks dataset took 3.933906555175781e-05s
Availability | VoID file availability check for Norway fishery stocks dataset took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for Norway fishery stocks dataset took 0.19381952285766602s
Reputation | Calculation of the PageRank for Norway fishery stocks dataset took 0.0204010009765625s
Interlinking | Calculation of Degree of Connection for Norway fishery stocks dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Norway fishery stocks dataset took 0.0007336139678955078s
Interlinking | Calculation of Clustering coefficient for Norway fishery stocks dataset took 3.0040740966796875e-05s
Believability | Calculation of trust value for Norway fishery stocks dataset took 1.2636184692382812e-05s
INFO | --- Analysis for Norway_Fishery_ took 2.038072347640991s
Availability | SPARQL endpoint availability check for Norwegian geo-divisions took 7.915496826171875e-05s
Availability | VoID file availability check for Norwegian geo-divisions took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for Norwegian geo-divisions took 0.18541431427001953s
Reputation | Calculation of the PageRank for Norwegian geo-divisions took 0.020245790481567383s
Interlinking | Calculation of Degree of Connection for Norwegian geo-divisions took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Norwegian geo-divisions took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for Norwegian geo-divisions took 4.601478576660156e-05s
Believability | Calculation of trust value for Norwegian geo-divisions took 1.0013580322265625e-05s
INFO | --- Analysis for norwegian-geo-divisions took 2.0074167251586914s
Availability | SPARQL endpoint availability check for NorwegianSoE took 7.987022399902344e-05s
Availability | VoID file availability check for NorwegianSoE took 0.0004775524139404297s
Completeness | Calculation of interlinking completeness for NorwegianSoE took 0.18159842491149902s
Reputation | Calculation of the PageRank for NorwegianSoE took 0.020292282104492188s
Interlinking | Calculation of Degree of Connection for NorwegianSoE took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NorwegianSoE took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for NorwegianSoE took 2.9325485229492188e-05s
Believability | Calculation of trust value for NorwegianSoE took 1.0251998901367188e-05s
INFO | --- Analysis for norwegiansoe took 2.021223545074463s
Availability | SPARQL endpoint availability check for NITP took 4.100799560546875e-05s
Availability | VoID file availability check for NITP took 0.00045299530029296875s
Completeness | Calculation of interlinking completeness for NITP took 0.1729435920715332s
Reputation | Calculation of the PageRank for NITP took 0.02040576934814453s
Interlinking | Calculation of Degree of Connection for NITP took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for NITP took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for NITP took 6.437301635742188e-05s
Believability | Calculation of trust value for NITP took 5.7220458984375e-06s
INFO | --- Analysis for notIdentifier took 2.0269484519958496s
Availability | SPARQL endpoint availability check for Nottingham Trent University Resource Lists took 7.891654968261719e-05s
Availability | VoID file availability check for Nottingham Trent University Resource Lists took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for Nottingham Trent University Resource Lists took 0.23438453674316406s
Reputation | Calculation of the PageRank for Nottingham Trent University Resource Lists took 0.02254199981689453s
Interlinking | Calculation of Degree of Connection for Nottingham Trent University Resource Lists took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Nottingham Trent University Resource Lists took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for Nottingham Trent University Resource Lists took 3.457069396972656e-05s
Believability | Calculation of trust value for Nottingham Trent University Resource Lists took 1.2874603271484375e-05s
INFO | --- Analysis for nottingham-trent-university-resource-lists took 2.0681114196777344s
Availability | SPARQL endpoint availability check for Nature Publishing Group - ALL took 9.083747863769531e-05s
Availability | VoID file availability check for Nature Publishing Group - ALL took 0.0009005069732666016s
Completeness | Calculation of interlinking completeness for Nature Publishing Group - ALL took 0.17608094215393066s
Reputation | Calculation of the PageRank for Nature Publishing Group - ALL took 0.02169489860534668s
Interlinking | Calculation of Degree of Connection for Nature Publishing Group - ALL took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Nature Publishing Group - ALL took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for Nature Publishing Group - ALL took 2.9802322387695312e-05s
Believability | Calculation of trust value for Nature Publishing Group - ALL took 1.2874603271484375e-05s
INFO | --- Analysis for npg took 1.9901673793792725s
Availability | SPARQL endpoint availability check for NPM took 3.910064697265625e-05s
Availability | VoID file availability check for NPM took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for NPM took 0.17445778846740723s
Reputation | Calculation of the PageRank for NPM took 0.020328998565673828s
Interlinking | Calculation of Degree of Connection for NPM took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for NPM took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for NPM took 3.3855438232421875e-05s
Believability | Calculation of trust value for NPM took 1.0251998901367188e-05s
INFO | --- Analysis for npm took 1.9779975414276123s
Availability | SPARQL endpoint availability check for NTNU special collections took 0.050340890884399414s
Availability | VoID file availability check for NTNU special collections took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for NTNU special collections took 0.17693471908569336s
Reputation | Calculation of the PageRank for NTNU special collections took 0.02060985565185547s
Interlinking | Calculation of Degree of Connection for NTNU special collections took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for NTNU special collections took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for NTNU special collections took 5.53131103515625e-05s
Believability | Calculation of trust value for NTNU special collections took 9.5367431640625e-06s
INFO | --- Analysis for ntnusc took 2.083587408065796s
Availability | SPARQL endpoint availability check for links took 8.177757263183594e-05s
Availability | VoID file availability check for links took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for links took 0.17358183860778809s
Reputation | Calculation of the PageRank for links took 0.0205841064453125s
Interlinking | Calculation of Degree of Connection for links took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for links took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for links took 1.1682510375976562e-05s
Believability | Calculation of trust value for links took 1.0013580322265625e-05s
INFO | --- Analysis for nugmyanmar took 1.9822330474853516s
Availability | SPARQL endpoint availability check for NUTS (GeoVocab) took 4.124641418457031e-05s
Availability | VoID file availability check for NUTS (GeoVocab) took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for NUTS (GeoVocab) took 0.1893320083618164s
Reputation | Calculation of the PageRank for NUTS (GeoVocab) took 0.020285844802856445s
Interlinking | Calculation of Degree of Connection for NUTS (GeoVocab) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for NUTS (GeoVocab) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for NUTS (GeoVocab) took 9.918212890625e-05s
Believability | Calculation of trust value for NUTS (GeoVocab) took 1.0728836059570312e-05s
INFO | --- Analysis for nuts-geovocab took 2.000985860824585s
Availability | SPARQL endpoint availability check for Norsk inndeling av vitenskapsdisipliner took 4.029273986816406e-05s
Availability | VoID file availability check for Norsk inndeling av vitenskapsdisipliner took 0.0003871917724609375s
Completeness | Calculation of interlinking completeness for Norsk inndeling av vitenskapsdisipliner took 0.18004655838012695s
Reputation | Calculation of the PageRank for Norsk inndeling av vitenskapsdisipliner took 0.022034406661987305s
Interlinking | Calculation of Degree of Connection for Norsk inndeling av vitenskapsdisipliner took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Norsk inndeling av vitenskapsdisipliner took 0.0011091232299804688s
Interlinking | Calculation of Clustering coefficient for Norsk inndeling av vitenskapsdisipliner took 8.225440979003906e-05s
Believability | Calculation of trust value for Norsk inndeling av vitenskapsdisipliner took 7.3909759521484375e-06s
INFO | --- Analysis for nvd took 1.9831769466400146s
Availability | SPARQL endpoint availability check for NERC Vocabulary Server 2.0 took 8.177757263183594e-05s
Availability | VoID file availability check for NERC Vocabulary Server 2.0 took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for NERC Vocabulary Server 2.0 took 0.17444801330566406s
Reputation | Calculation of the PageRank for NERC Vocabulary Server 2.0 took 0.020305156707763672s
Interlinking | Calculation of Degree of Connection for NERC Vocabulary Server 2.0 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for NERC Vocabulary Server 2.0 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for NERC Vocabulary Server 2.0 took 7.462501525878906e-05s
Believability | Calculation of trust value for NERC Vocabulary Server 2.0 took 1.0728836059570312e-05s
INFO | --- Analysis for nvs took 2.0350582599639893s
Availability | SPARQL endpoint availability check for New York Times - Linked Open Data took 3.933906555175781e-05s
Availability | VoID file availability check for New York Times - Linked Open Data took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for New York Times - Linked Open Data took 0.17962145805358887s
Reputation | Calculation of the PageRank for New York Times - Linked Open Data took 0.02114558219909668s
Interlinking | Calculation of Degree of Connection for New York Times - Linked Open Data took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for New York Times - Linked Open Data took 0.0007283687591552734s
Interlinking | Calculation of Clustering coefficient for New York Times - Linked Open Data took 0.0001819133758544922s
Believability | Calculation of trust value for New York Times - Linked Open Data took 1.1205673217773438e-05s
INFO | --- Analysis for nytimes-linked-open-data took 1.9914367198944092s
Availability | SPARQL endpoint availability check for American National Corpus - Open Portion took 8.20159912109375e-05s
Availability | VoID file availability check for American National Corpus - Open Portion took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for American National Corpus - Open Portion took 0.18146753311157227s
Reputation | Calculation of the PageRank for American National Corpus - Open Portion took 0.0202333927154541s
Interlinking | Calculation of Degree of Connection for American National Corpus - Open Portion took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for American National Corpus - Open Portion took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for American National Corpus - Open Portion took 2.765655517578125e-05s
Believability | Calculation of trust value for American National Corpus - Open Portion took 1.1205673217773438e-05s
INFO | --- Analysis for o-anc took 2.033839464187622s
Availability | SPARQL endpoint availability check for OANetzwerk took 8.368492126464844e-05s
Availability | VoID file availability check for OANetzwerk took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for OANetzwerk took 0.18254876136779785s
Reputation | Calculation of the PageRank for OANetzwerk took 0.020955562591552734s
Interlinking | Calculation of Degree of Connection for OANetzwerk took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OANetzwerk took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for OANetzwerk took 2.8371810913085938e-05s
Believability | Calculation of trust value for OANetzwerk took 1.3113021850585938e-05s
INFO | --- Analysis for oanetzwerk took 2.0553972721099854s
Availability | SPARQL endpoint availability check for Obce, okresy a kraje České republiky took 3.981590270996094e-05s
Availability | VoID file availability check for Obce, okresy a kraje České republiky took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for Obce, okresy a kraje České republiky took 0.1831221580505371s
Reputation | Calculation of the PageRank for Obce, okresy a kraje České republiky took 0.020351409912109375s
Interlinking | Calculation of Degree of Connection for Obce, okresy a kraje České republiky took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Obce, okresy a kraje České republiky took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Obce, okresy a kraje České republiky took 2.9325485229492188e-05s
Believability | Calculation of trust value for Obce, okresy a kraje České republiky took 1.0967254638671875e-05s
INFO | --- Analysis for obce--okresy-a-kraje--esk--republiky took 2.013721227645874s
Availability | SPARQL endpoint availability check for Italian Chamber of Deputies - official dataset took 9.465217590332031e-05s
Availability | VoID file availability check for Italian Chamber of Deputies - official dataset took 0.00020742416381835938s
Completeness | Calculation of interlinking completeness for Italian Chamber of Deputies - official dataset took 0.1695094108581543s
Reputation | Calculation of the PageRank for Italian Chamber of Deputies - official dataset took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Italian Chamber of Deputies - official dataset took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Italian Chamber of Deputies - official dataset took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Italian Chamber of Deputies - official dataset took 8.96453857421875e-05s
Believability | Calculation of trust value for Italian Chamber of Deputies - official dataset took 1.0013580322265625e-05s
INFO | --- Analysis for ocd took 1.9702579975128174s
Availability | SPARQL endpoint availability check for oceandrilling-borehole took 3.8623809814453125e-05s
Availability | VoID file availability check for oceandrilling-borehole took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for oceandrilling-borehole took 0.18359947204589844s
Reputation | Calculation of the PageRank for oceandrilling-borehole took 0.020957231521606445s
Interlinking | Calculation of Degree of Connection for oceandrilling-borehole took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for oceandrilling-borehole took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for oceandrilling-borehole took 3.504753112792969e-05s
Believability | Calculation of trust value for oceandrilling-borehole took 5.7220458984375e-06s
INFO | --- Analysis for oceandrilling-borehole took 1.9780981540679932s
Availability | SPARQL endpoint availability check for Ocean Drilling - Codices took 8.392333984375e-05s
Availability | VoID file availability check for Ocean Drilling - Codices took 0.0004715919494628906s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Codices took 0.17284727096557617s
Reputation | Calculation of the PageRank for Ocean Drilling - Codices took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Codices took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Codices took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Codices took 7.43865966796875e-05s
Believability | Calculation of trust value for Ocean Drilling - Codices took 1.239776611328125e-05s
INFO | --- Analysis for oceandrilling-codices took 1.9932234287261963s
Availability | SPARQL endpoint availability check for Ocean Drilling - dbSEABED took 4.291534423828125e-05s
Availability | VoID file availability check for Ocean Drilling - dbSEABED took 0.0005216598510742188s
Completeness | Calculation of interlinking completeness for Ocean Drilling - dbSEABED took 0.1787419319152832s
Reputation | Calculation of the PageRank for Ocean Drilling - dbSEABED took 0.021933317184448242s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - dbSEABED took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - dbSEABED took 0.0008349418640136719s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - dbSEABED took 3.361701965332031e-05s
Believability | Calculation of trust value for Ocean Drilling - dbSEABED took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-dbseabed took 1.9784760475158691s
Availability | SPARQL endpoint availability check for Ocean Drilling - Forams took 0.00011110305786132812s
Availability | VoID file availability check for Ocean Drilling - Forams took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Forams took 0.1759636402130127s
Reputation | Calculation of the PageRank for Ocean Drilling - Forams took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Forams took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Forams took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Forams took 3.552436828613281e-05s
Believability | Calculation of trust value for Ocean Drilling - Forams took 1.3113021850585938e-05s
INFO | --- Analysis for oceandrilling-forams took 2.052102565765381s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus LOD took 8.7738037109375e-05s
Availability | VoID file availability check for Ocean Drilling - Janus LOD took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus LOD took 0.18487167358398438s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus LOD took 0.020665645599365234s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus LOD took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus LOD took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus LOD took 3.075599670410156e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus LOD took 6.67572021484375e-06s
INFO | --- Analysis for oceandrilling-janus took 1.9933459758758545s
Availability | SPARQL endpoint availability check for Ocean Drilling - Janus Age Models took 8.535385131835938e-05s
Availability | VoID file availability check for Ocean Drilling - Janus Age Models took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for Ocean Drilling - Janus Age Models took 0.18392682075500488s
Reputation | Calculation of the PageRank for Ocean Drilling - Janus Age Models took 0.020552873611450195s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - Janus Age Models took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Ocean Drilling - Janus Age Models took 0.001050710678100586s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - Janus Age Models took 3.838539123535156e-05s
Believability | Calculation of trust value for Ocean Drilling - Janus Age Models took 1.2159347534179688e-05s
INFO | --- Analysis for oceandrilling-janusamp took 2.008847951889038s
Availability | SPARQL endpoint availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 3.910064697265625e-05s
Availability | VoID file availability check for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.1720447540283203s
Reputation | Calculation of the PageRank for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.021434783935546875s
Interlinking | Calculation of Degree of Connection for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Ocean Drilling - LDEO log files as data (TEST leg 218 only) took 1.1444091796875e-05s
INFO | --- Analysis for oceandrilling-ldeo took 1.9659955501556396s
Availability | SPARQL endpoint availability check for Faceted Application of Subject Terminology took 4.1484832763671875e-05s
Availability | VoID file availability check for Faceted Application of Subject Terminology took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Faceted Application of Subject Terminology took 0.17497777938842773s
Reputation | Calculation of the PageRank for Faceted Application of Subject Terminology took 0.023406505584716797s
Interlinking | Calculation of Degree of Connection for Faceted Application of Subject Terminology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Faceted Application of Subject Terminology took 0.0010852813720703125s
Interlinking | Calculation of Clustering coefficient for Faceted Application of Subject Terminology took 6.437301635742188e-05s
Believability | Calculation of trust value for Faceted Application of Subject Terminology took 1.239776611328125e-05s
INFO | --- Analysis for oclc-fast took 1.987675666809082s
Availability | SPARQL endpoint availability check for Open Data Communities took 3.910064697265625e-05s
Availability | VoID file availability check for Open Data Communities took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Open Data Communities took 0.16942548751831055s
Reputation | Calculation of the PageRank for Open Data Communities took 0.020325422286987305s
Interlinking | Calculation of Degree of Connection for Open Data Communities took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Open Data Communities took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Open Data Communities took 2.6702880859375e-05s
Believability | Calculation of trust value for Open Data Communities took 1.049041748046875e-05s
INFO | --- Analysis for odc took 1.9762001037597656s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 7.987022399902344e-05s
Availability | VoID file availability check for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.1852867603302002s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 2.8133392333984375e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation, Living Environment Deprivation Domain, Scores 2010 took 1.0728836059570312e-05s
INFO | --- Analysis for odc-imd-environment-score took 1.9675805568695068s
Availability | SPARQL endpoint availability check for Index of Multiple Deprivation Ranking, 2007 took 4.124641418457031e-05s
Availability | VoID file availability check for Index of Multiple Deprivation Ranking, 2007 took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for Index of Multiple Deprivation Ranking, 2007 took 0.18780875205993652s
Reputation | Calculation of the PageRank for Index of Multiple Deprivation Ranking, 2007 took 0.020238399505615234s
Interlinking | Calculation of Degree of Connection for Index of Multiple Deprivation Ranking, 2007 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Index of Multiple Deprivation Ranking, 2007 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Index of Multiple Deprivation Ranking, 2007 took 2.6941299438476562e-05s
Believability | Calculation of trust value for Index of Multiple Deprivation Ranking, 2007 took 6.198883056640625e-06s
INFO | --- Analysis for odc-imd-rank-2007 took 1.9606530666351318s
Availability | SPARQL endpoint availability check for Open Data Communities - Lower layer Super Output Areas took 8.440017700195312e-05s
Availability | VoID file availability check for Open Data Communities - Lower layer Super Output Areas took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Open Data Communities - Lower layer Super Output Areas took 0.17827653884887695s
Reputation | Calculation of the PageRank for Open Data Communities - Lower layer Super Output Areas took 0.020143747329711914s
Interlinking | Calculation of Degree of Connection for Open Data Communities - Lower layer Super Output Areas took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Open Data Communities - Lower layer Super Output Areas took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Open Data Communities - Lower layer Super Output Areas took 3.170967102050781e-05s
Believability | Calculation of trust value for Open Data Communities - Lower layer Super Output Areas took 1.2159347534179688e-05s
INFO | --- Analysis for odc-lsoa took 1.9751975536346436s
Availability | SPARQL endpoint availability check for Estimated mid-year population 2005 took 8.273124694824219e-05s
Availability | VoID file availability check for Estimated mid-year population 2005 took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Estimated mid-year population 2005 took 0.17778778076171875s
Reputation | Calculation of the PageRank for Estimated mid-year population 2005 took 0.02041339874267578s
Interlinking | Calculation of Degree of Connection for Estimated mid-year population 2005 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Estimated mid-year population 2005 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Estimated mid-year population 2005 took 2.7418136596679688e-05s
Believability | Calculation of trust value for Estimated mid-year population 2005 took 1.1682510375976562e-05s
INFO | --- Analysis for odc-population-2005 took 1.9751179218292236s
Availability | SPARQL endpoint availability check for Open Discovery Space (ODS) took 4.029273986816406e-05s
Availability | VoID file availability check for Open Discovery Space (ODS) took 0.00021147727966308594s
Completeness | Calculation of interlinking completeness for Open Discovery Space (ODS) took 0.16820096969604492s
Reputation | Calculation of the PageRank for Open Discovery Space (ODS) took 0.020046234130859375s
Interlinking | Calculation of Degree of Connection for Open Discovery Space (ODS) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Discovery Space (ODS) took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Open Discovery Space (ODS) took 2.7418136596679688e-05s
Believability | Calculation of trust value for Open Discovery Space (ODS) took 7.62939453125e-06s
INFO | --- Analysis for ods took 1.963735580444336s
Availability | SPARQL endpoint availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 3.933906555175781e-05s
Availability | VoID file availability check for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.1773688793182373s
Reputation | Calculation of the PageRank for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0200655460357666s
Interlinking | Calculation of Degree of Connection for Organisation for Economic Co-operation and Development (OECD) Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Organisation for Economic Co-operation and Development (OECD) Linked Data took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Organisation for Economic Co-operation and Development (OECD) Linked Data took 8.893013000488281e-05s
Believability | Calculation of trust value for Organisation for Economic Co-operation and Development (OECD) Linked Data took 1.1920928955078125e-05s
INFO | --- Analysis for oecd-linked-data took 1.961498498916626s
Availability | SPARQL endpoint availability check for Offener Haushalt took 4.0531158447265625e-05s
Availability | VoID file availability check for Offener Haushalt took 0.000232696533203125s
Completeness | Calculation of interlinking completeness for Offener Haushalt took 0.17743492126464844s
Reputation | Calculation of the PageRank for Offener Haushalt took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for Offener Haushalt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Offener Haushalt took 0.0007495880126953125s
Interlinking | Calculation of Clustering coefficient for Offener Haushalt took 2.8371810913085938e-05s
Believability | Calculation of trust value for Offener Haushalt took 7.3909759521484375e-06s
INFO | --- Analysis for offener-haushalt took 1.9347846508026123s
Availability | SPARQL endpoint availability check for Orthology and Diseases Information - OGO took 3.886222839355469e-05s
Availability | VoID file availability check for Orthology and Diseases Information - OGO took 0.00024390220642089844s
Completeness | Calculation of interlinking completeness for Orthology and Diseases Information - OGO took 0.17053985595703125s
Reputation | Calculation of the PageRank for Orthology and Diseases Information - OGO took 0.020294666290283203s
Interlinking | Calculation of Degree of Connection for Orthology and Diseases Information - OGO took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Orthology and Diseases Information - OGO took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Orthology and Diseases Information - OGO took 3.6716461181640625e-05s
Believability | Calculation of trust value for Orthology and Diseases Information - OGO took 6.9141387939453125e-06s
INFO | --- Analysis for ogolod took 2.170055627822876s
Availability | SPARQL endpoint availability check for OLAC Metadata took 8.034706115722656e-05s
Availability | VoID file availability check for OLAC Metadata took 0.0002448558807373047s
Completeness | Calculation of interlinking completeness for OLAC Metadata took 0.1774129867553711s
Reputation | Calculation of the PageRank for OLAC Metadata took 0.020294904708862305s
Interlinking | Calculation of Degree of Connection for OLAC Metadata took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for OLAC Metadata took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for OLAC Metadata took 3.552436828613281e-05s
Believability | Calculation of trust value for OLAC Metadata took 7.62939453125e-06s
INFO | --- Analysis for olac took 1.9256324768066406s
Availability | SPARQL endpoint availability check for OLiA took 4.029273986816406e-05s
Availability | VoID file availability check for OLiA took 0.000301361083984375s
Completeness | Calculation of interlinking completeness for OLiA took 0.17770028114318848s
Reputation | Calculation of the PageRank for OLiA took 0.02021002769470215s
Interlinking | Calculation of Degree of Connection for OLiA took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for OLiA took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for OLiA took 0.00011944770812988281s
Believability | Calculation of trust value for OLiA took 6.9141387939453125e-06s
INFO | --- Analysis for olia took 1.9715185165405273s
Availability | SPARQL endpoint availability check for OLiA Discourse took 8.630752563476562e-05s
Availability | VoID file availability check for OLiA Discourse took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for OLiA Discourse took 0.18288183212280273s
Reputation | Calculation of the PageRank for OLiA Discourse took 0.0210268497467041s
Interlinking | Calculation of Degree of Connection for OLiA Discourse took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OLiA Discourse took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for OLiA Discourse took 4.2438507080078125e-05s
Believability | Calculation of trust value for OLiA Discourse took 1.1682510375976562e-05s
INFO | --- Analysis for olia-discourse took 1.98919677734375s
Availability | SPARQL endpoint availability check for Open Land Use took 8.249282836914062e-05s
Availability | VoID file availability check for Open Land Use took 0.0004818439483642578s
Completeness | Calculation of interlinking completeness for Open Land Use took 0.19510197639465332s
Reputation | Calculation of the PageRank for Open Land Use took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for Open Land Use took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Land Use took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Open Land Use took 2.8133392333984375e-05s
Believability | Calculation of trust value for Open Land Use took 1.2159347534179688e-05s
INFO | --- Analysis for OLU took 1.974898099899292s
Availability | SPARQL endpoint availability check for OmegaWiki took 8.225440979003906e-05s
Availability | VoID file availability check for OmegaWiki took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for OmegaWiki took 0.18258929252624512s
Reputation | Calculation of the PageRank for OmegaWiki took 0.021292924880981445s
Interlinking | Calculation of Degree of Connection for OmegaWiki took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for OmegaWiki took 0.0011091232299804688s
Interlinking | Calculation of Clustering coefficient for OmegaWiki took 3.6716461181640625e-05s
Believability | Calculation of trust value for OmegaWiki took 1.1682510375976562e-05s
INFO | --- Analysis for omegawiki took 1.9677748680114746s
Availability | SPARQL endpoint availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Availability | VoID file availability check for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for Albanet WordNet (as part of Open Multilingual WordNet) took 0.17381620407104492s
Reputation | Calculation of the PageRank for Albanet WordNet (as part of Open Multilingual WordNet) took 0.020558834075927734s
Interlinking | Calculation of Degree of Connection for Albanet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Albanet WordNet (as part of Open Multilingual WordNet) took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Albanet WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Albanet WordNet (as part of Open Multilingual WordNet) took 7.3909759521484375e-06s
INFO | --- Analysis for omwn-als took 1.9793357849121094s
Availability | SPARQL endpoint availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 8.249282836914062e-05s
Availability | VoID file availability check for Arabic WordNet (as part of Open Multilingual WordNet) took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Arabic WordNet (as part of Open Multilingual WordNet) took 0.17332673072814941s
Reputation | Calculation of the PageRank for Arabic WordNet (as part of Open Multilingual WordNet) took 0.02161264419555664s
Interlinking | Calculation of Degree of Connection for Arabic WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Arabic WordNet (as part of Open Multilingual WordNet) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Arabic WordNet (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Arabic WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-arb took 1.9687445163726807s
Availability | SPARQL endpoint availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 7.843971252441406e-05s
Availability | VoID file availability check for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.1810154914855957s
Reputation | Calculation of the PageRank for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.020342350006103516s
Interlinking | Calculation of Degree of Connection for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 3.719329833984375e-05s
Believability | Calculation of trust value for BulTreeBank WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-bul took 1.9665136337280273s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 8.082389831542969e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0004961490631103516s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.18049287796020508s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.02020549774169922s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0006973743438720703s
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 1.0251998901367188e-05s
INFO | --- Analysis for omwn-cow took 1.9837887287139893s
Availability | SPARQL endpoint availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 8.20159912109375e-05s
Availability | VoID file availability check for Chinese WordNet (as part of Open Multilingual WordNet) took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Chinese WordNet (as part of Open Multilingual WordNet) took 0.17549443244934082s
Reputation | Calculation of the PageRank for Chinese WordNet (as part of Open Multilingual WordNet) took 0.020354032516479492s
Interlinking | Calculation of Degree of Connection for Chinese WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Chinese WordNet (as part of Open Multilingual WordNet) took 0.0007522106170654297s
Interlinking | Calculation of Clustering coefficient for Chinese WordNet (as part of Open Multilingual WordNet) took 3.552436828613281e-05s
Believability | Calculation of trust value for Chinese WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-cwn took 1.9724724292755127s
Availability | SPARQL endpoint availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 4.1484832763671875e-05s
Availability | VoID file availability check for DanNet WordNet (as part of Open Multilingual WordNet) took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for DanNet WordNet (as part of Open Multilingual WordNet) took 0.17321562767028809s
Reputation | Calculation of the PageRank for DanNet WordNet (as part of Open Multilingual WordNet) took 0.02051830291748047s
Interlinking | Calculation of Degree of Connection for DanNet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for DanNet WordNet (as part of Open Multilingual WordNet) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for DanNet WordNet (as part of Open Multilingual WordNet) took 4.100799560546875e-05s
Believability | Calculation of trust value for DanNet WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-dan took 1.9795901775360107s
Availability | SPARQL endpoint availability check for Greek WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Availability | VoID file availability check for Greek WordNet (as part of Open Multilingual WordNet) took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Greek WordNet (as part of Open Multilingual WordNet) took 0.1790463924407959s
Reputation | Calculation of the PageRank for Greek WordNet (as part of Open Multilingual WordNet) took 0.020229578018188477s
Interlinking | Calculation of Degree of Connection for Greek WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Greek WordNet (as part of Open Multilingual WordNet) took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Greek WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Greek WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-ell took 1.9814093112945557s
Availability | SPARQL endpoint availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 8.368492126464844e-05s
Availability | VoID file availability check for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Princeton WordNet (as part of Open Multilingual WordNet) took 0.185774564743042s
Reputation | Calculation of the PageRank for Princeton WordNet (as part of Open Multilingual WordNet) took 0.021724939346313477s
Interlinking | Calculation of Degree of Connection for Princeton WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Princeton WordNet (as part of Open Multilingual WordNet) took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Princeton WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Believability | Calculation of trust value for Princeton WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-eng took 1.979595422744751s
Availability | SPARQL endpoint availability check for Persian WordNet (as part of Open Multilingual WordNet) took 3.8623809814453125e-05s
Availability | VoID file availability check for Persian WordNet (as part of Open Multilingual WordNet) took 0.0002086162567138672s
Completeness | Calculation of interlinking completeness for Persian WordNet (as part of Open Multilingual WordNet) took 0.17721843719482422s
Reputation | Calculation of the PageRank for Persian WordNet (as part of Open Multilingual WordNet) took 0.020335674285888672s
Interlinking | Calculation of Degree of Connection for Persian WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Persian WordNet (as part of Open Multilingual WordNet) took 0.0007402896881103516s
Interlinking | Calculation of Clustering coefficient for Persian WordNet (as part of Open Multilingual WordNet) took 3.62396240234375e-05s
Believability | Calculation of trust value for Persian WordNet (as part of Open Multilingual WordNet) took 5.7220458984375e-06s
INFO | --- Analysis for omwn-fas took 2.032813787460327s
Availability | SPARQL endpoint availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 4.00543212890625e-05s
Availability | VoID file availability check for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004699230194091797s
Completeness | Calculation of interlinking completeness for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.17383527755737305s
Reputation | Calculation of the PageRank for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.02023148536682129s
Interlinking | Calculation of Degree of Connection for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for FinnWordNet WordNet (as part of Open Multilingual WordNet) took 6.198883056640625e-06s
INFO | --- Analysis for omwn-fin took 1.9512908458709717s
Availability | SPARQL endpoint availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Availability | VoID file availability check for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for WOLF WordNet (as part of Open Multilingual WordNet) took 0.1953113079071045s
Reputation | Calculation of the PageRank for WOLF WordNet (as part of Open Multilingual WordNet) took 0.021158933639526367s
Interlinking | Calculation of Degree of Connection for WOLF WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for WOLF WordNet (as part of Open Multilingual WordNet) took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for WOLF WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for WOLF WordNet (as part of Open Multilingual WordNet) took 1.2159347534179688e-05s
INFO | --- Analysis for omwn-fra took 2.0193028450012207s
Availability | SPARQL endpoint availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 8.511543273925781e-05s
Availability | VoID file availability check for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.18376636505126953s
Reputation | Calculation of the PageRank for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for Hebrew WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Hebrew WordNet (as part of Open Multilingual WordNet) took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Hebrew WordNet (as part of Open Multilingual WordNet) took 3.647804260253906e-05s
Believability | Calculation of trust value for Hebrew WordNet (as part of Open Multilingual WordNet) took 1.239776611328125e-05s
INFO | --- Analysis for omwn-heb took 1.994335412979126s
Availability | SPARQL endpoint availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 8.153915405273438e-05s
Availability | VoID file availability check for Croatian WordNet (as part of Open Multilingual WordNet) took 0.000530242919921875s
Completeness | Calculation of interlinking completeness for Croatian WordNet (as part of Open Multilingual WordNet) took 0.1830613613128662s
Reputation | Calculation of the PageRank for Croatian WordNet (as part of Open Multilingual WordNet) took 0.021840572357177734s
Interlinking | Calculation of Degree of Connection for Croatian WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Croatian WordNet (as part of Open Multilingual WordNet) took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for Croatian WordNet (as part of Open Multilingual WordNet) took 3.743171691894531e-05s
Believability | Calculation of trust value for Croatian WordNet (as part of Open Multilingual WordNet) took 1.1444091796875e-05s
INFO | --- Analysis for omwn-hrv took 2.016777276992798s
Availability | SPARQL endpoint availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.886222839355469e-05s
Availability | VoID file availability check for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0004966259002685547s
Completeness | Calculation of interlinking completeness for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.1718578338623047s
Reputation | Calculation of the PageRank for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.020198583602905273s
Interlinking | Calculation of Degree of Connection for IceWordNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IceWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for IceWordNet WordNet (as part of Open Multilingual WordNet) took 3.3855438232421875e-05s
Believability | Calculation of trust value for IceWordNet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-isl took 1.95294189453125s
Availability | SPARQL endpoint availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 9.226799011230469e-05s
Availability | VoID file availability check for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.00048232078552246094s
Completeness | Calculation of interlinking completeness for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.18472075462341309s
Reputation | Calculation of the PageRank for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for MultiWordNet WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-ita took 2.017068386077881s
Availability | SPARQL endpoint availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 8.368492126464844e-05s
Availability | VoID file availability check for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0004909038543701172s
Completeness | Calculation of interlinking completeness for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.17450857162475586s
Reputation | Calculation of the PageRank for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 3.504753112792969e-05s
Believability | Calculation of trust value for ItalWordnet WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-iwn took 1.9462933540344238s
Availability | SPARQL endpoint availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 3.981590270996094e-05s
Availability | VoID file availability check for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for Japanese WordNet (as part of Open Multilingual WordNet) took 0.1886577606201172s
Reputation | Calculation of the PageRank for Japanese WordNet (as part of Open Multilingual WordNet) took 0.022535324096679688s
Interlinking | Calculation of Degree of Connection for Japanese WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Japanese WordNet (as part of Open Multilingual WordNet) took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for Japanese WordNet (as part of Open Multilingual WordNet) took 6.031990051269531e-05s
Believability | Calculation of trust value for Japanese WordNet (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-jpn took 1.9824864864349365s
Availability | SPARQL endpoint availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 5.1021575927734375e-05s
Availability | VoID file availability check for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0004734992980957031s
Completeness | Calculation of interlinking completeness for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.17870259284973145s
Reputation | Calculation of the PageRank for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.022559165954589844s
Interlinking | Calculation of Degree of Connection for Multilingual Central Repository (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Multilingual Central Repository (as part of Open Multilingual WordNet) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Multilingual Central Repository (as part of Open Multilingual WordNet) took 3.7670135498046875e-05s
Believability | Calculation of trust value for Multilingual Central Repository (as part of Open Multilingual WordNet) took 1.1682510375976562e-05s
INFO | --- Analysis for omwn-mcr took 1.9790198802947998s
Availability | SPARQL endpoint availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-05s
Availability | VoID file availability check for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0004627704620361328s
Completeness | Calculation of interlinking completeness for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.17417383193969727s
Reputation | Calculation of the PageRank for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.020181894302368164s
Interlinking | Calculation of Degree of Connection for Wordnet WordNet (as part of Open Multilingual WordNet) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Wordnet WordNet (as part of Open Multilingual WordNet) took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Wordnet WordNet (as part of Open Multilingual WordNet) took 3.6716461181640625e-05s
Believability | Calculation of trust value for Wordnet WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-msa took 1.985511302947998s
Availability | SPARQL endpoint availability check for Open WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Availability | VoID file availability check for Open WordNet (as part of Open Multilingual WordNet) took 0.0004584789276123047s
Completeness | Calculation of interlinking completeness for Open WordNet (as part of Open Multilingual WordNet) took 0.17342591285705566s
Reputation | Calculation of the PageRank for Open WordNet (as part of Open Multilingual WordNet) took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for Open WordNet (as part of Open Multilingual WordNet) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open WordNet (as part of Open Multilingual WordNet) took 0.0007078647613525391s
Interlinking | Calculation of Clustering coefficient for Open WordNet (as part of Open Multilingual WordNet) took 3.4809112548828125e-05s
Believability | Calculation of trust value for Open WordNet (as part of Open Multilingual WordNet) took 1.1205673217773438e-05s
INFO | --- Analysis for omwn-nld took 1.9612770080566406s
Availability | SPARQL endpoint availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 8.368492126464844e-05s
Availability | VoID file availability check for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.1813039779663086s
Reputation | Calculation of the PageRank for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.02039623260498047s
Interlinking | Calculation of Degree of Connection for Norwegian WordNet (as part of Open Multilingual WordNet) took 7.62939453125e-06s
Interlinking | Calculation of Centrality for Norwegian WordNet (as part of Open Multilingual WordNet) took 0.0007174015045166016s
Interlinking | Calculation of Clustering coefficient for Norwegian WordNet (as part of Open Multilingual WordNet) took 3.5762786865234375e-05s
Believability | Calculation of trust value for Norwegian WordNet (as part of Open Multilingual WordNet) took 1.0728836059570312e-05s
INFO | --- Analysis for omwn-nor took 1.974841594696045s
Availability | SPARQL endpoint availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 8.344650268554688e-05s
Availability | VoID file availability check for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.18583178520202637s
Reputation | Calculation of the PageRank for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.021508216857910156s
Interlinking | Calculation of Degree of Connection for plWordNet WordNet (as part of Open Multilingual WordNet) took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for plWordNet WordNet (as part of Open Multilingual WordNet) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for plWordNet WordNet (as part of Open Multilingual WordNet) took 3.600120544433594e-05s
Believability | Calculation of trust value for plWordNet WordNet (as part of Open Multilingual WordNet) took 1.0251998901367188e-05s
INFO | --- Analysis for omwn-pol took 1.985490322113037s
Availability | SPARQL endpoint availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 4.2438507080078125e-05s
Availability | VoID file availability check for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.17509770393371582s
Reputation | Calculation of the PageRank for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for OpenWN-PT WordNet (as part of Open Multilingual WordNet) took 1.33514404296875e-05s
INFO | --- Analysis for omwn-por took 1.99951171875s
Availability | SPARQL endpoint availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 8.20159912109375e-05s
Availability | VoID file availability check for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Romanian WordNet (as part of Open Multilingual WordNet) took 0.17313098907470703s
Reputation | Calculation of the PageRank for Romanian WordNet (as part of Open Multilingual WordNet) took 0.022053956985473633s
Interlinking | Calculation of Degree of Connection for Romanian WordNet (as part of Open Multilingual WordNet) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Romanian WordNet (as part of Open Multilingual WordNet) took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Romanian WordNet (as part of Open Multilingual WordNet) took 3.790855407714844e-05s
Believability | Calculation of trust value for Romanian WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-ron took 2.014502763748169s
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.0004999637603759766s
Completeness | Calculation of interlinking completeness for Slovak WordNet (as part of Open Multilingual WordNet) took 0.17677521705627441s
Reputation | Calculation of the PageRank for Slovak WordNet (as part of Open Multilingual WordNet) took 0.020429372787475586s
Interlinking | Calculation of Degree of Connection for Slovak WordNet (as part of Open Multilingual WordNet) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Slovak WordNet (as part of Open Multilingual WordNet) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Slovak WordNet (as part of Open Multilingual WordNet) took 3.910064697265625e-05s
Believability | Calculation of trust value for Slovak WordNet (as part of Open Multilingual WordNet) took 1.3589859008789062e-05s
INFO | --- Analysis for omwn-slk took 1.9618630409240723s
Availability | SPARQL endpoint availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 4.0531158447265625e-05s
Availability | VoID file availability check for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0005061626434326172s
Completeness | Calculation of interlinking completeness for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.17266011238098145s
Reputation | Calculation of the PageRank for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.02055215835571289s
Interlinking | Calculation of Degree of Connection for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sloWNet WordNet (as part of Open Multilingual WordNet) took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for sloWNet WordNet (as part of Open Multilingual WordNet) took 3.9577484130859375e-05s
Believability | Calculation of trust value for sloWNet WordNet (as part of Open Multilingual WordNet) took 1.3113021850585938e-05s
INFO | --- Analysis for omwn-slv took 1.9619781970977783s
Availability | SPARQL endpoint availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 8.225440979003906e-05s
Availability | VoID file availability check for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Swedish WordNet (as part of Open Multilingual WordNet) took 0.17194247245788574s
Reputation | Calculation of the PageRank for Swedish WordNet (as part of Open Multilingual WordNet) took 0.020453929901123047s
Interlinking | Calculation of Degree of Connection for Swedish WordNet (as part of Open Multilingual WordNet) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Swedish WordNet (as part of Open Multilingual WordNet) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Swedish WordNet (as part of Open Multilingual WordNet) took 4.029273986816406e-05s
Believability | Calculation of trust value for Swedish WordNet (as part of Open Multilingual WordNet) took 1.2636184692382812e-05s
INFO | --- Analysis for omwn-swe took 1.9737210273742676s
Availability | SPARQL endpoint availability check for Thai WordNet (as part of Open Multilingual WordNet) took 8.249282836914062e-05s
Availability | VoID file availability check for Thai WordNet (as part of Open Multilingual WordNet) took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for Thai WordNet (as part of Open Multilingual WordNet) took 0.18156719207763672s
Reputation | Calculation of the PageRank for Thai WordNet (as part of Open Multilingual WordNet) took 0.020318984985351562s
Interlinking | Calculation of Degree of Connection for Thai WordNet (as part of Open Multilingual WordNet) took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Thai WordNet (as part of Open Multilingual WordNet) took 0.0007333755493164062s
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 1.3113021850585938e-05s
INFO | --- Analysis for omwn-tha took 1.9929141998291016s
Availability | SPARQL endpoint availability check for OntoBeef Domain took 8.559226989746094e-05s
Availability | VoID file availability check for OntoBeef Domain took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for OntoBeef Domain took 0.17345213890075684s
Reputation | Calculation of the PageRank for OntoBeef Domain took 0.020808696746826172s
Interlinking | Calculation of Degree of Connection for OntoBeef Domain took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for OntoBeef Domain took 0.0010097026824951172s
Interlinking | Calculation of Clustering coefficient for OntoBeef Domain took 4.982948303222656e-05s
Believability | Calculation of trust value for OntoBeef Domain took 1.1920928955078125e-05s
INFO | --- Analysis for ontobeef-domain took 1.9801557064056396s
Availability | SPARQL endpoint availability check for Ontos News Portal took 4.0531158447265625e-05s
Availability | VoID file availability check for Ontos News Portal took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Ontos News Portal took 0.17183351516723633s
Reputation | Calculation of the PageRank for Ontos News Portal took 0.02033829689025879s
Interlinking | Calculation of Degree of Connection for Ontos News Portal took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Ontos News Portal took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Ontos News Portal took 8.654594421386719e-05s
Believability | Calculation of trust value for Ontos News Portal took 8.344650268554688e-06s
INFO | --- Analysis for ontos-news-portal took 1.9939415454864502s
Availability | SPARQL endpoint availability check for Ookaboo RDF dump took 9.179115295410156e-05s
Availability | VoID file availability check for Ookaboo RDF dump took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for Ookaboo RDF dump took 0.17180371284484863s
Reputation | Calculation of the PageRank for Ookaboo RDF dump took 0.02039313316345215s
Interlinking | Calculation of Degree of Connection for Ookaboo RDF dump took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Ookaboo RDF dump took 0.0009794235229492188s
Interlinking | Calculation of Clustering coefficient for Ookaboo RDF dump took 3.886222839355469e-05s
Believability | Calculation of trust value for Ookaboo RDF dump took 1.2159347534179688e-05s
INFO | --- Analysis for ookaboo-rdf-dump took 1.9706544876098633s
Availability | SPARQL endpoint availability check for Open Bantu isiXhosa Lexicon took 8.153915405273438e-05s
Availability | VoID file availability check for Open Bantu isiXhosa Lexicon took 0.00030612945556640625s
Completeness | Calculation of interlinking completeness for Open Bantu isiXhosa Lexicon took 0.1731586456298828s
Reputation | Calculation of the PageRank for Open Bantu isiXhosa Lexicon took 0.02046942710876465s
Interlinking | Calculation of Degree of Connection for Open Bantu isiXhosa Lexicon took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Bantu isiXhosa Lexicon took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Open Bantu isiXhosa Lexicon took 3.790855407714844e-05s
Believability | Calculation of trust value for Open Bantu isiXhosa Lexicon took 1.2636184692382812e-05s
INFO | --- Analysis for open-bantu-isixhosa-lexicon took 1.975888729095459s
Availability | SPARQL endpoint availability check for Open Courseware Consortium metadata in RDF took 4.124641418457031e-05s
Availability | VoID file availability check for Open Courseware Consortium metadata in RDF took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for Open Courseware Consortium metadata in RDF took 0.17324614524841309s
Reputation | Calculation of the PageRank for Open Courseware Consortium metadata in RDF took 0.020186424255371094s
Interlinking | Calculation of Degree of Connection for Open Courseware Consortium metadata in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Courseware Consortium metadata in RDF took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Open Courseware Consortium metadata in RDF took 2.765655517578125e-05s
Believability | Calculation of trust value for Open Courseware Consortium metadata in RDF took 1.239776611328125e-05s
INFO | --- Analysis for open-courseware-consortium-metadata-in-rdf took 1.9687178134918213s
Availability | SPARQL endpoint availability check for Open Data Euskadi took 4.076957702636719e-05s
Availability | VoID file availability check for Open Data Euskadi took 0.0002694129943847656s
Completeness | Calculation of interlinking completeness for Open Data Euskadi took 0.1840226650238037s
Reputation | Calculation of the PageRank for Open Data Euskadi took 0.020216703414916992s
Interlinking | Calculation of Degree of Connection for Open Data Euskadi took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Open Data Euskadi took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for Open Data Euskadi took 4.3392181396484375e-05s
Believability | Calculation of trust value for Open Data Euskadi took 6.198883056640625e-06s
INFO | --- Analysis for open-data-euskadi took 2.0095393657684326s
Availability | SPARQL endpoint availability check for Open Data RISP, the Spanish Open Data community took 3.933906555175781e-05s
Availability | VoID file availability check for Open Data RISP, the Spanish Open Data community took 0.00021767616271972656s
Completeness | Calculation of interlinking completeness for Open Data RISP, the Spanish Open Data community took 0.18369364738464355s
Reputation | Calculation of the PageRank for Open Data RISP, the Spanish Open Data community took 0.020151376724243164s
Interlinking | Calculation of Degree of Connection for Open Data RISP, the Spanish Open Data community took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data RISP, the Spanish Open Data community took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Open Data RISP, the Spanish Open Data community took 9.751319885253906e-05s
Believability | Calculation of trust value for Open Data RISP, the Spanish Open Data community took 7.152557373046875e-06s
INFO | --- Analysis for open-data-risp took 1.9420301914215088s
Availability | SPARQL endpoint availability check for Open Data Thesaurus took 4.124641418457031e-05s
Availability | VoID file availability check for Open Data Thesaurus took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Open Data Thesaurus took 0.19610309600830078s
Reputation | Calculation of the PageRank for Open Data Thesaurus took 0.020486831665039062s
Interlinking | Calculation of Degree of Connection for Open Data Thesaurus took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Open Data Thesaurus took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Open Data Thesaurus took 7.295608520507812e-05s
Believability | Calculation of trust value for Open Data Thesaurus took 1.3113021850585938e-05s
INFO | --- Analysis for open-data-thesaurus took 1.9961705207824707s
Availability | SPARQL endpoint availability check for Open Data @ Tor Vergata took 8.273124694824219e-05s
Availability | VoID file availability check for Open Data @ Tor Vergata took 0.0005092620849609375s
Completeness | Calculation of interlinking completeness for Open Data @ Tor Vergata took 0.17458009719848633s
Reputation | Calculation of the PageRank for Open Data @ Tor Vergata took 0.020165681838989258s
Interlinking | Calculation of Degree of Connection for Open Data @ Tor Vergata took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Open Data @ Tor Vergata took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Open Data @ Tor Vergata took 2.9325485229492188e-05s
Believability | Calculation of trust value for Open Data @ Tor Vergata took 1.2159347534179688e-05s
INFO | --- Analysis for open-data-tor-vergata took 1.9611475467681885s
Availability | SPARQL endpoint availability check for Open Election Data Project took 5.936622619628906e-05s
Availability | VoID file availability check for Open Election Data Project took 0.0004944801330566406s
Completeness | Calculation of interlinking completeness for Open Election Data Project took 0.19114279747009277s
Reputation | Calculation of the PageRank for Open Election Data Project took 0.020388364791870117s
Interlinking | Calculation of Degree of Connection for Open Election Data Project took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Open Election Data Project took 0.0009095668792724609s
Interlinking | Calculation of Clustering coefficient for Open Election Data Project took 7.43865966796875e-05s
Believability | Calculation of trust value for Open Election Data Project took 1.1682510375976562e-05s
INFO | --- Analysis for open-election-data-project took 1.9933981895446777s
Availability | SPARQL endpoint availability check for OpenEI - Open Energy Info took 3.9577484130859375e-05s
Availability | VoID file availability check for OpenEI - Open Energy Info took 0.0005817413330078125s
Completeness | Calculation of interlinking completeness for OpenEI - Open Energy Info took 0.18360090255737305s
Reputation | Calculation of the PageRank for OpenEI - Open Energy Info took 0.020058393478393555s
Interlinking | Calculation of Degree of Connection for OpenEI - Open Energy Info took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for OpenEI - Open Energy Info took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for OpenEI - Open Energy Info took 8.153915405273438e-05s
Believability | Calculation of trust value for OpenEI - Open Energy Info took 1.2636184692382812e-05s
INFO | --- Analysis for open-energy-info-wiki took 2.0046982765197754s
Availability | SPARQL endpoint availability check for Open Library took 4.172325134277344e-05s
Availability | VoID file availability check for Open Library took 0.00048351287841796875s
Completeness | Calculation of interlinking completeness for Open Library took 0.17309165000915527s
Reputation | Calculation of the PageRank for Open Library took 0.021717309951782227s
Interlinking | Calculation of Degree of Connection for Open Library took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Open Library took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Open Library took 6.580352783203125e-05s
Believability | Calculation of trust value for Open Library took 1.239776611328125e-05s
INFO | --- Analysis for open-library took 1.990490436553955s
Availability | SPARQL endpoint availability check for Open Directory took 8.58306884765625e-05s
Availability | VoID file availability check for Open Directory took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for Open Directory took 0.17239832878112793s
Reputation | Calculation of the PageRank for Open Directory took 0.020330190658569336s
Interlinking | Calculation of Degree of Connection for Open Directory took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Open Directory took 0.0009202957153320312s
Interlinking | Calculation of Clustering coefficient for Open Directory took 3.314018249511719e-05s
Believability | Calculation of trust value for Open Directory took 1.2159347534179688e-05s
INFO | --- Analysis for open_directory took 1.986252784729004s
Availability | SPARQL endpoint availability check for Open Land Use @PSNC took 8.535385131835938e-05s
Availability | VoID file availability check for Open Land Use @PSNC took 0.0005269050598144531s
Completeness | Calculation of interlinking completeness for Open Land Use @PSNC took 0.17977309226989746s
Reputation | Calculation of the PageRank for Open Land Use @PSNC took 0.021834611892700195s
Interlinking | Calculation of Degree of Connection for Open Land Use @PSNC took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Land Use @PSNC took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Open Land Use @PSNC took 2.7894973754882812e-05s
Believability | Calculation of trust value for Open Land Use @PSNC took 1.5497207641601562e-05s
INFO | --- Analysis for Open_Land_Use took 1.990990161895752s
Availability | SPARQL endpoint availability check for flyatlas took 9.870529174804688e-05s
Availability | VoID file availability check for flyatlas took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for flyatlas took 0.17551660537719727s
Reputation | Calculation of the PageRank for flyatlas took 0.020182371139526367s
Interlinking | Calculation of Degree of Connection for flyatlas took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for flyatlas took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for flyatlas took 2.6464462280273438e-05s
Believability | Calculation of trust value for flyatlas took 7.62939453125e-06s
INFO | --- Analysis for openbiomed-flyatlas took 1.9966912269592285s
Availability | SPARQL endpoint availability check for OpenCalais took 8.630752563476562e-05s
Availability | VoID file availability check for OpenCalais took 0.000492095947265625s
Completeness | Calculation of interlinking completeness for OpenCalais took 0.18352198600769043s
Reputation | Calculation of the PageRank for OpenCalais took 0.020122528076171875s
Interlinking | Calculation of Degree of Connection for OpenCalais took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenCalais took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for OpenCalais took 0.00010418891906738281s
Believability | Calculation of trust value for OpenCalais took 1.2636184692382812e-05s
INFO | --- Analysis for opencalais took 2.0178515911102295s
Availability | SPARQL endpoint availability check for OpenCorporates - The Open Database Of The Corporate World took 8.034706115722656e-05s
Availability | VoID file availability check for OpenCorporates - The Open Database Of The Corporate World took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for OpenCorporates - The Open Database Of The Corporate World took 0.17819833755493164s
Reputation | Calculation of the PageRank for OpenCorporates - The Open Database Of The Corporate World took 0.020441532135009766s
Interlinking | Calculation of Degree of Connection for OpenCorporates - The Open Database Of The Corporate World took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for OpenCorporates - The Open Database Of The Corporate World took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for OpenCorporates - The Open Database Of The Corporate World took 7.2479248046875e-05s
Believability | Calculation of trust value for OpenCorporates - The Open Database Of The Corporate World took 1.33514404296875e-05s
INFO | --- Analysis for opencorporates took 1.9817392826080322s
Availability | SPARQL endpoint availability check for OpenCyc took 8.463859558105469e-05s
Availability | VoID file availability check for OpenCyc took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for OpenCyc took 0.180189847946167s
Reputation | Calculation of the PageRank for OpenCyc took 0.02071523666381836s
Interlinking | Calculation of Degree of Connection for OpenCyc took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for OpenCyc took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for OpenCyc took 0.000102996826171875s
Believability | Calculation of trust value for OpenCyc took 1.2874603271484375e-05s
INFO | --- Analysis for opencyc took 1.967797040939331s
Availability | SPARQL endpoint availability check for opendatacommunities-dev-local-authority-services took 8.559226989746094e-05s
Availability | VoID file availability check for opendatacommunities-dev-local-authority-services took 0.00024962425231933594s
Completeness | Calculation of interlinking completeness for opendatacommunities-dev-local-authority-services took 0.17148399353027344s
Reputation | Calculation of the PageRank for opendatacommunities-dev-local-authority-services took 0.020095348358154297s
Interlinking | Calculation of Degree of Connection for opendatacommunities-dev-local-authority-services took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-dev-local-authority-services took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-dev-local-authority-services took 3.170967102050781e-05s
Believability | Calculation of trust value for opendatacommunities-dev-local-authority-services took 6.9141387939453125e-06s
INFO | --- Analysis for opendatacommunities-dev-local-authority-services took 1.9421803951263428s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-acceptances-per-1000 took 4.315376281738281e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-acceptances-per-1000 took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-acceptances-per-1000 took 0.1789100170135498s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-acceptances-per-1000 took 0.02024531364440918s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-acceptances-per-1000 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-acceptances-per-1000 took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-acceptances-per-1000 took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-acceptances-per-1000 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-homelessness-acceptances-per-1000 took 1.951406717300415s
Availability | SPARQL endpoint availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 5.3882598876953125e-05s
Availability | VoID file availability check for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.18398737907409668s
Reputation | Calculation of the PageRank for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0200350284576416s
Interlinking | Calculation of Degree of Connection for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 3.695487976074219e-05s
Believability | Calculation of trust value for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 1.2636184692382812e-05s
INFO | --- Analysis for opendatacommunities-homelessness-households-accommodated-temporary-housing-types took 2.0088586807250977s
Availability | SPARQL endpoint availability check for opendatacommunities-households-2008 took 8.440017700195312e-05s
Availability | VoID file availability check for opendatacommunities-households-2008 took 0.0004863739013671875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-2008 took 0.18498015403747559s
Reputation | Calculation of the PageRank for opendatacommunities-households-2008 took 0.02017688751220703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-2008 took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-2008 took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-2008 took 3.647804260253906e-05s
Believability | Calculation of trust value for opendatacommunities-households-2008 took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-households-2008 took 1.9618937969207764s
Availability | SPARQL endpoint availability check for opendatacommunities-households-accommodated-per-1000 took 8.440017700195312e-05s
Availability | VoID file availability check for opendatacommunities-households-accommodated-per-1000 took 0.00024580955505371094s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-accommodated-per-1000 took 0.19795775413513184s
Reputation | Calculation of the PageRank for opendatacommunities-households-accommodated-per-1000 took 0.022914409637451172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-accommodated-per-1000 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-accommodated-per-1000 took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-accommodated-per-1000 took 3.4809112548828125e-05s
Believability | Calculation of trust value for opendatacommunities-households-accommodated-per-1000 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-households-accommodated-per-1000 took 1.9969828128814697s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-population took 3.9577484130859375e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-population took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-population took 0.17489266395568848s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-population took 0.020281076431274414s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-population took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-population took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-population took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-population took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-households-projections-population took 1.958272933959961s
Availability | SPARQL endpoint availability check for opendatacommunities-households-projections-totalhouseolds took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-households-projections-totalhouseolds took 0.0005161762237548828s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-projections-totalhouseolds took 0.1706397533416748s
Reputation | Calculation of the PageRank for opendatacommunities-households-projections-totalhouseolds took 0.02038264274597168s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-projections-totalhouseolds took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-projections-totalhouseolds took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-projections-totalhouseolds took 3.910064697265625e-05s
Believability | Calculation of trust value for opendatacommunities-households-projections-totalhouseolds took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-households-projections-totalhouseolds took 1.964233636856079s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.910064697265625e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.24741697311401367s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.020374059677124023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-household-composition took 2.093226671218872s
Availability | SPARQL endpoint availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 8.106231689453125e-05s
Availability | VoID file availability check for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.00048828125s
Completeness | Calculation of interlinking completeness for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.17604660987854004s
Reputation | Calculation of the PageRank for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.021365880966186523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 3.9577484130859375e-05s
Believability | Calculation of trust value for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-households-social-lettings-general-needs-lettings-prp-number-bedrooms took 1.998119831085205s
Availability | SPARQL endpoint availability check for opendatacommunities-housing-market took 8.463859558105469e-05s
Availability | VoID file availability check for opendatacommunities-housing-market took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for opendatacommunities-housing-market took 0.18696093559265137s
Reputation | Calculation of the PageRank for opendatacommunities-housing-market took 0.02059793472290039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-housing-market took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-housing-market took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-housing-market took 4.029273986816406e-05s
Believability | Calculation of trust value for opendatacommunities-housing-market took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-housing-market took 2.024284839630127s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-crime-rank-2010 took 4.1484832763671875e-05s
Availability | VoID file availability check for opendatacommunities-imd-crime-rank-2010 took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-crime-rank-2010 took 0.18898463249206543s
Reputation | Calculation of the PageRank for opendatacommunities-imd-crime-rank-2010 took 0.021930217742919922s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-crime-rank-2010 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-imd-crime-rank-2010 took 0.0011074542999267578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-crime-rank-2010 took 4.863739013671875e-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 1.9824097156524658s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-environment-rank-2010 took 8.916854858398438e-05s
Availability | VoID file availability check for opendatacommunities-imd-environment-rank-2010 took 0.00020360946655273438s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-environment-rank-2010 took 0.1897740364074707s
Reputation | Calculation of the PageRank for opendatacommunities-imd-environment-rank-2010 took 0.020189762115478516s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-environment-rank-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-environment-rank-2010 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-environment-rank-2010 took 3.7670135498046875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-environment-rank-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-imd-environment-rank-2010 took 1.9819612503051758s
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.000240325927734375s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-income-rank-la-2010 took 0.17261767387390137s
Reputation | Calculation of the PageRank for opendatacommunities-imd-income-rank-la-2010 took 0.020053625106811523s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-income-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-income-rank-la-2010 took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-income-rank-la-2010 took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-imd-income-rank-la-2010 took 6.198883056640625e-06s
INFO | --- Analysis for opendatacommunities-imd-income-rank-la-2010 took 1.9040396213531494s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-rank-2010 took 3.886222839355469e-05s
Availability | VoID file availability check for opendatacommunities-imd-rank-2010 took 0.0002162456512451172s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-rank-2010 took 0.1739189624786377s
Reputation | Calculation of the PageRank for opendatacommunities-imd-rank-2010 took 0.020102262496948242s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-rank-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-rank-2010 took 0.0007455348968505859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-imd-rank-2010 took 4.100799560546875e-05s
Believability | Calculation of trust value for opendatacommunities-imd-rank-2010 took 7.152557373046875e-06s
INFO | --- Analysis for opendatacommunities-imd-rank-2010 took 2.061866283416748s
Availability | SPARQL endpoint availability check for opendatacommunities-imd-score-2010 took 4.4345855712890625e-05s
Availability | VoID file availability check for opendatacommunities-imd-score-2010 took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for opendatacommunities-imd-score-2010 took 0.17001557350158691s
Reputation | Calculation of the PageRank for opendatacommunities-imd-score-2010 took 0.02028822898864746s
Interlinking | Calculation of Degree of Connection for opendatacommunities-imd-score-2010 took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-imd-score-2010 took 0.0007698535919189453s
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.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-imd-score-2010 took 1.9240221977233887s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 3.886222839355469e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-affordable-housing-starts took 0.00021529197692871094s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-affordable-housing-starts took 0.16948199272155762s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-affordable-housing-starts took 0.020215988159179688s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-affordable-housing-starts took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-affordable-housing-starts took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-affordable-housing-starts took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-affordable-housing-starts took 6.67572021484375e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-affordable-housing-starts took 1.9091312885284424s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0002570152282714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.17600393295288086s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0202178955078125s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-energy-efficiency-new-builds took 1.9224276542663574s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-housing-starts took 3.8623809814453125e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-housing-starts took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-housing-starts took 0.17004919052124023s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-housing-starts took 0.020092487335205078s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-housing-starts took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-housing-starts took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-housing-starts took 4.029273986816406e-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 1.922677755355835s
Availability | SPARQL endpoint availability check for opendatacommunities-impact-indicators-planning-applications-granted took 8.273124694824219e-05s
Availability | VoID file availability check for opendatacommunities-impact-indicators-planning-applications-granted took 0.0002460479736328125s
Completeness | Calculation of interlinking completeness for opendatacommunities-impact-indicators-planning-applications-granted took 0.18030500411987305s
Reputation | Calculation of the PageRank for opendatacommunities-impact-indicators-planning-applications-granted took 0.02026534080505371s
Interlinking | Calculation of Degree of Connection for opendatacommunities-impact-indicators-planning-applications-granted took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for opendatacommunities-impact-indicators-planning-applications-granted took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-impact-indicators-planning-applications-granted took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-impact-indicators-planning-applications-granted took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-impact-indicators-planning-applications-granted took 1.9202167987823486s
Availability | SPARQL endpoint availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 3.8623809814453125e-05s
Availability | VoID file availability check for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.00021576881408691406s
Completeness | Calculation of interlinking completeness for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.17422199249267578s
Reputation | Calculation of the PageRank for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.02020716667175293s
Interlinking | Calculation of Degree of Connection for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 5.7220458984375e-06s
INFO | --- Analysis for opendatacommunities-input-indicators-local-authority-funding-from-government-grant took 1.9385340213775635s
Availability | SPARQL endpoint availability check for opendatacommunities-net-additional-dwellings took 3.9577484130859375e-05s
Availability | VoID file availability check for opendatacommunities-net-additional-dwellings took 0.0002627372741699219s
Completeness | Calculation of interlinking completeness for opendatacommunities-net-additional-dwellings took 0.17570185661315918s
Reputation | Calculation of the PageRank for opendatacommunities-net-additional-dwellings took 0.0201413631439209s
Interlinking | Calculation of Degree of Connection for opendatacommunities-net-additional-dwellings took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-net-additional-dwellings took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-net-additional-dwellings took 3.719329833984375e-05s
Believability | Calculation of trust value for opendatacommunities-net-additional-dwellings took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-net-additional-dwellings took 1.9749786853790283s
Availability | SPARQL endpoint availability check for opendatacommunities-service-expenditure took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-service-expenditure took 0.00047779083251953125s
Completeness | Calculation of interlinking completeness for opendatacommunities-service-expenditure took 0.20262789726257324s
Reputation | Calculation of the PageRank for opendatacommunities-service-expenditure took 0.02069234848022461s
Interlinking | Calculation of Degree of Connection for opendatacommunities-service-expenditure took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-service-expenditure took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-service-expenditure took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-service-expenditure took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-service-expenditure took 2.0498549938201904s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.100799560546875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.20123577117919922s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.020209074020385742s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 4.2438507080078125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 1.1205673217773438e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-education-rank-la-2010 took 2.0133609771728516s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 5.221366882324219e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.18044710159301758s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.020173311233520508s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 1.239776611328125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-rank-la-2010 took 2.002284288406372s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 3.933906555175781e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0004622936248779297s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.18314099311828613s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.02257513999938965s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 5.507469177246094e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-employment-score-2010 took 2.080193519592285s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 9.822845458984375e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.000522613525390625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.18451738357543945s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.020190954208374023s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-rank-la-2010 took 2.1046688556671143s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 8.344650268554688e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.000545501708984375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.18020415306091309s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.022038936614990234s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 0.0008380413055419922s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 5.030632019042969e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 7.62939453125e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-health-score-2010 took 1.992027997970581s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 3.981590270996094e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.000270843505859375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.1739826202392578s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.020235776901245117s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 0.0007448196411132812s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.0967254638671875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-housing-rank-la-2010 took 1.9603679180145264s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 3.886222839355469e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.000560760498046875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.18322157859802246s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.020520448684692383s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 5.14984130859375e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.049041748046875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-income-rank-la-2010 took 1.985626220703125s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.249282836914062e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.00043010711669921875s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.17503595352172852s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.020716190338134766s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 4.220008850097656e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 1.1920928955078125e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2007 took 2.018533706665039s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 4.57763671875e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0004374980926513672s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.17487597465515137s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.020123958587646484s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 3.790855407714844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-2010 took 2.028322458267212s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 8.702278137207031e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.17277884483337402s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.02023482322692871s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 4.553794860839844e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-rank-la-2010 took 2.177309274673462s
Availability | SPARQL endpoint availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.17267274856567383s
Reputation | Calculation of the PageRank for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 4.506111145019531e-05s
Believability | Calculation of trust value for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-societal-wellbeing-deprivation-imd-score-2010 took 1.9484577178955078s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 7.939338684082031e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.17725658416748047s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.020228862762451172s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-affordable-housing-starts took 1.9542567729949951s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 3.933906555175781e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0002243518829345703s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.1750044822692871s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0202486515045166s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 4.291534423828125e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 9.059906005859375e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-households-in-temporary-accommodation took 1.9300017356872559s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 3.9577484130859375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0002143383026123047s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-housing-starts took 0.16975855827331543s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-housing-starts took 0.02011585235595703s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-housing-starts took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-housing-starts took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-housing-starts took 4.458427429199219e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-housing-starts took 5.9604644775390625e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-housing-starts took 1.942842960357666s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.1699213981628418s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.020134449005126953s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 4.076957702636719e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.1682510375976562e-05s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-neighbourhood-plans took 1.9348394870758057s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 4.076957702636719e-05s
Availability | VoID file availability check for opendatacommunities-transparency-impact-indicators-troubled-families took 0.000213623046875s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-impact-indicators-troubled-families took 0.17923235893249512s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-impact-indicators-troubled-families took 0.020125150680541992s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-impact-indicators-troubled-families took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-impact-indicators-troubled-families took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-impact-indicators-troubled-families took 4.124641418457031e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-impact-indicators-troubled-families took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-transparency-impact-indicators-troubled-families took 1.943326711654663s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 3.9577484130859375e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.00021791458129882812s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.18718791007995605s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.02023172378540039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 4.00543212890625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 6.4373016357421875e-06s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authorities-working-with-troubled-families took 1.9718339443206787s
Availability | SPARQL endpoint availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.00543212890625e-05s
Availability | VoID file availability check for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0005941390991210938s
Completeness | Calculation of interlinking completeness for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.19161033630371094s
Reputation | Calculation of the PageRank for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.020203590393066406s
Interlinking | Calculation of Degree of Connection for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 4.8160552978515625e-05s
Believability | Calculation of trust value for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.0251998901367188e-05s
INFO | --- Analysis for opendatacommunities-transparency-input-indicators-local-authority-funding-from-government-grant took 1.979003667831421s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 8.392333984375e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.17442059516906738s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.0728836059570312e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-happy-yesterday-standard-deviation took 1.9578289985656738s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 8.416175842285156e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.1849813461303711s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.02023172378540039s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 3.838539123535156e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.1444091796875e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-lsoa-happy-yesterday-mean took 1.9847042560577393s
Availability | SPARQL endpoint availability check for opendatacommunities-wellbeing-worthwhile-mean took 3.981590270996094e-05s
Availability | VoID file availability check for opendatacommunities-wellbeing-worthwhile-mean took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for opendatacommunities-wellbeing-worthwhile-mean took 0.18108773231506348s
Reputation | Calculation of the PageRank for opendatacommunities-wellbeing-worthwhile-mean took 0.02064037322998047s
Interlinking | Calculation of Degree of Connection for opendatacommunities-wellbeing-worthwhile-mean took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for opendatacommunities-wellbeing-worthwhile-mean took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for opendatacommunities-wellbeing-worthwhile-mean took 3.814697265625e-05s
Believability | Calculation of trust value for opendatacommunities-wellbeing-worthwhile-mean took 1.2159347534179688e-05s
INFO | --- Analysis for opendatacommunities-wellbeing-worthwhile-mean took 1.9705920219421387s
Availability | SPARQL endpoint availability check for Open Data of Ecuador took 8.320808410644531e-05s
Availability | VoID file availability check for Open Data of Ecuador took 0.000446319580078125s
Completeness | Calculation of interlinking completeness for Open Data of Ecuador took 0.20293760299682617s
Reputation | Calculation of the PageRank for Open Data of Ecuador took 0.0208432674407959s
Interlinking | Calculation of Degree of Connection for Open Data of Ecuador took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Open Data of Ecuador took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Open Data of Ecuador took 8.988380432128906e-05s
Believability | Calculation of trust value for Open Data of Ecuador took 1.0967254638671875e-05s
INFO | --- Analysis for opendataec took 1.9961788654327393s
Availability | SPARQL endpoint availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 7.987022399902344e-05s
Availability | VoID file availability check for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.17940855026245117s
Reputation | Calculation of the PageRank for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.02047133445739746s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-education-pupils-by-school-and-datazone took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-education-pupils-by-school-and-datazone took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-education-pupils-by-school-and-datazone took 4.0531158447265625e-05s
Believability | Calculation of trust value for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.1444091796875e-05s
INFO | --- Analysis for opendatascotland-graph-education-pupils-by-school-and-datazone took 1.9856114387512207s
Availability | SPARQL endpoint availability check for opendatascotland-graph-simd-rank took 8.177757263183594e-05s
Availability | VoID file availability check for opendatascotland-graph-simd-rank took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for opendatascotland-graph-simd-rank took 0.1871788501739502s
Reputation | Calculation of the PageRank for opendatascotland-graph-simd-rank took 0.021645784378051758s
Interlinking | Calculation of Degree of Connection for opendatascotland-graph-simd-rank took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for opendatascotland-graph-simd-rank took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for opendatascotland-graph-simd-rank took 3.933906555175781e-05s
Believability | Calculation of trust value for opendatascotland-graph-simd-rank took 1.239776611328125e-05s
INFO | --- Analysis for opendatascotland-graph-simd-rank took 2.080864429473877s
Availability | SPARQL endpoint availability check for opendatascotland-simd-crime-rank took 8.296966552734375e-05s
Availability | VoID file availability check for opendatascotland-simd-crime-rank took 0.0004620552062988281s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-crime-rank took 0.17382550239562988s
Reputation | Calculation of the PageRank for opendatascotland-simd-crime-rank took 0.020594358444213867s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-crime-rank took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for opendatascotland-simd-crime-rank took 0.0007355213165283203s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-crime-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-simd-crime-rank took 1.2874603271484375e-05s
INFO | --- Analysis for opendatascotland-simd-crime-rank took 1.9539978504180908s
Availability | SPARQL endpoint availability check for opendatascotland-simd-education-rank took 4.100799560546875e-05s
Availability | VoID file availability check for opendatascotland-simd-education-rank took 0.00045609474182128906s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-education-rank took 0.18318772315979004s
Reputation | Calculation of the PageRank for opendatascotland-simd-education-rank took 0.02045893669128418s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-education-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-education-rank took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-education-rank took 3.8623809814453125e-05s
Believability | Calculation of trust value for opendatascotland-simd-education-rank took 1.3113021850585938e-05s
INFO | --- Analysis for opendatascotland-simd-education-rank took 1.9957122802734375s
Availability | SPARQL endpoint availability check for opendatascotland-simd-employment-rank took 4.100799560546875e-05s
Availability | VoID file availability check for opendatascotland-simd-employment-rank took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-employment-rank took 0.1839921474456787s
Reputation | Calculation of the PageRank for opendatascotland-simd-employment-rank took 0.02052021026611328s
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.0008611679077148438s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-employment-rank took 4.38690185546875e-05s
Believability | Calculation of trust value for opendatascotland-simd-employment-rank took 1.2636184692382812e-05s
INFO | --- Analysis for opendatascotland-simd-employment-rank took 1.9740335941314697s
Availability | SPARQL endpoint availability check for opendatascotland-simd-geographic-access-rank took 0.00011706352233886719s
Availability | VoID file availability check for opendatascotland-simd-geographic-access-rank took 0.0004968643188476562s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-geographic-access-rank took 0.18436765670776367s
Reputation | Calculation of the PageRank for opendatascotland-simd-geographic-access-rank took 0.020451784133911133s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-geographic-access-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-geographic-access-rank took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-geographic-access-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-simd-geographic-access-rank took 1.1920928955078125e-05s
INFO | --- Analysis for opendatascotland-simd-geographic-access-rank took 2.0087718963623047s
Availability | SPARQL endpoint availability check for opendatascotland-simd-health-rank took 7.891654968261719e-05s
Availability | VoID file availability check for opendatascotland-simd-health-rank took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-health-rank took 0.1797647476196289s
Reputation | Calculation of the PageRank for opendatascotland-simd-health-rank took 0.020895004272460938s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-health-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-health-rank took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-health-rank took 3.814697265625e-05s
Believability | Calculation of trust value for opendatascotland-simd-health-rank took 1.0967254638671875e-05s
INFO | --- Analysis for opendatascotland-simd-health-rank took 2.024834156036377s
Availability | SPARQL endpoint availability check for opendatascotland-simd-housing-rank took 8.606910705566406e-05s
Availability | VoID file availability check for opendatascotland-simd-housing-rank took 0.0004436969757080078s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-housing-rank took 0.18489313125610352s
Reputation | Calculation of the PageRank for opendatascotland-simd-housing-rank took 0.022333145141601562s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-housing-rank took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-housing-rank took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-housing-rank took 4.172325134277344e-05s
Believability | Calculation of trust value for opendatascotland-simd-housing-rank took 1.1205673217773438e-05s
INFO | --- Analysis for opendatascotland-simd-housing-rank took 1.9781200885772705s
Availability | SPARQL endpoint availability check for opendatascotland-simd-income-rank took 8.58306884765625e-05s
Availability | VoID file availability check for opendatascotland-simd-income-rank took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for opendatascotland-simd-income-rank took 0.17698121070861816s
Reputation | Calculation of the PageRank for opendatascotland-simd-income-rank took 0.020935535430908203s
Interlinking | Calculation of Degree of Connection for opendatascotland-simd-income-rank took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for opendatascotland-simd-income-rank took 0.0007433891296386719s
Interlinking | Calculation of Clustering coefficient for opendatascotland-simd-income-rank took 3.981590270996094e-05s
Believability | Calculation of trust value for opendatascotland-simd-income-rank took 7.3909759521484375e-06s
INFO | --- Analysis for opendatascotland-simd-income-rank took 2.0111193656921387s
Availability | SPARQL endpoint availability check for OpenLink Software LOD Cache took 8.463859558105469e-05s
Availability | VoID file availability check for OpenLink Software LOD Cache took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for OpenLink Software LOD Cache took 0.17503762245178223s
Reputation | Calculation of the PageRank for OpenLink Software LOD Cache took 0.022289037704467773s
Interlinking | Calculation of Degree of Connection for OpenLink Software LOD Cache took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for OpenLink Software LOD Cache took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for OpenLink Software LOD Cache took 3.0517578125e-05s
Believability | Calculation of trust value for OpenLink Software LOD Cache took 1.1682510375976562e-05s
INFO | --- Analysis for openlink-lod-cache took 1.9748764038085938s
Availability | SPARQL endpoint availability check for openlinksw dataspaces took 8.344650268554688e-05s
Availability | VoID file availability check for openlinksw dataspaces took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for openlinksw dataspaces took 0.18612146377563477s
Reputation | Calculation of the PageRank for openlinksw dataspaces took 0.020615816116333008s
Interlinking | Calculation of Degree of Connection for openlinksw dataspaces took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for openlinksw dataspaces took 0.00074005126953125s
Interlinking | Calculation of Clustering coefficient for openlinksw dataspaces took 9.369850158691406e-05s
Believability | Calculation of trust value for openlinksw dataspaces took 1.2636184692382812e-05s
INFO | --- Analysis for openlinksw-dataspaces took 2.0121312141418457s
Availability | SPARQL endpoint availability check for Openly Local :: Making Local Government More Transparent took 8.440017700195312e-05s
Availability | VoID file availability check for Openly Local :: Making Local Government More Transparent took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for Openly Local :: Making Local Government More Transparent took 0.1849226951599121s
Reputation | Calculation of the PageRank for Openly Local :: Making Local Government More Transparent took 0.020560503005981445s
Interlinking | Calculation of Degree of Connection for Openly Local :: Making Local Government More Transparent took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Openly Local :: Making Local Government More Transparent took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Openly Local :: Making Local Government More Transparent took 9.34600830078125e-05s
Believability | Calculation of trust value for Openly Local :: Making Local Government More Transparent took 1.239776611328125e-05s
INFO | --- Analysis for openlylocal took 1.996211051940918s
Availability | SPARQL endpoint availability check for OpenMobileNetwork took 8.225440979003906e-05s
Availability | VoID file availability check for OpenMobileNetwork took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for OpenMobileNetwork took 0.18273019790649414s
Reputation | Calculation of the PageRank for OpenMobileNetwork took 0.02033710479736328s
Interlinking | Calculation of Degree of Connection for OpenMobileNetwork took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for OpenMobileNetwork took 0.0007491111755371094s
Interlinking | Calculation of Clustering coefficient for OpenMobileNetwork took 7.224082946777344e-05s
Believability | Calculation of trust value for OpenMobileNetwork took 1.1920928955078125e-05s
INFO | --- Analysis for openmobilenetwork took 1.9804563522338867s
Availability | SPARQL endpoint availability check for OpenTox took 8.249282836914062e-05s
Availability | VoID file availability check for OpenTox took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for OpenTox took 0.1871473789215088s
Reputation | Calculation of the PageRank for OpenTox took 0.020805835723876953s
Interlinking | Calculation of Degree of Connection for OpenTox took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for OpenTox took 0.0007636547088623047s
Interlinking | Calculation of Clustering coefficient for OpenTox took 3.147125244140625e-05s
Believability | Calculation of trust value for OpenTox took 1.3828277587890625e-05s
INFO | --- Analysis for opentox took 1.9820902347564697s
Availability | SPARQL endpoint availability check for OpenUpLabs Datasets took 3.981590270996094e-05s
Availability | VoID file availability check for OpenUpLabs Datasets took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for OpenUpLabs Datasets took 0.17651987075805664s
Reputation | Calculation of the PageRank for OpenUpLabs Datasets took 0.0204160213470459s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Datasets took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Datasets took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Datasets took 3.0517578125e-05s
Believability | Calculation of trust value for OpenUpLabs Datasets took 1.049041748046875e-05s
INFO | --- Analysis for openuplabs took 1.9645390510559082s
Availability | SPARQL endpoint availability check for OPUS - an open source parallel corpus took 8.225440979003906e-05s
Availability | VoID file availability check for OPUS - an open source parallel corpus took 0.0004246234893798828s
Completeness | Calculation of interlinking completeness for OPUS - an open source parallel corpus took 0.18255352973937988s
Reputation | Calculation of the PageRank for OPUS - an open source parallel corpus took 0.020453214645385742s
Interlinking | Calculation of Degree of Connection for OPUS - an open source parallel corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OPUS - an open source parallel corpus took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for OPUS - an open source parallel corpus took 3.170967102050781e-05s
Believability | Calculation of trust value for OPUS - an open source parallel corpus took 1.0251998901367188e-05s
INFO | --- Analysis for opus took 1.9893319606781006s
Availability | SPARQL endpoint availability check for ORCID Connecting Research and Researchers took 8.082389831542969e-05s
Availability | VoID file availability check for ORCID Connecting Research and Researchers took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for ORCID Connecting Research and Researchers took 0.181976318359375s
Reputation | Calculation of the PageRank for ORCID Connecting Research and Researchers took 0.020564556121826172s
Interlinking | Calculation of Degree of Connection for ORCID Connecting Research and Researchers took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ORCID Connecting Research and Researchers took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for ORCID Connecting Research and Researchers took 3.719329833984375e-05s
Believability | Calculation of trust value for ORCID Connecting Research and Researchers took 1.0728836059570312e-05s
INFO | --- Analysis for orcid took 1.9819281101226807s
Availability | SPARQL endpoint availability check for Ordnance Survey Linked Data took 0.00012183189392089844s
Availability | VoID file availability check for Ordnance Survey Linked Data took 0.0006394386291503906s
Completeness | Calculation of interlinking completeness for Ordnance Survey Linked Data took 0.25475096702575684s
Reputation | Calculation of the PageRank for Ordnance Survey Linked Data took 0.020470619201660156s
Interlinking | Calculation of Degree of Connection for Ordnance Survey Linked Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ordnance Survey Linked Data took 0.0007269382476806641s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey Linked Data took 9.632110595703125e-05s
Believability | Calculation of trust value for Ordnance Survey Linked Data took 8.106231689453125e-06s
INFO | --- Analysis for ordnance-survey-linked-data took 2.0931901931762695s
Availability | SPARQL endpoint availability check for oreilly took 8.296966552734375e-05s
Availability | VoID file availability check for oreilly took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for oreilly took 0.18095135688781738s
Reputation | Calculation of the PageRank for oreilly took 0.022266149520874023s
Interlinking | Calculation of Degree of Connection for oreilly took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for oreilly took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for oreilly took 5.030632019042969e-05s
Believability | Calculation of trust value for oreilly took 1.0967254638671875e-05s
INFO | --- Analysis for oreilly took 1.988088607788086s
Availability | SPARQL endpoint availability check for Medicine and Natural Product Data took 8.368492126464844e-05s
Availability | VoID file availability check for Medicine and Natural Product Data took 0.00045490264892578125s
Completeness | Calculation of interlinking completeness for Medicine and Natural Product Data took 0.18023133277893066s
Reputation | Calculation of the PageRank for Medicine and Natural Product Data took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for Medicine and Natural Product Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Medicine and Natural Product Data took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Medicine and Natural Product Data took 3.266334533691406e-05s
Believability | Calculation of trust value for Medicine and Natural Product Data took 1.1682510375976562e-05s
INFO | --- Analysis for Organchem-Data took 1.9764690399169922s
Availability | SPARQL endpoint availability check for Organic Edunet Linked Open Data took 6.67572021484375e-05s
Availability | VoID file availability check for Organic Edunet Linked Open Data took 0.00047850608825683594s
Completeness | Calculation of interlinking completeness for Organic Edunet Linked Open Data took 0.1800680160522461s
Reputation | Calculation of the PageRank for Organic Edunet Linked Open Data took 0.020148754119873047s
Interlinking | Calculation of Degree of Connection for Organic Edunet Linked Open Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Organic Edunet Linked Open Data took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Organic Edunet Linked Open Data took 6.4849853515625e-05s
Believability | Calculation of trust value for Organic Edunet Linked Open Data took 1.049041748046875e-05s
INFO | --- Analysis for organic-edunet took 1.979229211807251s
Availability | SPARQL endpoint availability check for Open Research Knowledge Graph (ORKG) took 8.487701416015625e-05s
Availability | VoID file availability check for Open Research Knowledge Graph (ORKG) took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Open Research Knowledge Graph (ORKG) took 0.1799321174621582s
Reputation | Calculation of the PageRank for Open Research Knowledge Graph (ORKG) took 0.022795915603637695s
Interlinking | Calculation of Degree of Connection for Open Research Knowledge Graph (ORKG) took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Open Research Knowledge Graph (ORKG) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Open Research Knowledge Graph (ORKG) took 1.0967254638671875e-05s
Believability | Calculation of trust value for Open Research Knowledge Graph (ORKG) took 1.0728836059570312e-05s
INFO | --- Analysis for orkg took 1.9792213439941406s
Availability | SPARQL endpoint availability check for The Orlando Women's Writing Linked Open Data Set took 2.905698537826538s
Availability | VoID file availability check for The Orlando Women's Writing Linked Open Data Set took 0.00048828125s
Completeness | Calculation of interlinking completeness for The Orlando Women's Writing Linked Open Data Set took 0.17899870872497559s
Reputation | Calculation of the PageRank for The Orlando Women's Writing Linked Open Data Set took 0.020308256149291992s
Interlinking | Calculation of Degree of Connection for The Orlando Women's Writing Linked Open Data Set took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Orlando Women's Writing Linked Open Data Set took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for The Orlando Women's Writing Linked Open Data Set took 7.82012939453125e-05s
Believability | Calculation of trust value for The Orlando Women's Writing Linked Open Data Set took 1.1205673217773438e-05s
INFO | --- Analysis for orlando-womens-writing-linked-open-data-set took 7.369816064834595s
Availability | SPARQL endpoint availability check for OSM Semantic Network took 8.130073547363281e-05s
Availability | VoID file availability check for OSM Semantic Network took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for OSM Semantic Network took 0.176865816116333s
Reputation | Calculation of the PageRank for OSM Semantic Network took 0.020111799240112305s
Interlinking | Calculation of Degree of Connection for OSM Semantic Network took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for OSM Semantic Network took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for OSM Semantic Network took 3.4332275390625e-05s
Believability | Calculation of trust value for OSM Semantic Network took 1.0967254638671875e-05s
INFO | --- Analysis for osm-semantic-network took 2.0055267810821533s
Availability | SPARQL endpoint availability check for Open Transport Map @PSNC took 3.9577484130859375e-05s
Availability | VoID file availability check for Open Transport Map @PSNC took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Open Transport Map @PSNC took 0.18131017684936523s
Reputation | Calculation of the PageRank for Open Transport Map @PSNC took 0.020214557647705078s
Interlinking | Calculation of Degree of Connection for Open Transport Map @PSNC took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Open Transport Map @PSNC took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Open Transport Map @PSNC took 2.7418136596679688e-05s
Believability | Calculation of trust value for Open Transport Map @PSNC took 1.1205673217773438e-05s
INFO | --- Analysis for OTM took 1.9708805084228516s
Availability | SPARQL endpoint availability check for OUNL DSpace in RDF took 8.20159912109375e-05s
Availability | VoID file availability check for OUNL DSpace in RDF took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for OUNL DSpace in RDF took 0.1747593879699707s
Reputation | Calculation of the PageRank for OUNL DSpace in RDF took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for OUNL DSpace in RDF took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for OUNL DSpace in RDF took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for OUNL DSpace in RDF took 2.9325485229492188e-05s
Believability | Calculation of trust value for OUNL DSpace in RDF took 1.0967254638671875e-05s
INFO | --- Analysis for ounl-dspace-in-rdf took 2.083463430404663s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 8.153915405273438e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0005002021789550781s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.1739058494567871s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.1682510375976562e-05s
INFO | --- Analysis for ox-ac-uk-catalogue took 1.9661004543304443s
Availability | SPARQL endpoint availability check for Dataset catalogue (University of Oxford) took 8.344650268554688e-05s
Availability | VoID file availability check for Dataset catalogue (University of Oxford) took 0.0005195140838623047s
Completeness | Calculation of interlinking completeness for Dataset catalogue (University of Oxford) took 0.17561888694763184s
Reputation | Calculation of the PageRank for Dataset catalogue (University of Oxford) took 0.022078752517700195s
Interlinking | Calculation of Degree of Connection for Dataset catalogue (University of Oxford) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Dataset catalogue (University of Oxford) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Dataset catalogue (University of Oxford) took 2.8133392333984375e-05s
Believability | Calculation of trust value for Dataset catalogue (University of Oxford) took 1.1205673217773438e-05s
INFO | --- Analysis for ox-ac-uk-catalogue-metadata took 1.9881796836853027s
Availability | SPARQL endpoint availability check for OpenMeters (University of Oxford) took 8.487701416015625e-05s
Availability | VoID file availability check for OpenMeters (University of Oxford) took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for OpenMeters (University of Oxford) took 0.1772904396057129s
Reputation | Calculation of the PageRank for OpenMeters (University of Oxford) took 0.020200490951538086s
Interlinking | Calculation of Degree of Connection for OpenMeters (University of Oxford) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OpenMeters (University of Oxford) took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for OpenMeters (University of Oxford) took 2.765655517578125e-05s
Believability | Calculation of trust value for OpenMeters (University of Oxford) took 1.2159347534179688e-05s
INFO | --- Analysis for ox-ac-uk-openmeters took 1.9983892440795898s
Availability | SPARQL endpoint availability check for Time-series metadata (University of Oxford) took 4.00543212890625e-05s
Availability | VoID file availability check for Time-series metadata (University of Oxford) took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for Time-series metadata (University of Oxford) took 0.17281246185302734s
Reputation | Calculation of the PageRank for Time-series metadata (University of Oxford) took 0.020192861557006836s
Interlinking | Calculation of Degree of Connection for Time-series metadata (University of Oxford) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Time-series metadata (University of Oxford) took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for Time-series metadata (University of Oxford) took 2.8848648071289062e-05s
Believability | Calculation of trust value for Time-series metadata (University of Oxford) took 1.1920928955078125e-05s
INFO | --- Analysis for ox-ac-uk-timeseries took 1.9850430488586426s
Availability | SPARQL endpoint availability check for Vacancies (University of Oxford) took 8.273124694824219e-05s
Availability | VoID file availability check for Vacancies (University of Oxford) took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Vacancies (University of Oxford) took 0.17708635330200195s
Reputation | Calculation of the PageRank for Vacancies (University of Oxford) took 0.02010035514831543s
Interlinking | Calculation of Degree of Connection for Vacancies (University of Oxford) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vacancies (University of Oxford) took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for Vacancies (University of Oxford) took 2.9087066650390625e-05s
Believability | Calculation of trust value for Vacancies (University of Oxford) took 1.0967254638671875e-05s
INFO | --- Analysis for ox-ac-uk-vacancies took 1.9580564498901367s
Availability | SPARQL endpoint availability check for Events calendar for the University (University of Oxford) took 3.9577484130859375e-05s
Availability | VoID file availability check for Events calendar for the University (University of Oxford) took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Events calendar for the University (University of Oxford) took 0.1789684295654297s
Reputation | Calculation of the PageRank for Events calendar for the University (University of Oxford) took 0.020113229751586914s
Interlinking | Calculation of Degree of Connection for Events calendar for the University (University of Oxford) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Events calendar for the University (University of Oxford) took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Events calendar for the University (University of Oxford) took 2.765655517578125e-05s
Believability | Calculation of trust value for Events calendar for the University (University of Oxford) took 1.0251998901367188e-05s
INFO | --- Analysis for ox-ac-uk-www-ox-ac-uk-events took 1.9981751441955566s
Availability | SPARQL endpoint availability check for OxPoints (University of Oxford) took 4.0531158447265625e-05s
Availability | VoID file availability check for OxPoints (University of Oxford) took 0.00043845176696777344s
Completeness | Calculation of interlinking completeness for OxPoints (University of Oxford) took 0.17896223068237305s
Reputation | Calculation of the PageRank for OxPoints (University of Oxford) took 0.020197629928588867s
Interlinking | Calculation of Degree of Connection for OxPoints (University of Oxford) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OxPoints (University of Oxford) took 0.0007140636444091797s
Interlinking | Calculation of Clustering coefficient for OxPoints (University of Oxford) took 3.0040740966796875e-05s
Believability | Calculation of trust value for OxPoints (University of Oxford) took 1.0967254638671875e-05s
INFO | --- Analysis for oxpoints took 1.9881434440612793s
Availability | SPARQL endpoint availability check for Pali English Lexicon took 1.496598243713379s
Availability | VoID file availability check for Pali English Lexicon took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Pali English Lexicon took 0.18448352813720703s
Reputation | Calculation of the PageRank for Pali English Lexicon took 0.020157337188720703s
Interlinking | Calculation of Degree of Connection for Pali English Lexicon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Pali English Lexicon took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Pali English Lexicon took 2.86102294921875e-05s
Believability | Calculation of trust value for Pali English Lexicon took 1.049041748046875e-05s
INFO | --- Analysis for pali-english-lexicon took 4.570513486862183s
Availability | SPARQL endpoint availability check for PanLex took 8.368492126464844e-05s
Availability | VoID file availability check for PanLex took 0.00022983551025390625s
Completeness | Calculation of interlinking completeness for PanLex took 0.17980480194091797s
Reputation | Calculation of the PageRank for PanLex took 0.02196192741394043s
Interlinking | Calculation of Degree of Connection for PanLex took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for PanLex took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for PanLex took 7.033348083496094e-05s
Believability | Calculation of trust value for PanLex took 1.0967254638671875e-05s
INFO | --- Analysis for panlex took 1.9727413654327393s
Availability | SPARQL endpoint availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 8.368492126464844e-05s
Availability | VoID file availability check for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for Parole/Simple 'lexinfo' Ontology & lexicons took 0.17314600944519043s
Reputation | Calculation of the PageRank for Parole/Simple 'lexinfo' Ontology & lexicons took 0.020120620727539062s
Interlinking | Calculation of Degree of Connection for Parole/Simple 'lexinfo' Ontology & lexicons took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Parole/Simple 'lexinfo' Ontology & lexicons took 0.0007987022399902344s
Interlinking | Calculation of Clustering coefficient for Parole/Simple 'lexinfo' Ontology & lexicons took 3.838539123535156e-05s
Believability | Calculation of trust value for Parole/Simple 'lexinfo' Ontology & lexicons took 1.049041748046875e-05s
INFO | --- Analysis for parole-simple-lexinfo-ontology-lexicons took 1.9486236572265625s
Availability | SPARQL endpoint availability check for patents.data.gov.uk took 8.249282836914062e-05s
Availability | VoID file availability check for patents.data.gov.uk took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for patents.data.gov.uk took 0.17515230178833008s
Reputation | Calculation of the PageRank for patents.data.gov.uk took 0.02068018913269043s
Interlinking | Calculation of Degree of Connection for patents.data.gov.uk took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for patents.data.gov.uk took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for patents.data.gov.uk took 4.7206878662109375e-05s
Believability | Calculation of trust value for patents.data.gov.uk took 1.0251998901367188e-05s
INFO | --- Analysis for patents-data-gov-uk took 1.991715431213379s
Availability | SPARQL endpoint availability check for PDEV-Lemon took 8.344650268554688e-05s
Availability | VoID file availability check for PDEV-Lemon took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for PDEV-Lemon took 0.18764877319335938s
Reputation | Calculation of the PageRank for PDEV-Lemon took 0.020112991333007812s
Interlinking | Calculation of Degree of Connection for PDEV-Lemon took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PDEV-Lemon took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for PDEV-Lemon took 3.457069396972656e-05s
Believability | Calculation of trust value for PDEV-Lemon took 1.0728836059570312e-05s
INFO | --- Analysis for pdev-lemon took 1.9602208137512207s
Availability | SPARQL endpoint availability check for pdevlemon took 8.296966552734375e-05s
Availability | VoID file availability check for pdevlemon took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for pdevlemon took 0.17459678649902344s
Reputation | Calculation of the PageRank for pdevlemon took 0.020549535751342773s
Interlinking | Calculation of Degree of Connection for pdevlemon took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for pdevlemon took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for pdevlemon took 3.0279159545898438e-05s
Believability | Calculation of trust value for pdevlemon took 1.2159347534179688e-05s
INFO | --- Analysis for pdevlemon took 2.0312788486480713s
Availability | SPARQL endpoint availability check for PeriodO Period Gazetteer took 9.417533874511719e-05s
Availability | VoID file availability check for PeriodO Period Gazetteer took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for PeriodO Period Gazetteer took 0.1804490089416504s
Reputation | Calculation of the PageRank for PeriodO Period Gazetteer took 0.02250838279724121s
Interlinking | Calculation of Degree of Connection for PeriodO Period Gazetteer took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for PeriodO Period Gazetteer took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for PeriodO Period Gazetteer took 7.510185241699219e-05s
Believability | Calculation of trust value for PeriodO Period Gazetteer took 1.239776611328125e-05s
INFO | --- Analysis for periodo took 2.006927251815796s
Availability | SPARQL endpoint availability check for Personal_Homepages took 8.296966552734375e-05s
Availability | VoID file availability check for Personal_Homepages took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for Personal_Homepages took 0.17361927032470703s
Reputation | Calculation of the PageRank for Personal_Homepages took 0.020140886306762695s
Interlinking | Calculation of Degree of Connection for Personal_Homepages took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Personal_Homepages took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Personal_Homepages took 0.00038242340087890625s
Believability | Calculation of trust value for Personal_Homepages took 1.0728836059570312e-05s
INFO | --- Analysis for personal-homepages took 1.9797303676605225s
Availability | SPARQL endpoint availability check for Ontology of University People took 8.392333984375e-05s
Availability | VoID file availability check for Ontology of University People took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Ontology of University People took 0.18123650550842285s
Reputation | Calculation of the PageRank for Ontology of University People took 0.021160125732421875s
Interlinking | Calculation of Degree of Connection for Ontology of University People took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Ontology of University People took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Ontology of University People took 2.7418136596679688e-05s
Believability | Calculation of trust value for Ontology of University People took 1.1205673217773438e-05s
INFO | --- Analysis for PersonOnto took 2.0200417041778564s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 8.249282836914062e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.18786334991455078s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.020528316497802734s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.2159347534179688e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1920928955078125e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0251998901367188e-05s
INFO | --- Analysis for PFKHS took 2.000805616378784s
Availability | SPARQL endpoint availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 8.058547973632812e-05s
Availability | VoID file availability check for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0004227161407470703s
Completeness | Calculation of interlinking completeness for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.18372774124145508s
Reputation | Calculation of the PageRank for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.02014946937561035s
Interlinking | Calculation of Degree of Connection for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.1205673217773438e-05s
Believability | Calculation of trust value for The retellings of "The Pear Film" by preschoolers, primary school students, and high school students took 1.0013580322265625e-05s
INFO | --- Analysis for PFRPPH took 1.9820737838745117s
Availability | SPARQL endpoint availability check for PGxLOD took 8.0108642578125e-05s
Availability | VoID file availability check for PGxLOD took 0.00021648406982421875s
Completeness | Calculation of interlinking completeness for PGxLOD took 0.17871809005737305s
Reputation | Calculation of the PageRank for PGxLOD took 0.020089149475097656s
Interlinking | Calculation of Degree of Connection for PGxLOD took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for PGxLOD took 0.0007979869842529297s
Interlinking | Calculation of Clustering coefficient for PGxLOD took 4.124641418457031e-05s
Believability | Calculation of trust value for PGxLOD took 1.0251998901367188e-05s
INFO | --- Analysis for PGxLOD took 2.004206895828247s
Availability | SPARQL endpoint availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 8.273124694824219e-05s
Availability | VoID file availability check for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for Phonetics Information Base and Lexicon (PHOIBLE) took 0.17949247360229492s
Reputation | Calculation of the PageRank for Phonetics Information Base and Lexicon (PHOIBLE) took 0.020346641540527344s
Interlinking | Calculation of Degree of Connection for Phonetics Information Base and Lexicon (PHOIBLE) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Phonetics Information Base and Lexicon (PHOIBLE) took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for Phonetics Information Base and Lexicon (PHOIBLE) took 3.361701965332031e-05s
Believability | Calculation of trust value for Phonetics Information Base and Lexicon (PHOIBLE) took 1.049041748046875e-05s
INFO | --- Analysis for phoible took 1.9546089172363281s
Availability | SPARQL endpoint availability check for Parallel ice sheet model took 8.344650268554688e-05s
Availability | VoID file availability check for Parallel ice sheet model took 0.0004730224609375s
Completeness | Calculation of interlinking completeness for Parallel ice sheet model took 0.17247629165649414s
Reputation | Calculation of the PageRank for Parallel ice sheet model took 0.022609949111938477s
Interlinking | Calculation of Degree of Connection for Parallel ice sheet model took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Parallel ice sheet model took 0.0007219314575195312s
Interlinking | Calculation of Clustering coefficient for Parallel ice sheet model took 3.337860107421875e-05s
Believability | Calculation of trust value for Parallel ice sheet model took 1.0728836059570312e-05s
INFO | --- Analysis for PISM took 2.002000331878662s
Availability | SPARQL endpoint availability check for PlanetData Project Wiki took 8.058547973632812e-05s
Availability | VoID file availability check for PlanetData Project Wiki took 0.0005240440368652344s
Completeness | Calculation of interlinking completeness for PlanetData Project Wiki took 0.18069148063659668s
Reputation | Calculation of the PageRank for PlanetData Project Wiki took 0.020434856414794922s
Interlinking | Calculation of Degree of Connection for PlanetData Project Wiki took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for PlanetData Project Wiki took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for PlanetData Project Wiki took 8.20159912109375e-05s
Believability | Calculation of trust value for PlanetData Project Wiki took 1.049041748046875e-05s
INFO | --- Analysis for planetdata-project-wiki took 1.9434237480163574s
Availability | SPARQL endpoint availability check for digitized plant specimen took 4.00543212890625e-05s
Availability | VoID file availability check for digitized plant specimen took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for digitized plant specimen took 0.1774759292602539s
Reputation | Calculation of the PageRank for digitized plant specimen took 0.020315885543823242s
Interlinking | Calculation of Degree of Connection for digitized plant specimen took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for digitized plant specimen took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for digitized plant specimen took 6.389617919921875e-05s
Believability | Calculation of trust value for digitized plant specimen took 1.0013580322265625e-05s
INFO | --- Analysis for plant-specimen took 2.073345184326172s
Availability | SPARQL endpoint availability check for Pleiades took 8.678436279296875e-05s
Availability | VoID file availability check for Pleiades took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for Pleiades took 0.1790604591369629s
Reputation | Calculation of the PageRank for Pleiades took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Pleiades took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Pleiades took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Pleiades took 7.939338684082031e-05s
Believability | Calculation of trust value for Pleiades took 6.198883056640625e-06s
INFO | --- Analysis for pleiades took 1.9927613735198975s
Availability | SPARQL endpoint availability check for podorozhnyk.com took 8.344650268554688e-05s
Availability | VoID file availability check for podorozhnyk.com took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for podorozhnyk.com took 0.17289066314697266s
Reputation | Calculation of the PageRank for podorozhnyk.com took 0.02044820785522461s
Interlinking | Calculation of Degree of Connection for podorozhnyk.com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for podorozhnyk.com took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for podorozhnyk.com took 2.8133392333984375e-05s
Believability | Calculation of trust value for podorozhnyk.com took 5.9604644775390625e-06s
INFO | --- Analysis for podorozhnyk took 1.9566564559936523s
Availability | SPARQL endpoint availability check for Poképédia took 4.0531158447265625e-05s
Availability | VoID file availability check for Poképédia took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Poképédia took 0.18087458610534668s
Reputation | Calculation of the PageRank for Poképédia took 0.020172595977783203s
Interlinking | Calculation of Degree of Connection for Poképédia took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Poképédia took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Poképédia took 6.747245788574219e-05s
Believability | Calculation of trust value for Poképédia took 6.4373016357421875e-06s
INFO | --- Analysis for pokepedia-fr took 1.938866376876831s
Availability | SPARQL endpoint availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 4.1484832763671875e-05s
Availability | VoID file availability check for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.1790311336517334s
Reputation | Calculation of the PageRank for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.020269393920898438s
Interlinking | Calculation of Degree of Connection for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 0.0007238388061523438s
Interlinking | Calculation of Clustering coefficient for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 7.414817810058594e-05s
Believability | Calculation of trust value for Polymath Virtual Library (Authority data) - Fundación Ignacio Larramendi took 1.0967254638671875e-05s
INFO | --- Analysis for polymath-virtual-library took 1.9854638576507568s
Availability | SPARQL endpoint availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 8.225440979003906e-05s
Availability | VoID file availability check for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0004322528839111328s
Completeness | Calculation of interlinking completeness for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.18072104454040527s
Reputation | Calculation of the PageRank for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.02097153663635254s
Interlinking | Calculation of Degree of Connection for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.3113021850585938e-05s
Believability | Calculation of trust value for Synthetic Portuguese prisons releases Jan 2018 - Dec 2023 took 1.049041748046875e-05s
INFO | --- Analysis for portuguese_prisons_releases took 1.9669334888458252s
Availability | SPARQL endpoint availability check for Barley trading volume and wholesale prices took 3.8623809814453125e-05s
Availability | VoID file availability check for Barley trading volume and wholesale prices took 0.0004181861877441406s
Completeness | Calculation of interlinking completeness for Barley trading volume and wholesale prices took 0.17451214790344238s
Reputation | Calculation of the PageRank for Barley trading volume and wholesale prices took 0.02272653579711914s
Interlinking | Calculation of Degree of Connection for Barley trading volume and wholesale prices took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Barley trading volume and wholesale prices took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for Barley trading volume and wholesale prices took 3.0517578125e-05s
Believability | Calculation of trust value for Barley trading volume and wholesale prices took 1.0013580322265625e-05s
INFO | --- Analysis for predicting-barley-volume-and-wholesale-prices took 1.9491643905639648s
Availability | SPARQL endpoint availability check for Corn trading volume and wholesale prices took 9.059906005859375e-05s
Availability | VoID file availability check for Corn trading volume and wholesale prices took 0.00045990943908691406s
Completeness | Calculation of interlinking completeness for Corn trading volume and wholesale prices took 0.1752009391784668s
Reputation | Calculation of the PageRank for Corn trading volume and wholesale prices took 0.020375967025756836s
Interlinking | Calculation of Degree of Connection for Corn trading volume and wholesale prices took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Corn trading volume and wholesale prices took 0.0007481575012207031s
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 1.1682510375976562e-05s
INFO | --- Analysis for predicting-corn-trading-volume-and-wholesale-prices took 1.9927239418029785s
Availability | SPARQL endpoint availability check for Onion trading volume and wholesale prices took 8.368492126464844e-05s
Availability | VoID file availability check for Onion trading volume and wholesale prices took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Onion trading volume and wholesale prices took 0.18251466751098633s
Reputation | Calculation of the PageRank for Onion trading volume and wholesale prices took 0.020376920700073242s
Interlinking | Calculation of Degree of Connection for Onion trading volume and wholesale prices took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Onion trading volume and wholesale prices took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Onion trading volume and wholesale prices took 2.8848648071289062e-05s
Believability | Calculation of trust value for Onion trading volume and wholesale prices took 1.1920928955078125e-05s
INFO | --- Analysis for predicting-onion-volume-and-wholesale-prices took 1.987023115158081s
Availability | SPARQL endpoint availability check for Potato trading volume and wholesale price took 8.082389831542969e-05s
Availability | VoID file availability check for Potato trading volume and wholesale price took 0.00044608116149902344s
Completeness | Calculation of interlinking completeness for Potato trading volume and wholesale price took 0.1909632682800293s
Reputation | Calculation of the PageRank for Potato trading volume and wholesale price took 0.020256757736206055s
Interlinking | Calculation of Degree of Connection for Potato trading volume and wholesale price took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Potato trading volume and wholesale price took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Potato trading volume and wholesale price took 2.8848648071289062e-05s
Believability | Calculation of trust value for Potato trading volume and wholesale price took 6.4373016357421875e-06s
INFO | --- Analysis for predicting-potato-trading-volume-and-wholesale-prices took 1.9671411514282227s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of apples took 3.9577484130859375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of apples took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of apples took 0.17794466018676758s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of apples took 0.020169973373413086s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of apples took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of apples took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of apples took 2.86102294921875e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of apples took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-apples took 1.9738099575042725s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of barley took 8.296966552734375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of barley took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of barley took 0.18187236785888672s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of barley took 0.020352840423583984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of barley took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of barley took 0.0007174015045166016s
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 1.1920928955078125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-barley took 1.9710054397583008s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of bean took 8.416175842285156e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of bean took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of bean took 0.18034577369689941s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of bean took 0.02034592628479004s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of bean took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of bean took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of bean took 2.956390380859375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of bean took 1.2874603271484375e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-bean took 1.9599239826202393s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cabbage took 3.910064697265625e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cabbage took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cabbage took 0.18356919288635254s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cabbage took 0.020170211791992188s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cabbage took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cabbage took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cabbage took 2.7418136596679688e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cabbage took 1.1682510375976562e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cabbage took 1.98972749710083s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of corn took 8.368492126464844e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of corn took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of corn took 0.18132758140563965s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of corn took 0.020101547241210938s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of corn took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of corn took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of corn took 2.8133392333984375e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of corn took 1.1444091796875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-corn took 1.993600845336914s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of crab took 8.463859558105469e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of crab took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of crab took 0.177321195602417s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of crab took 0.02029275894165039s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of crab took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of crab took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of crab took 2.8848648071289062e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of crab took 1.0967254638671875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-crab took 1.9695165157318115s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of cucumber took 7.987022399902344e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of cucumber took 0.0005059242248535156s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of cucumber took 0.17547130584716797s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of cucumber took 0.020150184631347656s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of cucumber took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of cucumber took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of cucumber took 2.7179718017578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of cucumber took 1.0967254638671875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-cucumber took 1.9887394905090332s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of lettuce took 4.482269287109375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of lettuce took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of lettuce took 0.18756866455078125s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of lettuce took 0.020727872848510742s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of lettuce took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of lettuce took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of lettuce took 2.7418136596679688e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of lettuce took 1.2159347534179688e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-lettuce2 took 1.990851879119873s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of onion took 3.886222839355469e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of onion took 0.00047898292541503906s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of onion took 0.17979955673217773s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of onion took 0.022519588470458984s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of onion took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of onion took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of onion took 2.7894973754882812e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of onion took 1.1682510375976562e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-onion took 1.9815537929534912s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of oyster mushroom took 8.296966552734375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of oyster mushroom took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of oyster mushroom took 0.18371820449829102s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of oyster mushroom took 0.020072221755981445s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of oyster mushroom took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of oyster mushroom took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of oyster mushroom took 2.7894973754882812e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of oyster mushroom took 1.0967254638671875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-oyster-mushroom took 1.9991254806518555s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of potato took 8.630752563476562e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of potato took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of potato took 0.18298935890197754s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of potato took 0.02088022232055664s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of potato took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of potato took 0.00072479248046875s
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 6.67572021484375e-06s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-potato took 1.9820570945739746s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of radish took 8.344650268554688e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of radish took 0.00047016143798828125s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of radish took 0.1896069049835205s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of radish took 0.020102262496948242s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of radish took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of radish took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of radish took 2.7418136596679688e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of radish took 1.1682510375976562e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-radish2 took 2.0138330459594727s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of rice plant took 8.392333984375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of rice plant took 0.00020170211791992188s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of rice plant took 0.18738102912902832s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of rice plant took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of rice plant took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of rice plant took 0.0007715225219726562s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of rice plant took 3.24249267578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of rice plant took 1.239776611328125e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-rice-plant took 1.9800965785980225s
Availability | SPARQL endpoint availability check for Predicting wholesale imports by region of watermelon took 8.392333984375e-05s
Availability | VoID file availability check for Predicting wholesale imports by region of watermelon took 0.000499725341796875s
Completeness | Calculation of interlinking completeness for Predicting wholesale imports by region of watermelon took 0.1838057041168213s
Reputation | Calculation of the PageRank for Predicting wholesale imports by region of watermelon took 0.021095991134643555s
Interlinking | Calculation of Degree of Connection for Predicting wholesale imports by region of watermelon took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Predicting wholesale imports by region of watermelon took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Predicting wholesale imports by region of watermelon took 2.765655517578125e-05s
Believability | Calculation of trust value for Predicting wholesale imports by region of watermelon took 1.0967254638671875e-05s
INFO | --- Analysis for predicting-wholesale-imports-by-region-of-watermelon took 1.9915120601654053s
Availability | SPARQL endpoint availability check for prefix.cc took 8.130073547363281e-05s
Availability | VoID file availability check for prefix.cc took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for prefix.cc took 0.1833634376525879s
Reputation | Calculation of the PageRank for prefix.cc took 0.02016758918762207s
Interlinking | Calculation of Degree of Connection for prefix.cc took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for prefix.cc took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for prefix.cc took 3.5762786865234375e-05s
Believability | Calculation of trust value for prefix.cc took 1.1205673217773438e-05s
INFO | --- Analysis for prefix-cc took 1.993640661239624s
Availability | SPARQL endpoint availability check for PREJUST4WOMEN Knowledge Graph took 8.463859558105469e-05s
Availability | VoID file availability check for PREJUST4WOMEN Knowledge Graph took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for PREJUST4WOMEN Knowledge Graph took 0.1733720302581787s
Reputation | Calculation of the PageRank for PREJUST4WOMEN Knowledge Graph took 0.020116806030273438s
Interlinking | Calculation of Degree of Connection for PREJUST4WOMEN Knowledge Graph took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for PREJUST4WOMEN Knowledge Graph took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for PREJUST4WOMEN Knowledge Graph took 4.673004150390625e-05s
Believability | Calculation of trust value for PREJUST4WOMEN Knowledge Graph took 1.1205673217773438e-05s
INFO | --- Analysis for PREJUST4WOMAN_PROJECT took 1.9831037521362305s
Availability | SPARQL endpoint availability check for PreLex took 4.363059997558594e-05s
Availability | VoID file availability check for PreLex took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for PreLex took 0.1729745864868164s
Reputation | Calculation of the PageRank for PreLex took 0.02033209800720215s
Interlinking | Calculation of Degree of Connection for PreLex took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PreLex took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for PreLex took 6.651878356933594e-05s
Believability | Calculation of trust value for PreLex took 1.1444091796875e-05s
INFO | --- Analysis for prelex took 2.000793933868408s
Availability | SPARQL endpoint availability check for Prelinger Archives took 2.223593235015869s
Availability | VoID file availability check for Prelinger Archives took 0.0004820823669433594s
Completeness | Calculation of interlinking completeness for Prelinger Archives took 0.19766569137573242s
Reputation | Calculation of the PageRank for Prelinger Archives took 0.020141124725341797s
Interlinking | Calculation of Degree of Connection for Prelinger Archives took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Prelinger Archives took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Prelinger Archives took 2.9802322387695312e-05s
Believability | Calculation of trust value for Prelinger Archives took 7.3909759521484375e-06s
INFO | --- Analysis for prelinger_archives took 6.064001083374023s
Availability | SPARQL endpoint availability check for PreMOn (Predicate Model for Ontologies) took 8.296966552734375e-05s
Availability | VoID file availability check for PreMOn (Predicate Model for Ontologies) took 0.0004475116729736328s
Completeness | Calculation of interlinking completeness for PreMOn (Predicate Model for Ontologies) took 0.1743912696838379s
Reputation | Calculation of the PageRank for PreMOn (Predicate Model for Ontologies) took 0.020310163497924805s
Interlinking | Calculation of Degree of Connection for PreMOn (Predicate Model for Ontologies) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PreMOn (Predicate Model for Ontologies) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for PreMOn (Predicate Model for Ontologies) took 4.935264587402344e-05s
Believability | Calculation of trust value for PreMOn (Predicate Model for Ontologies) took 8.106231689453125e-06s
INFO | --- Analysis for premon took 1.9778130054473877s
Availability | SPARQL endpoint availability check for Princeton Library FindingAids took 8.678436279296875e-05s
Availability | VoID file availability check for Princeton Library FindingAids took 0.0005309581756591797s
Completeness | Calculation of interlinking completeness for Princeton Library FindingAids took 0.18540024757385254s
Reputation | Calculation of the PageRank for Princeton Library FindingAids took 0.02224445343017578s
Interlinking | Calculation of Degree of Connection for Princeton Library FindingAids took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Princeton Library FindingAids took 0.0007641315460205078s
Interlinking | Calculation of Clustering coefficient for Princeton Library FindingAids took 6.413459777832031e-05s
Believability | Calculation of trust value for Princeton Library FindingAids took 1.2636184692382812e-05s
INFO | --- Analysis for princeton-library-findingaids took 1.9995191097259521s
Availability | SPARQL endpoint availability check for PrinParLat in LiLa took 4.172325134277344e-05s
Availability | VoID file availability check for PrinParLat in LiLa took 0.0002541542053222656s
Completeness | Calculation of interlinking completeness for PrinParLat in LiLa took 0.19965195655822754s
Reputation | Calculation of the PageRank for PrinParLat in LiLa took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for PrinParLat in LiLa took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PrinParLat in LiLa took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for PrinParLat in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for PrinParLat in LiLa took 1.2874603271484375e-05s
INFO | --- Analysis for PrinParLat took 1.9984962940216064s
Availability | SPARQL endpoint availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.43855977058410645s
Availability | VoID file availability check for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.18001842498779297s
Reputation | Calculation of the PageRank for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.02202439308166504s
Interlinking | Calculation of Degree of Connection for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 8.034706115722656e-05s
Believability | Calculation of trust value for English Language Books listed in Printed Book Auction Catalogues from 17th Century Holland took 7.62939453125e-06s
INFO | --- Analysis for printed-book-auction-catalogues took 2.5530800819396973s
Availability | SPARQL endpoint availability check for Prior Panel took 8.368492126464844e-05s
Availability | VoID file availability check for Prior Panel took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Prior Panel took 0.17502737045288086s
Reputation | Calculation of the PageRank for Prior Panel took 0.027333498001098633s
Interlinking | Calculation of Degree of Connection for Prior Panel took 2.384185791015625e-05s
Interlinking | Calculation of Centrality for Prior Panel took 0.002373218536376953s
Interlinking | Calculation of Clustering coefficient for Prior Panel took 7.534027099609375e-05s
Believability | Calculation of trust value for Prior Panel took 1.0728836059570312e-05s
INFO | --- Analysis for Prior_Panel took 2.010958433151245s
Availability | SPARQL endpoint availability check for Procedimientos, trámites y servicios took 8.96453857421875e-05s
Availability | VoID file availability check for Procedimientos, trámites y servicios took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for Procedimientos, trámites y servicios took 0.18278980255126953s
Reputation | Calculation of the PageRank for Procedimientos, trámites y servicios took 0.022046804428100586s
Interlinking | Calculation of Degree of Connection for Procedimientos, trámites y servicios took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Procedimientos, trámites y servicios took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Procedimientos, trámites y servicios took 3.0517578125e-05s
Believability | Calculation of trust value for Procedimientos, trámites y servicios took 1.3828277587890625e-05s
INFO | --- Analysis for procedimientos-tramites-servicios-zaragoza took 1.9871337413787842s
Availability | SPARQL endpoint availability check for Procomún SPARQL took 8.58306884765625e-05s
Availability | VoID file availability check for Procomún SPARQL took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for Procomún SPARQL took 0.1854240894317627s
Reputation | Calculation of the PageRank for Procomún SPARQL took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for Procomún SPARQL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Procomún SPARQL took 0.0007216930389404297s
Interlinking | Calculation of Clustering coefficient for Procomún SPARQL took 2.9325485229492188e-05s
Believability | Calculation of trust value for Procomún SPARQL took 1.3589859008789062e-05s
INFO | --- Analysis for procomun-sparql took 1.9642024040222168s
Availability | SPARQL endpoint availability check for PROD - JISC Project Directory in RDF took 8.177757263183594e-05s
Availability | VoID file availability check for PROD - JISC Project Directory in RDF took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for PROD - JISC Project Directory in RDF took 0.18015313148498535s
Reputation | Calculation of the PageRank for PROD - JISC Project Directory in RDF took 0.022493839263916016s
Interlinking | Calculation of Degree of Connection for PROD - JISC Project Directory in RDF took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for PROD - JISC Project Directory in RDF took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for PROD - JISC Project Directory in RDF took 3.075599670410156e-05s
Believability | Calculation of trust value for PROD - JISC Project Directory in RDF took 5.0067901611328125e-06s
INFO | --- Analysis for prod-jisc-project-directory-in-rdf took 1.971360683441162s
Availability | SPARQL endpoint availability check for ProductDB took 8.726119995117188e-05s
Availability | VoID file availability check for ProductDB took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for ProductDB took 0.17925572395324707s
Reputation | Calculation of the PageRank for ProductDB took 0.022423982620239258s
Interlinking | Calculation of Degree of Connection for ProductDB took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ProductDB took 0.000957489013671875s
Interlinking | Calculation of Clustering coefficient for ProductDB took 7.605552673339844e-05s
Believability | Calculation of trust value for ProductDB took 1.2874603271484375e-05s
INFO | --- Analysis for productdb took 1.9985201358795166s
Availability | SPARQL endpoint availability check for Product Types Ontology took 8.177757263183594e-05s
Availability | VoID file availability check for Product Types Ontology took 0.00020766258239746094s
Completeness | Calculation of interlinking completeness for Product Types Ontology took 0.1780092716217041s
Reputation | Calculation of the PageRank for Product Types Ontology took 0.020190954208374023s
Interlinking | Calculation of Degree of Connection for Product Types Ontology took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Product Types Ontology took 0.0007307529449462891s
Interlinking | Calculation of Clustering coefficient for Product Types Ontology took 7.152557373046875e-05s
Believability | Calculation of trust value for Product Types Ontology took 1.1205673217773438e-05s
INFO | --- Analysis for productontology took 1.9852344989776611s
Availability | SPARQL endpoint availability check for Prospects and Trends (GNOSS) took 8.20159912109375e-05s
Availability | VoID file availability check for Prospects and Trends (GNOSS) took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Prospects and Trends (GNOSS) took 0.1834244728088379s
Reputation | Calculation of the PageRank for Prospects and Trends (GNOSS) took 0.02013230323791504s
Interlinking | Calculation of Degree of Connection for Prospects and Trends (GNOSS) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Prospects and Trends (GNOSS) took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Prospects and Trends (GNOSS) took 9.751319885253906e-05s
Believability | Calculation of trust value for Prospects and Trends (GNOSS) took 1.1682510375976562e-05s
INFO | --- Analysis for prospects-and-trends-gnoss took 2.208078384399414s
Availability | SPARQL endpoint availability check for provenanceweb took 8.058547973632812e-05s
Availability | VoID file availability check for provenanceweb took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for provenanceweb took 0.1839148998260498s
Reputation | Calculation of the PageRank for provenanceweb took 0.02008056640625s
Interlinking | Calculation of Degree of Connection for provenanceweb took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for provenanceweb took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for provenanceweb took 6.67572021484375e-05s
Believability | Calculation of trust value for provenanceweb took 6.67572021484375e-06s
INFO | --- Analysis for provenanceweb took 1.9791169166564941s
Availability | SPARQL endpoint availability check for Proyecto Apadrina,  Marketing Punto de Venta took 9.822845458984375e-05s
Availability | VoID file availability check for Proyecto Apadrina,  Marketing Punto de Venta took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for Proyecto Apadrina,  Marketing Punto de Venta took 0.17448139190673828s
Reputation | Calculation of the PageRank for Proyecto Apadrina,  Marketing Punto de Venta took 0.020548105239868164s
Interlinking | Calculation of Degree of Connection for Proyecto Apadrina,  Marketing Punto de Venta took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Proyecto Apadrina,  Marketing Punto de Venta took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for Proyecto Apadrina,  Marketing Punto de Venta took 9.655952453613281e-05s
Believability | Calculation of trust value for Proyecto Apadrina,  Marketing Punto de Venta took 1.049041748046875e-05s
INFO | --- Analysis for proyectoapadrina took 1.9870781898498535s
Availability | SPARQL endpoint availability check for Product Scheme Classifications Catalogue took 3.9577484130859375e-05s
Availability | VoID file availability check for Product Scheme Classifications Catalogue took 0.00044155120849609375s
Completeness | Calculation of interlinking completeness for Product Scheme Classifications Catalogue took 0.18265390396118164s
Reputation | Calculation of the PageRank for Product Scheme Classifications Catalogue took 0.020279645919799805s
Interlinking | Calculation of Degree of Connection for Product Scheme Classifications Catalogue took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Product Scheme Classifications Catalogue took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for Product Scheme Classifications Catalogue took 3.266334533691406e-05s
Believability | Calculation of trust value for Product Scheme Classifications Catalogue took 1.33514404296875e-05s
INFO | --- Analysis for pscs-catalogue took 2.0378262996673584s
Availability | SPARQL endpoint availability check for Polythematic Structured Subject Heading System took 8.273124694824219e-05s
Availability | VoID file availability check for Polythematic Structured Subject Heading System took 0.00022101402282714844s
Completeness | Calculation of interlinking completeness for Polythematic Structured Subject Heading System took 0.1813063621520996s
Reputation | Calculation of the PageRank for Polythematic Structured Subject Heading System took 0.021613597869873047s
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.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Polythematic Structured Subject Heading System took 7.05718994140625e-05s
Believability | Calculation of trust value for Polythematic Structured Subject Heading System took 1.0967254638671875e-05s
INFO | --- Analysis for psh-subject-headings took 2.013707160949707s
Availability | SPARQL endpoint availability check for Depression took 7.82012939453125e-05s
Availability | VoID file availability check for Depression took 0.0004284381866455078s
Completeness | Calculation of interlinking completeness for Depression took 0.18216919898986816s
Reputation | Calculation of the PageRank for Depression took 0.021721363067626953s
Interlinking | Calculation of Degree of Connection for Depression took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Depression took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for Depression took 3.075599670410156e-05s
Believability | Calculation of trust value for Depression took 5.7220458984375e-06s
INFO | --- Analysis for Psychology took 1.967005968093872s
Availability | SPARQL endpoint availability check for PubChem RDF took 8.153915405273438e-05s
Availability | VoID file availability check for PubChem RDF took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for PubChem RDF took 0.18087077140808105s
Reputation | Calculation of the PageRank for PubChem RDF took 0.020176172256469727s
Interlinking | Calculation of Degree of Connection for PubChem RDF took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for PubChem RDF took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for PubChem RDF took 3.814697265625e-05s
Believability | Calculation of trust value for PubChem RDF took 1.0967254638671875e-05s
INFO | --- Analysis for PubChem_RDF took 1.976377248764038s
Availability | SPARQL endpoint availability check for Public Record Office Victoria Semantic Wiki took 8.487701416015625e-05s
Availability | VoID file availability check for Public Record Office Victoria Semantic Wiki took 0.0004253387451171875s
Completeness | Calculation of interlinking completeness for Public Record Office Victoria Semantic Wiki took 0.1792151927947998s
Reputation | Calculation of the PageRank for Public Record Office Victoria Semantic Wiki took 0.022426366806030273s
Interlinking | Calculation of Degree of Connection for Public Record Office Victoria Semantic Wiki took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Public Record Office Victoria Semantic Wiki took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for Public Record Office Victoria Semantic Wiki took 2.8848648071289062e-05s
Believability | Calculation of trust value for Public Record Office Victoria Semantic Wiki took 1.0728836059570312e-05s
INFO | --- Analysis for public-record-office-victoria-semantic-wiki took 1.9890503883361816s
Availability | SPARQL endpoint availability check for Public Spending in Greece took 8.034706115722656e-05s
Availability | VoID file availability check for Public Spending in Greece took 0.0004324913024902344s
Completeness | Calculation of interlinking completeness for Public Spending in Greece took 0.1798877716064453s
Reputation | Calculation of the PageRank for Public Spending in Greece took 0.020305633544921875s
Interlinking | Calculation of Degree of Connection for Public Spending in Greece took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Public Spending in Greece took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Public Spending in Greece took 7.62939453125e-05s
Believability | Calculation of trust value for Public Spending in Greece took 1.049041748046875e-05s
INFO | --- Analysis for public-spending-in-greece took 2.0525808334350586s
Availability | SPARQL endpoint availability check for Publications of Charles University in Prague took 8.058547973632812e-05s
Availability | VoID file availability check for Publications of Charles University in Prague took 0.00043892860412597656s
Completeness | Calculation of interlinking completeness for Publications of Charles University in Prague took 0.17470717430114746s
Reputation | Calculation of the PageRank for Publications of Charles University in Prague took 0.020023822784423828s
Interlinking | Calculation of Degree of Connection for Publications of Charles University in Prague took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Publications of Charles University in Prague took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for Publications of Charles University in Prague took 2.9087066650390625e-05s
Believability | Calculation of trust value for Publications of Charles University in Prague took 1.049041748046875e-05s
INFO | --- Analysis for publications-of-charles-university-in-prague took 1.9915506839752197s
Availability | SPARQL endpoint availability check for Publications Office Authority tables took 9.274482727050781e-05s
Availability | VoID file availability check for Publications Office Authority tables took 0.00041866302490234375s
Completeness | Calculation of interlinking completeness for Publications Office Authority tables took 0.18473172187805176s
Reputation | Calculation of the PageRank for Publications Office Authority tables took 0.022319555282592773s
Interlinking | Calculation of Degree of Connection for Publications Office Authority tables took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Publications Office Authority tables took 0.0007784366607666016s
Interlinking | Calculation of Clustering coefficient for Publications Office Authority tables took 3.743171691894531e-05s
Believability | Calculation of trust value for Publications Office Authority tables took 1.049041748046875e-05s
INFO | --- Analysis for publications_office_authority_tables took 2.0040249824523926s
Availability | SPARQL endpoint availability check for Publikace Univerzity Karlovy v Praze took 8.106231689453125e-05s
Availability | VoID file availability check for Publikace Univerzity Karlovy v Praze took 0.0004420280456542969s
Completeness | Calculation of interlinking completeness for Publikace Univerzity Karlovy v Praze took 0.17806148529052734s
Reputation | Calculation of the PageRank for Publikace Univerzity Karlovy v Praze took 0.02208995819091797s
Interlinking | Calculation of Degree of Connection for Publikace Univerzity Karlovy v Praze took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Publikace Univerzity Karlovy v Praze took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for Publikace Univerzity Karlovy v Praze took 2.765655517578125e-05s
Believability | Calculation of trust value for Publikace Univerzity Karlovy v Praze took 1.049041748046875e-05s
INFO | --- Analysis for publikace-univerzity-karlovy-v-praze took 2.0151565074920654s
Availability | SPARQL endpoint availability check for QBOAirbase took 3.886222839355469e-05s
Availability | VoID file availability check for QBOAirbase took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for QBOAirbase took 0.1697392463684082s
Reputation | Calculation of the PageRank for QBOAirbase took 0.021592378616333008s
Interlinking | Calculation of Degree of Connection for QBOAirbase took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for QBOAirbase took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for QBOAirbase took 7.224082946777344e-05s
Believability | Calculation of trust value for QBOAirbase took 5.9604644775390625e-06s
INFO | --- Analysis for qboairbase took 2.103403091430664s
Availability | SPARQL endpoint availability check for qualitywebdata.org took 4.076957702636719e-05s
Availability | VoID file availability check for qualitywebdata.org took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for qualitywebdata.org took 0.17429089546203613s
Reputation | Calculation of the PageRank for qualitywebdata.org took 0.020261049270629883s
Interlinking | Calculation of Degree of Connection for qualitywebdata.org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for qualitywebdata.org took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for qualitywebdata.org took 2.765655517578125e-05s
Believability | Calculation of trust value for qualitywebdata.org took 1.0251998901367188e-05s
INFO | --- Analysis for qualitywebdata-org took 1.934128999710083s
Availability | SPARQL endpoint availability check for Qualité de l'air took 8.296966552734375e-05s
Availability | VoID file availability check for Qualité de l'air took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for Qualité de l'air took 0.17534756660461426s
Reputation | Calculation of the PageRank for Qualité de l'air took 0.020177364349365234s
Interlinking | Calculation of Degree of Connection for Qualité de l'air took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Qualité de l'air took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air took 2.9325485229492188e-05s
Believability | Calculation of trust value for Qualité de l'air took 1.0013580322265625e-05s
INFO | --- Analysis for Qualité_de_l'air took 1.9699525833129883s
Availability | SPARQL endpoint availability check for Qualité de l'air dans le monde took 4.00543212890625e-05s
Availability | VoID file availability check for Qualité de l'air dans le monde took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for Qualité de l'air dans le monde took 0.18510913848876953s
Reputation | Calculation of the PageRank for Qualité de l'air dans le monde took 0.02026081085205078s
Interlinking | Calculation of Degree of Connection for Qualité de l'air dans le monde took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Qualité de l'air dans le monde took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Qualité de l'air dans le monde took 2.6702880859375e-05s
Believability | Calculation of trust value for Qualité de l'air dans le monde took 1.0251998901367188e-05s
INFO | --- Analysis for Qualité_de_l'air_dans_le_monde took 1.9843344688415527s
Availability | SPARQL endpoint availability check for Querolus in LiLa took 0.5802021026611328s
Availability | VoID file availability check for Querolus in LiLa took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for Querolus in LiLa took 0.1723923683166504s
Reputation | Calculation of the PageRank for Querolus in LiLa took 0.020456790924072266s
Interlinking | Calculation of Degree of Connection for Querolus in LiLa took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Querolus in LiLa took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for Querolus in LiLa took 3.62396240234375e-05s
Believability | Calculation of trust value for Querolus in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for Querolus took 2.942660093307495s
Availability | SPARQL endpoint availability check for Quotations Book took 8.344650268554688e-05s
Availability | VoID file availability check for Quotations Book took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Quotations Book took 0.18425416946411133s
Reputation | Calculation of the PageRank for Quotations Book took 0.02135157585144043s
Interlinking | Calculation of Degree of Connection for Quotations Book took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Quotations Book took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Quotations Book took 2.765655517578125e-05s
Believability | Calculation of trust value for Quotations Book took 1.1205673217773438e-05s
INFO | --- Analysis for quotations_book took 1.999765396118164s
Availability | SPARQL endpoint availability check for Relations for Reusing (R4R) Ontology took 8.416175842285156e-05s
Availability | VoID file availability check for Relations for Reusing (R4R) Ontology took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Relations for Reusing (R4R) Ontology took 0.17336726188659668s
Reputation | Calculation of the PageRank for Relations for Reusing (R4R) Ontology took 0.021347522735595703s
Interlinking | Calculation of Degree of Connection for Relations for Reusing (R4R) Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Relations for Reusing (R4R) Ontology took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Relations for Reusing (R4R) Ontology took 3.123283386230469e-05s
Believability | Calculation of trust value for Relations for Reusing (R4R) Ontology took 1.0967254638671875e-05s
INFO | --- Analysis for r4r took 2.000257730484009s
Availability | SPARQL endpoint availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 8.463859558105469e-05s
Availability | VoID file availability check for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.1761338710784912s
Reputation | Calculation of the PageRank for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.020333051681518555s
Interlinking | Calculation of Degree of Connection for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 7.867813110351562e-06s
Interlinking | Calculation of Centrality for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 4.601478576660156e-05s
Believability | Calculation of trust value for Romanian Named Entity Recognition in the Legal domain (LegalNERo) took 1.2159347534179688e-05s
INFO | --- Analysis for racai-legalnero took 2.027060031890869s
Availability | SPARQL endpoint availability check for Romanian CoRoLa Word Embeddings took 8.130073547363281e-05s
Availability | VoID file availability check for Romanian CoRoLa Word Embeddings took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for Romanian CoRoLa Word Embeddings took 0.17862629890441895s
Reputation | Calculation of the PageRank for Romanian CoRoLa Word Embeddings took 0.020282745361328125s
Interlinking | Calculation of Degree of Connection for Romanian CoRoLa Word Embeddings took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Romanian CoRoLa Word Embeddings took 0.0007860660552978516s
Interlinking | Calculation of Clustering coefficient for Romanian CoRoLa Word Embeddings took 3.266334533691406e-05s
Believability | Calculation of trust value for Romanian CoRoLa Word Embeddings took 1.0728836059570312e-05s
INFO | --- Analysis for racai-llod-corola-we took 1.9840404987335205s
Availability | SPARQL endpoint availability check for PARSEME-Ro corpus took 8.249282836914062e-05s
Availability | VoID file availability check for PARSEME-Ro corpus took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for PARSEME-Ro corpus took 0.17839503288269043s
Reputation | Calculation of the PageRank for PARSEME-Ro corpus took 0.020076751708984375s
Interlinking | Calculation of Degree of Connection for PARSEME-Ro corpus took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for PARSEME-Ro corpus took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for PARSEME-Ro corpus took 2.8371810913085938e-05s
Believability | Calculation of trust value for PARSEME-Ro corpus took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-parseme-ro took 2.0016417503356934s
Availability | SPARQL endpoint availability check for RoLEX took 4.172325134277344e-05s
Availability | VoID file availability check for RoLEX took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for RoLEX took 0.18830585479736328s
Reputation | Calculation of the PageRank for RoLEX took 0.02031397819519043s
Interlinking | Calculation of Degree of Connection for RoLEX took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RoLEX took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for RoLEX took 2.9802322387695312e-05s
Believability | Calculation of trust value for RoLEX took 1.049041748046875e-05s
INFO | --- Analysis for racai-llod-rolex took 1.9786403179168701s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.17222905158996582s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020330429077148438s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Romanian took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Romanian took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Romanian took 2.9087066650390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Romanian took 1.1920928955078125e-05s
INFO | --- Analysis for racai-llod-romanian-treebank took 1.9837822914123535s
Availability | SPARQL endpoint availability check for JSON Romanian Wordnet took 8.58306884765625e-05s
Availability | VoID file availability check for JSON Romanian Wordnet took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for JSON Romanian Wordnet took 0.18778514862060547s
Reputation | Calculation of the PageRank for JSON Romanian Wordnet took 0.020305395126342773s
Interlinking | Calculation of Degree of Connection for JSON Romanian Wordnet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for JSON Romanian Wordnet took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for JSON Romanian Wordnet took 2.8371810913085938e-05s
Believability | Calculation of trust value for JSON Romanian Wordnet took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-json took 1.9800693988800049s
Availability | SPARQL endpoint availability check for LMF Romanian Wordnet took 4.029273986816406e-05s
Availability | VoID file availability check for LMF Romanian Wordnet took 0.00020599365234375s
Completeness | Calculation of interlinking completeness for LMF Romanian Wordnet took 0.18010258674621582s
Reputation | Calculation of the PageRank for LMF Romanian Wordnet took 0.021381616592407227s
Interlinking | Calculation of Degree of Connection for LMF Romanian Wordnet took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for LMF Romanian Wordnet took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for LMF Romanian Wordnet took 2.86102294921875e-05s
Believability | Calculation of trust value for LMF Romanian Wordnet took 1.0967254638671875e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-lmf took 1.9615881443023682s
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.0004456043243408203s
Completeness | Calculation of interlinking completeness for Turtle-RDF Romanian Wordnet took 0.18046355247497559s
Reputation | Calculation of the PageRank for Turtle-RDF Romanian Wordnet took 0.02261042594909668s
Interlinking | Calculation of Degree of Connection for Turtle-RDF Romanian Wordnet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Turtle-RDF Romanian Wordnet took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Turtle-RDF Romanian Wordnet took 2.956390380859375e-05s
Believability | Calculation of trust value for Turtle-RDF Romanian Wordnet took 1.1682510375976562e-05s
INFO | --- Analysis for racai-llod-romanian-wordnet-ttl took 1.9879035949707031s
Availability | SPARQL endpoint availability check for ROBIN Technical Acquisition Speech Corpus took 8.225440979003906e-05s
Availability | VoID file availability check for ROBIN Technical Acquisition Speech Corpus took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for ROBIN Technical Acquisition Speech Corpus took 0.1753678321838379s
Reputation | Calculation of the PageRank for ROBIN Technical Acquisition Speech Corpus took 0.0204622745513916s
Interlinking | Calculation of Degree of Connection for ROBIN Technical Acquisition Speech Corpus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ROBIN Technical Acquisition Speech Corpus took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for ROBIN Technical Acquisition Speech Corpus took 2.9087066650390625e-05s
Believability | Calculation of trust value for ROBIN Technical Acquisition Speech Corpus took 1.1205673217773438e-05s
INFO | --- Analysis for racai-llod-rtasc took 1.9782006740570068s
Availability | SPARQL endpoint availability check for SiMoNERo - the Romanian medical treebank took 4.00543212890625e-05s
Availability | VoID file availability check for SiMoNERo - the Romanian medical treebank took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for SiMoNERo - the Romanian medical treebank took 0.181962251663208s
Reputation | Calculation of the PageRank for SiMoNERo - the Romanian medical treebank took 0.021177291870117188s
Interlinking | Calculation of Degree of Connection for SiMoNERo - the Romanian medical treebank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SiMoNERo - the Romanian medical treebank took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for SiMoNERo - the Romanian medical treebank took 2.8848648071289062e-05s
Believability | Calculation of trust value for SiMoNERo - the Romanian medical treebank took 1.0251998901367188e-05s
INFO | --- Analysis for racai-llod-simonero took 1.9945731163024902s
Availability | SPARQL endpoint availability check for Rådata nå! took 0.22812438011169434s
Availability | VoID file availability check for Rådata nå! took 0.0004858970642089844s
Completeness | Calculation of interlinking completeness for Rådata nå! took 0.1754002571105957s
Reputation | Calculation of the PageRank for Rådata nå! took 0.02032637596130371s
Interlinking | Calculation of Degree of Connection for Rådata nå! took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Rådata nå! took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Rådata nå! took 7.653236389160156e-05s
Believability | Calculation of trust value for Rådata nå! took 1.1444091796875e-05s
INFO | --- Analysis for radatana took 2.2232255935668945s
Availability | SPARQL endpoint availability check for "Rainis and Aspazija" Linked Digital Collection took 8.58306884765625e-05s
Availability | VoID file availability check for "Rainis and Aspazija" Linked Digital Collection took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for "Rainis and Aspazija" Linked Digital Collection took 0.1848587989807129s
Reputation | Calculation of the PageRank for "Rainis and Aspazija" Linked Digital Collection took 0.02058100700378418s
Interlinking | Calculation of Degree of Connection for "Rainis and Aspazija" Linked Digital Collection took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for "Rainis and Aspazija" Linked Digital Collection took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for "Rainis and Aspazija" Linked Digital Collection took 3.981590270996094e-05s
Believability | Calculation of trust value for "Rainis and Aspazija" Linked Digital Collection took 1.0013580322265625e-05s
INFO | --- Analysis for rainis-and-aspazija-linked-digital-collection took 1.9884681701660156s
Availability | SPARQL endpoint availability check for Raphael Research Resource took 3.9577484130859375e-05s
Availability | VoID file availability check for Raphael Research Resource took 0.0004591941833496094s
Completeness | Calculation of interlinking completeness for Raphael Research Resource took 0.17894220352172852s
Reputation | Calculation of the PageRank for Raphael Research Resource took 0.022336244583129883s
Interlinking | Calculation of Degree of Connection for Raphael Research Resource took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Raphael Research Resource took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Raphael Research Resource took 3.0040740966796875e-05s
Believability | Calculation of trust value for Raphael Research Resource took 1.0013580322265625e-05s
INFO | --- Analysis for raphaelresearchresource took 2.096068859100342s
Availability | SPARQL endpoint availability check for Ravensburg Local Shopping Graph took 7.748603820800781e-05s
Availability | VoID file availability check for Ravensburg Local Shopping Graph took 0.0004260540008544922s
Completeness | Calculation of interlinking completeness for Ravensburg Local Shopping Graph took 0.1876215934753418s
Reputation | Calculation of the PageRank for Ravensburg Local Shopping Graph took 0.02034735679626465s
Interlinking | Calculation of Degree of Connection for Ravensburg Local Shopping Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ravensburg Local Shopping Graph took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for Ravensburg Local Shopping Graph took 3.0994415283203125e-05s
Believability | Calculation of trust value for Ravensburg Local Shopping Graph took 1.0251998901367188e-05s
INFO | --- Analysis for ravensburg-local-shopping-graph took 2.026836633682251s
Availability | SPARQL endpoint availability check for Polish LGU financial statements took 7.772445678710938e-05s
Availability | VoID file availability check for Polish LGU financial statements took 0.0004329681396484375s
Completeness | Calculation of interlinking completeness for Polish LGU financial statements took 0.17423319816589355s
Reputation | Calculation of the PageRank for Polish LGU financial statements took 0.02288961410522461s
Interlinking | Calculation of Degree of Connection for Polish LGU financial statements took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Polish LGU financial statements took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Polish LGU financial statements took 3.0517578125e-05s
Believability | Calculation of trust value for Polish LGU financial statements took 1.0013580322265625e-05s
INFO | --- Analysis for Rb_PL_LGU took 1.9923477172851562s
Availability | SPARQL endpoint availability check for RCAHMS Archaeological Objects Thesaurus took 3.910064697265625e-05s
Availability | VoID file availability check for RCAHMS Archaeological Objects Thesaurus took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for RCAHMS Archaeological Objects Thesaurus took 0.2048323154449463s
Reputation | Calculation of the PageRank for RCAHMS Archaeological Objects Thesaurus took 0.02032923698425293s
Interlinking | Calculation of Degree of Connection for RCAHMS Archaeological Objects Thesaurus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RCAHMS Archaeological Objects Thesaurus took 0.0007379055023193359s
Interlinking | Calculation of Clustering coefficient for RCAHMS Archaeological Objects Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for RCAHMS Archaeological Objects Thesaurus took 1.0013580322265625e-05s
INFO | --- Analysis for rcahms-archaeological-objects-thesaurus took 2.0296905040740967s
Availability | SPARQL endpoint availability check for RCAHMS Maritime Craft Thesaurus took 7.843971252441406e-05s
Availability | VoID file availability check for RCAHMS Maritime Craft Thesaurus took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for RCAHMS Maritime Craft Thesaurus took 0.18233323097229004s
Reputation | Calculation of the PageRank for RCAHMS Maritime Craft Thesaurus took 0.020487546920776367s
Interlinking | Calculation of Degree of Connection for RCAHMS Maritime Craft Thesaurus took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RCAHMS Maritime Craft Thesaurus took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for RCAHMS Maritime Craft Thesaurus took 3.147125244140625e-05s
Believability | Calculation of trust value for RCAHMS Maritime Craft Thesaurus took 5.4836273193359375e-06s
INFO | --- Analysis for rcahms-maritime-craft-thesaurus took 1.9783892631530762s
Availability | SPARQL endpoint availability check for RCAHMS Monument Types Thesaurus took 0.0001266002655029297s
Availability | VoID file availability check for RCAHMS Monument Types Thesaurus took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for RCAHMS Monument Types Thesaurus took 0.17633318901062012s
Reputation | Calculation of the PageRank for RCAHMS Monument Types Thesaurus took 0.020166635513305664s
Interlinking | Calculation of Degree of Connection for RCAHMS Monument Types Thesaurus took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RCAHMS Monument Types Thesaurus took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for RCAHMS Monument Types Thesaurus took 3.0040740966796875e-05s
Believability | Calculation of trust value for RCAHMS Monument Types Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for rcahms-monument-types-thesaurus took 1.9874377250671387s
Availability | SPARQL endpoint availability check for RCAHMW Monument Types Thesaurus took 3.9577484130859375e-05s
Availability | VoID file availability check for RCAHMW Monument Types Thesaurus took 0.0004367828369140625s
Completeness | Calculation of interlinking completeness for RCAHMW Monument Types Thesaurus took 0.1830918788909912s
Reputation | Calculation of the PageRank for RCAHMW Monument Types Thesaurus took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for RCAHMW Monument Types Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RCAHMW Monument Types Thesaurus took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for RCAHMW Monument Types Thesaurus took 3.075599670410156e-05s
Believability | Calculation of trust value for RCAHMW Monument Types Thesaurus took 1.0251998901367188e-05s
INFO | --- Analysis for rcahmw-monument-types-thesaurus took 1.9792096614837646s
Availability | SPARQL endpoint availability check for RCAHMW Periods List took 8.058547973632812e-05s
Availability | VoID file availability check for RCAHMW Periods List took 0.0004248619079589844s
Completeness | Calculation of interlinking completeness for RCAHMW Periods List took 0.18381381034851074s
Reputation | Calculation of the PageRank for RCAHMW Periods List took 0.020243406295776367s
Interlinking | Calculation of Degree of Connection for RCAHMW Periods List took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RCAHMW Periods List took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for RCAHMW Periods List took 3.075599670410156e-05s
Believability | Calculation of trust value for RCAHMW Periods List took 1.0251998901367188e-05s
INFO | --- Analysis for rcahmw-periods-list took 1.9883365631103516s
Availability | SPARQL endpoint availability check for RDF Book Mashup took 7.939338684082031e-05s
Availability | VoID file availability check for RDF Book Mashup took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for RDF Book Mashup took 0.18091821670532227s
Reputation | Calculation of the PageRank for RDF Book Mashup took 0.020455121994018555s
Interlinking | Calculation of Degree of Connection for RDF Book Mashup took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RDF Book Mashup took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for RDF Book Mashup took 8.344650268554688e-05s
Believability | Calculation of trust value for RDF Book Mashup took 1.0013580322265625e-05s
INFO | --- Analysis for rdf-book-mashup took 2.03603196144104s
Availability | SPARQL endpoint availability check for Last.FM RDFization of Events, Artists, and Users took 8.869171142578125e-05s
Availability | VoID file availability check for Last.FM RDFization of Events, Artists, and Users took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Last.FM RDFization of Events, Artists, and Users took 0.17532682418823242s
Reputation | Calculation of the PageRank for Last.FM RDFization of Events, Artists, and Users took 0.020539522171020508s
Interlinking | Calculation of Degree of Connection for Last.FM RDFization of Events, Artists, and Users took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Last.FM RDFization of Events, Artists, and Users took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Last.FM RDFization of Events, Artists, and Users took 0.00011658668518066406s
Believability | Calculation of trust value for Last.FM RDFization of Events, Artists, and Users took 9.298324584960938e-06s
INFO | --- Analysis for rdfize-lastfm took 1.9919028282165527s
Availability | SPARQL endpoint availability check for RDFLicense took 9.894371032714844e-05s
Availability | VoID file availability check for RDFLicense took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for RDFLicense took 0.18305492401123047s
Reputation | Calculation of the PageRank for RDFLicense took 0.022354602813720703s
Interlinking | Calculation of Degree of Connection for RDFLicense took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RDFLicense took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for RDFLicense took 3.123283386230469e-05s
Believability | Calculation of trust value for RDFLicense took 1.0251998901367188e-05s
INFO | --- Analysis for rdflicense took 2.032850980758667s
Availability | SPARQL endpoint availability check for RDFohloh took 8.296966552734375e-05s
Availability | VoID file availability check for RDFohloh took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for RDFohloh took 0.17302775382995605s
Reputation | Calculation of the PageRank for RDFohloh took 0.021013975143432617s
Interlinking | Calculation of Degree of Connection for RDFohloh took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RDFohloh took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for RDFohloh took 0.00010585784912109375s
Believability | Calculation of trust value for RDFohloh took 1.1444091796875e-05s
INFO | --- Analysis for rdfohloh took 2.008225917816162s
Availability | SPARQL endpoint availability check for Reactome RDF took 8.296966552734375e-05s
Availability | VoID file availability check for Reactome RDF took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Reactome RDF took 0.19255924224853516s
Reputation | Calculation of the PageRank for Reactome RDF took 0.020381927490234375s
Interlinking | Calculation of Degree of Connection for Reactome RDF took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Reactome RDF took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Reactome RDF took 3.647804260253906e-05s
Believability | Calculation of trust value for Reactome RDF took 1.0967254638671875e-05s
INFO | --- Analysis for reactome-rdf took 2.0181832313537598s
Availability | SPARQL endpoint availability check for Rechtspraak.nl took 4.76837158203125e-05s
Availability | VoID file availability check for Rechtspraak.nl took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for Rechtspraak.nl took 0.17760777473449707s
Reputation | Calculation of the PageRank for Rechtspraak.nl took 0.0204465389251709s
Interlinking | Calculation of Degree of Connection for Rechtspraak.nl took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rechtspraak.nl took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Rechtspraak.nl took 9.608268737792969e-05s
Believability | Calculation of trust value for Rechtspraak.nl took 6.198883056640625e-06s
INFO | --- Analysis for rechtspraak took 1.9719717502593994s
Availability | SPARQL endpoint availability check for Red Uno Internacional (Santillana) took 4.0531158447265625e-05s
Availability | VoID file availability check for Red Uno Internacional (Santillana) took 0.00021600723266601562s
Completeness | Calculation of interlinking completeness for Red Uno Internacional (Santillana) took 0.18056797981262207s
Reputation | Calculation of the PageRank for Red Uno Internacional (Santillana) took 0.020491361618041992s
Interlinking | Calculation of Degree of Connection for Red Uno Internacional (Santillana) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Red Uno Internacional (Santillana) took 0.0007390975952148438s
Interlinking | Calculation of Clustering coefficient for Red Uno Internacional (Santillana) took 8.559226989746094e-05s
Believability | Calculation of trust value for Red Uno Internacional (Santillana) took 5.245208740234375e-06s
INFO | --- Analysis for red-uno-internacional-santillana took 2.0119495391845703s
Availability | SPARQL endpoint availability check for reference.data.gov.uk took 3.910064697265625e-05s
Availability | VoID file availability check for reference.data.gov.uk took 0.00021338462829589844s
Completeness | Calculation of interlinking completeness for reference.data.gov.uk took 0.1775360107421875s
Reputation | Calculation of the PageRank for reference.data.gov.uk took 0.020366907119750977s
Interlinking | Calculation of Degree of Connection for reference.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for reference.data.gov.uk took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for reference.data.gov.uk took 0.00015926361083984375s
Believability | Calculation of trust value for reference.data.gov.uk took 5.4836273193359375e-06s
INFO | --- Analysis for reference-data-gov-uk took 1.976011037826538s
Availability | SPARQL endpoint availability check for Regiony took 6.628036499023438e-05s
Availability | VoID file availability check for Regiony took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Regiony took 0.1806635856628418s
Reputation | Calculation of the PageRank for Regiony took 0.02051568031311035s
Interlinking | Calculation of Degree of Connection for Regiony took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Regiony took 0.0007278919219970703s
Interlinking | Calculation of Clustering coefficient for Regiony took 3.0517578125e-05s
Believability | Calculation of trust value for Regiony took 6.198883056640625e-06s
INFO | --- Analysis for regiony took 1.9657375812530518s
Availability | SPARQL endpoint availability check for RELD took 8.177757263183594e-05s
Availability | VoID file availability check for RELD took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for RELD took 0.17284703254699707s
Reputation | Calculation of the PageRank for RELD took 0.021152019500732422s
Interlinking | Calculation of Degree of Connection for RELD took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RELD took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for RELD took 3.2901763916015625e-05s
Believability | Calculation of trust value for RELD took 1.2874603271484375e-05s
INFO | --- Analysis for RELD took 2.0343034267425537s
Availability | SPARQL endpoint availability check for Repository for Linked Open Archival Data took 4.887580871582031e-05s
Availability | VoID file availability check for Repository for Linked Open Archival Data took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for Repository for Linked Open Archival Data took 0.19022417068481445s
Reputation | Calculation of the PageRank for Repository for Linked Open Archival Data took 0.02049875259399414s
Interlinking | Calculation of Degree of Connection for Repository for Linked Open Archival Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Repository for Linked Open Archival Data took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Repository for Linked Open Archival Data took 3.504753112792969e-05s
Believability | Calculation of trust value for Repository for Linked Open Archival Data took 5.4836273193359375e-06s
INFO | --- Analysis for reload took 1.9068279266357422s
Availability | SPARQL endpoint availability check for Land use merced dataset took 3.8623809814453125e-05s
Availability | VoID file availability check for Land use merced dataset took 0.0002129077911376953s
Completeness | Calculation of interlinking completeness for Land use merced dataset took 0.16885113716125488s
Reputation | Calculation of the PageRank for Land use merced dataset took 0.020298480987548828s
Interlinking | Calculation of Degree of Connection for Land use merced dataset took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Land use merced dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Land use merced dataset took 2.7894973754882812e-05s
Believability | Calculation of trust value for Land use merced dataset took 5.4836273193359375e-06s
INFO | --- Analysis for remote_Sensing took 1.920624017715454s
Availability | SPARQL endpoint availability check for Renewable Energy Generators took 3.814697265625e-05s
Availability | VoID file availability check for Renewable Energy Generators took 0.00021076202392578125s
Completeness | Calculation of interlinking completeness for Renewable Energy Generators took 0.17972612380981445s
Reputation | Calculation of the PageRank for Renewable Energy Generators took 0.020506858825683594s
Interlinking | Calculation of Degree of Connection for Renewable Energy Generators took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Renewable Energy Generators took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Renewable Energy Generators took 4.410743713378906e-05s
Believability | Calculation of trust value for Renewable Energy Generators took 1.2159347534179688e-05s
INFO | --- Analysis for renewable_energy_generators took 1.9615063667297363s
Availability | SPARQL endpoint availability check for research.data.gov.uk took 7.867813110351562e-05s
Availability | VoID file availability check for research.data.gov.uk took 0.00046062469482421875s
Completeness | Calculation of interlinking completeness for research.data.gov.uk took 0.17252206802368164s
Reputation | Calculation of the PageRank for research.data.gov.uk took 0.021010637283325195s
Interlinking | Calculation of Degree of Connection for research.data.gov.uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for research.data.gov.uk took 0.0007088184356689453s
Interlinking | Calculation of Clustering coefficient for research.data.gov.uk took 8.845329284667969e-05s
Believability | Calculation of trust value for research.data.gov.uk took 1.0967254638671875e-05s
INFO | --- Analysis for research-data-gov-uk took 1.973125696182251s
Availability | SPARQL endpoint availability check for Research object in Agricolture and Food of the University of Naples took 5.173683166503906e-05s
Availability | VoID file availability check for Research object in Agricolture and Food of the University of Naples took 0.0003039836883544922s
Completeness | Calculation of interlinking completeness for Research object in Agricolture and Food of the University of Naples took 0.17498207092285156s
Reputation | Calculation of the PageRank for Research object in Agricolture and Food of the University of Naples took 0.021076679229736328s
Interlinking | Calculation of Degree of Connection for Research object in Agricolture and Food of the University of Naples took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Research object in Agricolture and Food of the University of Naples took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Research object in Agricolture and Food of the University of Naples took 3.0994415283203125e-05s
Believability | Calculation of trust value for Research object in Agricolture and Food of the University of Naples took 1.1682510375976562e-05s
INFO | --- Analysis for research-object-in-agricolture-and-food-of-the-university-of-naples took 1.9917638301849365s
Availability | SPARQL endpoint availability check for Restaurantes took 7.963180541992188e-05s
Availability | VoID file availability check for Restaurantes took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for Restaurantes took 0.1847703456878662s
Reputation | Calculation of the PageRank for Restaurantes took 0.021620988845825195s
Interlinking | Calculation of Degree of Connection for Restaurantes took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Restaurantes took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for Restaurantes took 3.0994415283203125e-05s
Believability | Calculation of trust value for Restaurantes took 5.7220458984375e-06s
INFO | --- Analysis for restaurantes-zaragoza took 1.980194330215454s
Availability | SPARQL endpoint availability check for Reuters-128 NIF NER Corpus took 4.0531158447265625e-05s
Availability | VoID file availability check for Reuters-128 NIF NER Corpus took 0.00045418739318847656s
Completeness | Calculation of interlinking completeness for Reuters-128 NIF NER Corpus took 0.1889958381652832s
Reputation | Calculation of the PageRank for Reuters-128 NIF NER Corpus took 0.02063298225402832s
Interlinking | Calculation of Degree of Connection for Reuters-128 NIF NER Corpus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Reuters-128 NIF NER Corpus took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for Reuters-128 NIF NER Corpus took 6.628036499023438e-05s
Believability | Calculation of trust value for Reuters-128 NIF NER Corpus took 7.62939453125e-06s
INFO | --- Analysis for reuters-128-nif-ner-corpus took 1.990098237991333s
Availability | SPARQL endpoint availability check for Revista Excelencias Turísticas took 4.0531158447265625e-05s
Availability | VoID file availability check for Revista Excelencias Turísticas took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for Revista Excelencias Turísticas took 0.17902421951293945s
Reputation | Calculation of the PageRank for Revista Excelencias Turísticas took 0.022068500518798828s
Interlinking | Calculation of Degree of Connection for Revista Excelencias Turísticas took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Revista Excelencias Turísticas took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for Revista Excelencias Turísticas took 3.0994415283203125e-05s
Believability | Calculation of trust value for Revista Excelencias Turísticas took 1.049041748046875e-05s
INFO | --- Analysis for revistas_turismo took 1.9593253135681152s
Availability | SPARQL endpoint availability check for Revyu.com - Review Anything took 8.630752563476562e-05s
Availability | VoID file availability check for Revyu.com - Review Anything took 0.0005598068237304688s
Completeness | Calculation of interlinking completeness for Revyu.com - Review Anything took 0.19127655029296875s
Reputation | Calculation of the PageRank for Revyu.com - Review Anything took 0.022925853729248047s
Interlinking | Calculation of Degree of Connection for Revyu.com - Review Anything took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Revyu.com - Review Anything took 0.0011661052703857422s
Interlinking | Calculation of Clustering coefficient for Revyu.com - Review Anything took 0.00014543533325195312s
Believability | Calculation of trust value for Revyu.com - Review Anything took 1.6927719116210938e-05s
INFO | --- Analysis for revyu took 1.9716947078704834s
Availability | SPARQL endpoint availability check for sdafsadf took 8.153915405273438e-05s
Availability | VoID file availability check for sdafsadf took 0.0004546642303466797s
Completeness | Calculation of interlinking completeness for sdafsadf took 0.17343449592590332s
Reputation | Calculation of the PageRank for sdafsadf took 0.022301435470581055s
Interlinking | Calculation of Degree of Connection for sdafsadf took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for sdafsadf took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for sdafsadf took 2.9802322387695312e-05s
Believability | Calculation of trust value for sdafsadf took 1.0251998901367188e-05s
INFO | --- Analysis for rgsdfg took 1.9837403297424316s
Availability | SPARQL endpoint availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 4.267692565917969e-05s
Availability | VoID file availability check for RDFizing and Interlinking the EuroStat Data Set Effort took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for RDFizing and Interlinking the EuroStat Data Set Effort took 0.18357110023498535s
Reputation | Calculation of the PageRank for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for RDFizing and Interlinking the EuroStat Data Set Effort took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for RDFizing and Interlinking the EuroStat Data Set Effort took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for RDFizing and Interlinking the EuroStat Data Set Effort took 4.792213439941406e-05s
Believability | Calculation of trust value for RDFizing and Interlinking the EuroStat Data Set Effort took 5.7220458984375e-06s
INFO | --- Analysis for riese took 1.991368293762207s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection Data took 8.416175842285156e-05s
Availability | VoID file availability check for Rijksmuseum Collection Data took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection Data took 0.17997503280639648s
Reputation | Calculation of the PageRank for Rijksmuseum Collection Data took 0.02054738998413086s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Rijksmuseum Collection Data took 0.0007200241088867188s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection Data took 3.2901763916015625e-05s
Believability | Calculation of trust value for Rijksmuseum Collection Data took 1.0728836059570312e-05s
INFO | --- Analysis for rijksmuseum took 1.9943187236785889s
Availability | SPARQL endpoint availability check for Répertoire International des Sources Musicales - RISM took 134.35180592536926s
Availability | VoID file availability check for Répertoire International des Sources Musicales - RISM took 0.0005192756652832031s
Extra | Recovery of all triples for Répertoire International des Sources Musicales - RISM took 21.144726037979126s
Performance | Total latancy measurement for Répertoire International des Sources Musicales - RISM took 0.5023891925811768s
Amount of data | Number of triples check for Répertoire International des Sources Musicales - RISM took 51.97926664352417s
Interoperability | New terms check for Répertoire International des Sources Musicales - RISM took 1.9979135990142822s
Versatility | Languages check for Répertoire International des Sources Musicales - RISM took 173.71780705451965s
Interpretability | Number of blank nodes check for Répertoire International des Sources Musicales - RISM took 180.60528898239136s
Security | Check HTTPS for Répertoire International des Sources Musicales - RISM took 0.2365710735321045s
Interpretability | RDF structures check for Répertoire International des Sources Musicales - RISM took 0.13827180862426758s
Versatility | Serialization formats check for Répertoire International des Sources Musicales - RISM took 0.12409734725952148s
Availability | RDF dump link check for Répertoire International des Sources Musicales - RISM took 0.09358096122741699s
License | MR license check for Répertoire International des Sources Musicales - RISM took 0.10135149955749512s
License | HR license check for Répertoire International des Sources Musicales - RISM took 300.0964674949646s
Amount of data | Number of property check for Répertoire International des Sources Musicales - RISM took 135.30248951911926s
Understandability | Number of label check for Répertoire International des Sources Musicales - RISM took 8.161494255065918s
Understandability | URI regex check for Répertoire International des Sources Musicales - RISM took 0.23653554916381836s
Understandability | Vocabs check for Répertoire International des Sources Musicales - RISM took 0.10565924644470215s
Verifiability | Authors check for Répertoire International des Sources Musicales - RISM took 0.10187482833862305s
Verifiability | Publishers check for Répertoire International des Sources Musicales - RISM took 0.10981583595275879s
Performance | Throughput check for Répertoire International des Sources Musicales - RISM took 10.581970453262329s
Amount of data | Check the number of entities for Répertoire International des Sources Musicales - RISM took 0.00014472007751464844s
Verifiability | Contribs. check for Répertoire International des Sources Musicales - RISM took 0.10725903511047363s
Interlinking | sameAs chians check for Répertoire International des Sources Musicales - RISM took 1.2769300937652588s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.12805461883544922s
Interlinking | skos check for Répertoire International des Sources Musicales - RISM took 0.10226082801818848s
Timeliness | dataset update frequency check for Répertoire International des Sources Musicales - RISM took 0.10654520988464355s
Currency | Creation date check for Répertoire International des Sources Musicales - RISM took 0.23432207107543945s
Currency | Modification date check for Répertoire International des Sources Musicales - RISM took 0.23896312713623047s
Rep.Conc. | URIs length for Répertoire International des Sources Musicales - RISM took 75.39889097213745s
Interoperability | New vocabularies check for Répertoire International des Sources Musicales - RISM took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Répertoire International des Sources Musicales - RISM took 0.14417219161987305s
Accuracy | Check Functional Property for Répertoire International des Sources Musicales - RISM took 134.6081681251526s
Accuracy | Check Inverse Functional Property for Répertoire International des Sources Musicales - RISM took 0.1026303768157959s
Accuracy | Check Empty annotation labels for Répertoire International des Sources Musicales - RISM took 12.433645248413086s
Accuracy | Check White space in annotation for Répertoire International des Sources Musicales - RISM took 2.375643014907837s
Accuracy | Check Datatype consistency for Répertoire International des Sources Musicales - RISM took 3.751575231552124s
Consistency | Disjoint class check for Répertoire International des Sources Musicales - RISM took 0.11013317108154297s
Consistency | Check Misplaced properties for Répertoire International des Sources Musicales - RISM took 46.75182008743286s
Consistency | Check Ontology hijacking for Répertoire International des Sources Musicales - RISM took 139.59723162651062s
Consistency | Check Invalid usage of undefined classes for Répertoire International des Sources Musicales - RISM took 1.4100079536437988s
Consistency | Check Invalid usage of undefined properties for Répertoire International des Sources Musicales - RISM took 48.143465518951416s
Conciseness | Check Extensional conciseness for Répertoire International des Sources Musicales - RISM took 2.745847702026367s
Security | Sign check for Répertoire International des Sources Musicales - RISM took 0.09392786026000977s
Availability | Check URIs Dereferenciability for Répertoire International des Sources Musicales - RISM took 1.4915533065795898s
Completeness | Calculation of interlinking completeness for Répertoire International des Sources Musicales - RISM took 0.34981727600097656s
Reputation | Calculation of the PageRank for Répertoire International des Sources Musicales - RISM took 0.02093982696533203s
Interlinking | Calculation of Degree of Connection for Répertoire International des Sources Musicales - RISM took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Répertoire International des Sources Musicales - RISM took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for Répertoire International des Sources Musicales - RISM took 5.340576171875e-05s
Interoperability | Check the re-using of existing vocabs for Répertoire International des Sources Musicales - RISM took 2.86102294921875e-06s
Believability | Calculation of trust value for Répertoire International des Sources Musicales - RISM took 1.0728836059570312e-05s
INFO | --- Analysis for rism took 2186.163146495819s
Availability | SPARQL endpoint availability check for RISM Authority data took 0.13108348846435547s
Availability | VoID file availability check for RISM Authority data took 0.0004749298095703125s
Extra | Recovery of all triples for RISM Authority data took 20.509243965148926s
Performance | Total latancy measurement for RISM Authority data took 0.4969947338104248s
Amount of data | Number of triples check for RISM Authority data took 54.76179242134094s
Interoperability | New terms check for RISM Authority data took 1.836134910583496s
Versatility | Languages check for RISM Authority data took 167.3922357559204s
Interpretability | Number of blank nodes check for RISM Authority data took 49.76709198951721s
Security | Check HTTPS for RISM Authority data took 135.07562351226807s
Interpretability | RDF structures check for RISM Authority data took 0.15229368209838867s
Versatility | Serialization formats check for RISM Authority data took 0.1285090446472168s
Availability | RDF dump link check for RISM Authority data took 0.1022636890411377s
License | MR license check for RISM Authority data took 0.09389925003051758s
License | HR license check for RISM Authority data took 300.01045393943787s
Amount of data | Number of property check for RISM Authority data took 0.13954520225524902s
Understandability | Number of label check for RISM Authority data took 142.9313883781433s
Understandability | URI regex check for RISM Authority data took 0.2621474266052246s
Understandability | Vocabs check for RISM Authority data took 0.10167455673217773s
Verifiability | Authors check for RISM Authority data took 0.10948753356933594s
Verifiability | Publishers check for RISM Authority data took 0.10853171348571777s
Performance | Throughput check for RISM Authority data took 10.59556794166565s
Amount of data | Check the number of entities for RISM Authority data took 7.009506225585938e-05s
Verifiability | Contribs. check for RISM Authority data took 0.10771465301513672s
Interlinking | sameAs chians check for RISM Authority data took 1.322889804840088s
Interlinking | skos check for RISM Authority data took 0.13808774948120117s
Interlinking | skos check for RISM Authority data took 0.10578012466430664s
Timeliness | dataset update frequency check for RISM Authority data took 0.10448884963989258s
Currency | Creation date check for RISM Authority data took 0.2348787784576416s
Currency | Modification date check for RISM Authority data took 0.24336600303649902s
Rep.Conc. | URIs length for RISM Authority data took 72.66318488121033s
Interoperability | New vocabularies check for RISM Authority data took 8.106231689453125e-06s
Consistency | Deprecated classes/propertiers check for RISM Authority data took 0.1380624771118164s
Accuracy | Check Functional Property for RISM Authority data took 133.7590250968933s
Accuracy | Check Inverse Functional Property for RISM Authority data took 0.11679887771606445s
Accuracy | Check Empty annotation labels for RISM Authority data took 16.39866542816162s
Accuracy | Check White space in annotation for RISM Authority data took 2.3650565147399902s
Accuracy | Check Datatype consistency for RISM Authority data took 3.7643706798553467s
Consistency | Disjoint class check for RISM Authority data took 0.0947113037109375s
Consistency | Check Misplaced properties for RISM Authority data took 45.74236798286438s
Consistency | Check Ontology hijacking for RISM Authority data took 4.423082113265991s
Consistency | Check Invalid usage of undefined classes for RISM Authority data took 1.346670150756836s
Consistency | Check Invalid usage of undefined properties for RISM Authority data took 182.77411770820618s
Conciseness | Check Extensional conciseness for RISM Authority data took 2.91153883934021s
Security | Sign check for RISM Authority data took 0.09377717971801758s
Availability | Check URIs Dereferenciability for RISM Authority data took 1.4683234691619873s
Completeness | Calculation of interlinking completeness for RISM Authority data took 0.3321957588195801s
Reputation | Calculation of the PageRank for RISM Authority data took 0.021759033203125s
Interlinking | Calculation of Degree of Connection for RISM Authority data took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for RISM Authority data took 0.0008490085601806641s
Interlinking | Calculation of Clustering coefficient for RISM Authority data took 5.269050598144531e-05s
Interoperability | Check the re-using of existing vocabs for RISM Authority data took 3.0994415283203125e-06s
Believability | Calculation of trust value for RISM Authority data took 7.3909759521484375e-06s
INFO | --- Analysis for rism-authorities took 2056.5058465003967s
Availability | SPARQL endpoint availability check for engineering equipment ontology took 8.344650268554688e-05s
Availability | VoID file availability check for engineering equipment ontology took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for engineering equipment ontology took 0.19100522994995117s
Reputation | Calculation of the PageRank for engineering equipment ontology took 0.02039051055908203s
Interlinking | Calculation of Degree of Connection for engineering equipment ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for engineering equipment ontology took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for engineering equipment ontology took 3.075599670410156e-05s
Believability | Calculation of trust value for engineering equipment ontology took 1.0728836059570312e-05s
INFO | --- Analysis for rk took 1.9962520599365234s
Availability | SPARQL endpoint availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 8.177757263183594e-05s
Availability | VoID file availability check for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for Association for Computing Machinery (ACM) (RKBExplorer) took 0.17824673652648926s
Reputation | Calculation of the PageRank for Association for Computing Machinery (ACM) (RKBExplorer) took 0.02098536491394043s
Interlinking | Calculation of Degree of Connection for Association for Computing Machinery (ACM) (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Association for Computing Machinery (ACM) (RKBExplorer) took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for Association for Computing Machinery (ACM) (RKBExplorer) took 0.000225067138671875s
Believability | Calculation of trust value for Association for Computing Machinery (ACM) (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-acm took 1.9773733615875244s
Availability | SPARQL endpoint availability check for Budapest University of Technology and Economics (RKBExplorer) took 4.1484832763671875e-05s
Availability | VoID file availability check for Budapest University of Technology and Economics (RKBExplorer) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Budapest University of Technology and Economics (RKBExplorer) took 0.18253827095031738s
Reputation | Calculation of the PageRank for Budapest University of Technology and Economics (RKBExplorer) took 0.02145552635192871s
Interlinking | Calculation of Degree of Connection for Budapest University of Technology and Economics (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Budapest University of Technology and Economics (RKBExplorer) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Budapest University of Technology and Economics (RKBExplorer) took 0.0001354217529296875s
Believability | Calculation of trust value for Budapest University of Technology and Economics (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-budapest took 2.0095436573028564s
Availability | SPARQL endpoint availability check for CiteSeer (Research Index) (RKBExplorer) took 4.00543212890625e-05s
Availability | VoID file availability check for CiteSeer (Research Index) (RKBExplorer) took 0.0004870891571044922s
Completeness | Calculation of interlinking completeness for CiteSeer (Research Index) (RKBExplorer) took 0.17960381507873535s
Reputation | Calculation of the PageRank for CiteSeer (Research Index) (RKBExplorer) took 0.02061605453491211s
Interlinking | Calculation of Degree of Connection for CiteSeer (Research Index) (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for CiteSeer (Research Index) (RKBExplorer) took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for CiteSeer (Research Index) (RKBExplorer) took 0.00019431114196777344s
Believability | Calculation of trust value for CiteSeer (Research Index) (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-citeseer took 1.9877145290374756s
Availability | SPARQL endpoint availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.17920374870300293s
Reputation | Calculation of the PageRank for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.022329092025756836s
Interlinking | Calculation of Degree of Connection for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Community R&D Information Service (CORDIS) (RKBExplorer) took 0.0001533031463623047s
Believability | Calculation of trust value for Community R&D Information Service (CORDIS) (RKBExplorer) took 1.8835067749023438e-05s
INFO | --- Analysis for rkb-explorer-cordis took 1.9949719905853271s
Availability | SPARQL endpoint availability check for Resilient Computing Courseware (RKBExplorer) took 8.0108642578125e-05s
Availability | VoID file availability check for Resilient Computing Courseware (RKBExplorer) took 0.0004916191101074219s
Completeness | Calculation of interlinking completeness for Resilient Computing Courseware (RKBExplorer) took 0.20323467254638672s
Reputation | Calculation of the PageRank for Resilient Computing Courseware (RKBExplorer) took 0.022753238677978516s
Interlinking | Calculation of Degree of Connection for Resilient Computing Courseware (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Resilient Computing Courseware (RKBExplorer) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Resilient Computing Courseware (RKBExplorer) took 0.00015592575073242188s
Believability | Calculation of trust value for Resilient Computing Courseware (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-courseware took 2.029644250869751s
Availability | SPARQL endpoint availability check for Street level crime reports for England and Wales took 8.177757263183594e-05s
Availability | VoID file availability check for Street level crime reports for England and Wales took 0.0004742145538330078s
Completeness | Calculation of interlinking completeness for Street level crime reports for England and Wales took 0.17533564567565918s
Reputation | Calculation of the PageRank for Street level crime reports for England and Wales took 0.020572423934936523s
Interlinking | Calculation of Degree of Connection for Street level crime reports for England and Wales took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Street level crime reports for England and Wales took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for Street level crime reports for England and Wales took 3.695487976074219e-05s
Believability | Calculation of trust value for Street level crime reports for England and Wales took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-crime took 1.9664461612701416s
Availability | SPARQL endpoint availability check for crm took 8.559226989746094e-05s
Availability | VoID file availability check for crm took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for crm took 0.18532228469848633s
Reputation | Calculation of the PageRank for crm took 0.0201871395111084s
Interlinking | Calculation of Degree of Connection for crm took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for crm took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for crm took 2.8371810913085938e-05s
Believability | Calculation of trust value for crm took 1.4781951904296875e-05s
INFO | --- Analysis for rkb-explorer-crm took 1.9861772060394287s
Availability | SPARQL endpoint availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 7.843971252441406e-05s
Availability | VoID file availability check for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0005023479461669922s
Completeness | Calculation of interlinking completeness for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.18964338302612305s
Reputation | Calculation of the PageRank for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.02033853530883789s
Interlinking | Calculation of Degree of Connection for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 0.00011777877807617188s
Believability | Calculation of trust value for ReSIST MSc in Resilient Computing Curriculum (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-curriculum took 1.9843261241912842s
Availability | SPARQL endpoint availability check for Technische Universität Darmstadt (RKBExplorer) took 4.315376281738281e-05s
Availability | VoID file availability check for Technische Universität Darmstadt (RKBExplorer) took 0.00025963783264160156s
Completeness | Calculation of interlinking completeness for Technische Universität Darmstadt (RKBExplorer) took 0.17910504341125488s
Reputation | Calculation of the PageRank for Technische Universität Darmstadt (RKBExplorer) took 0.020334959030151367s
Interlinking | Calculation of Degree of Connection for Technische Universität Darmstadt (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Technische Universität Darmstadt (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Technische Universität Darmstadt (RKBExplorer) took 5.173683166503906e-05s
Believability | Calculation of trust value for Technische Universität Darmstadt (RKBExplorer) took 1.3589859008789062e-05s
INFO | --- Analysis for rkb-explorer-darmstadt took 1.9947755336761475s
Availability | SPARQL endpoint availability check for DBLP Computer Science Bibliography (RKBExplorer) took 3.981590270996094e-05s
Availability | VoID file availability check for DBLP Computer Science Bibliography (RKBExplorer) took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for DBLP Computer Science Bibliography (RKBExplorer) took 0.17351198196411133s
Reputation | Calculation of the PageRank for DBLP Computer Science Bibliography (RKBExplorer) took 0.021391630172729492s
Interlinking | Calculation of Degree of Connection for DBLP Computer Science Bibliography (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DBLP Computer Science Bibliography (RKBExplorer) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for DBLP Computer Science Bibliography (RKBExplorer) took 0.00023174285888671875s
Believability | Calculation of trust value for DBLP Computer Science Bibliography (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-dblp took 1.9613428115844727s
Availability | SPARQL endpoint availability check for Deep Blue (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for Deep Blue (RKBExplorer) took 0.0002117156982421875s
Completeness | Calculation of interlinking completeness for Deep Blue (RKBExplorer) took 0.17153120040893555s
Reputation | Calculation of the PageRank for Deep Blue (RKBExplorer) took 0.02227306365966797s
Interlinking | Calculation of Degree of Connection for Deep Blue (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Deep Blue (RKBExplorer) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Deep Blue (RKBExplorer) took 7.390975952148438e-05s
Believability | Calculation of trust value for Deep Blue (RKBExplorer) took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-deepblue took 1.9640498161315918s
Availability | SPARQL endpoint availability check for DEPLOY (RKBExplorer) took 9.250640869140625e-05s
Availability | VoID file availability check for DEPLOY (RKBExplorer) took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for DEPLOY (RKBExplorer) took 0.17705583572387695s
Reputation | Calculation of the PageRank for DEPLOY (RKBExplorer) took 0.020482301712036133s
Interlinking | Calculation of Degree of Connection for DEPLOY (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for DEPLOY (RKBExplorer) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for DEPLOY (RKBExplorer) took 9.250640869140625e-05s
Believability | Calculation of trust value for DEPLOY (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-deploy took 1.9750475883483887s
Availability | SPARQL endpoint availability check for digitaleconomy took 4.1961669921875e-05s
Availability | VoID file availability check for digitaleconomy took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for digitaleconomy took 0.17246127128601074s
Reputation | Calculation of the PageRank for digitaleconomy took 0.020468711853027344s
Interlinking | Calculation of Degree of Connection for digitaleconomy took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for digitaleconomy took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for digitaleconomy took 2.8848648071289062e-05s
Believability | Calculation of trust value for digitaleconomy took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-digitaleconomy took 1.9678726196289062s
Availability | SPARQL endpoint availability check for dotAC (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for dotAC (RKBExplorer) took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for dotAC (RKBExplorer) took 0.18026423454284668s
Reputation | Calculation of the PageRank for dotAC (RKBExplorer) took 0.020452022552490234s
Interlinking | Calculation of Degree of Connection for dotAC (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for dotAC (RKBExplorer) took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for dotAC (RKBExplorer) took 0.00014448165893554688s
Believability | Calculation of trust value for dotAC (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-dotac took 1.9793355464935303s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton took 8.153915405273438e-05s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton took 0.17829585075378418s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton took 0.020284652709960938s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton took 4.601478576660156e-05s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-ecs took 2.021899461746216s
Availability | SPARQL endpoint availability check for enaktingpsi took 3.981590270996094e-05s
Availability | VoID file availability check for enaktingpsi took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for enaktingpsi took 0.1869792938232422s
Reputation | Calculation of the PageRank for enaktingpsi took 0.021387338638305664s
Interlinking | Calculation of Degree of Connection for enaktingpsi took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for enaktingpsi took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for enaktingpsi took 2.8133392333984375e-05s
Believability | Calculation of trust value for enaktingpsi took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-enaktingpsi took 2.0430641174316406s
Availability | SPARQL endpoint availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 4.220008850097656e-05s
Availability | VoID file availability check for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.0004673004150390625s
Completeness | Calculation of interlinking completeness for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.1719658374786377s
Reputation | Calculation of the PageRank for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.02065873146057129s
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.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for ePrints3 Institutional Archive Collection (RKBExplorer) took 0.00017404556274414062s
Believability | Calculation of trust value for ePrints3 Institutional Archive Collection (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-eprints took 1.9961514472961426s
Availability | SPARQL endpoint availability check for epsrc took 0.00010704994201660156s
Availability | VoID file availability check for epsrc took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for epsrc took 0.18261122703552246s
Reputation | Calculation of the PageRank for epsrc took 0.02023029327392578s
Interlinking | Calculation of Degree of Connection for epsrc took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for epsrc took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for epsrc took 5.602836608886719e-05s
Believability | Calculation of trust value for epsrc took 7.152557373046875e-06s
INFO | --- Analysis for rkb-explorer-epsrc took 1.967862844467163s
Availability | SPARQL endpoint availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 6.222724914550781e-05s
Availability | VoID file availability check for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.17269134521484375s
Reputation | Calculation of the PageRank for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.021570444107055664s
Interlinking | Calculation of Degree of Connection for ERA - Australian Research Council publication ratings (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ERA - Australian Research Council publication ratings (RKBExplorer) took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for ERA - Australian Research Council publication ratings (RKBExplorer) took 8.20159912109375e-05s
Believability | Calculation of trust value for ERA - Australian Research Council publication ratings (RKBExplorer) took 6.9141387939453125e-06s
INFO | --- Analysis for rkb-explorer-era took 1.9575481414794922s
Availability | SPARQL endpoint availability check for Institut Eurécom (RKBExplorer) took 0.000110626220703125s
Availability | VoID file availability check for Institut Eurécom (RKBExplorer) took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for Institut Eurécom (RKBExplorer) took 0.18732738494873047s
Reputation | Calculation of the PageRank for Institut Eurécom (RKBExplorer) took 0.02042388916015625s
Interlinking | Calculation of Degree of Connection for Institut Eurécom (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Institut Eurécom (RKBExplorer) took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for Institut Eurécom (RKBExplorer) took 0.00010013580322265625s
Believability | Calculation of trust value for Institut Eurécom (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-eurecom took 1.9963278770446777s
Availability | SPARQL endpoint availability check for rkb-explorer-foreign took 3.981590270996094e-05s
Availability | VoID file availability check for rkb-explorer-foreign took 0.0005528926849365234s
Completeness | Calculation of interlinking completeness for rkb-explorer-foreign took 0.17931079864501953s
Reputation | Calculation of the PageRank for rkb-explorer-foreign took 0.020250558853149414s
Interlinking | Calculation of Degree of Connection for rkb-explorer-foreign took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for rkb-explorer-foreign took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for rkb-explorer-foreign took 3.409385681152344e-05s
Believability | Calculation of trust value for rkb-explorer-foreign took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-foreign took 1.9548695087432861s
Availability | SPARQL endpoint availability check for France Telecom Recherche et Développement (RKBExplorer) took 5.1975250244140625e-05s
Availability | VoID file availability check for France Telecom Recherche et Développement (RKBExplorer) took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for France Telecom Recherche et Développement (RKBExplorer) took 0.17775607109069824s
Reputation | Calculation of the PageRank for France Telecom Recherche et Développement (RKBExplorer) took 0.02012920379638672s
Interlinking | Calculation of Degree of Connection for France Telecom Recherche et Développement (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for France Telecom Recherche et Développement (RKBExplorer) took 0.0007431507110595703s
Interlinking | Calculation of Clustering coefficient for France Telecom Recherche et Développement (RKBExplorer) took 8.7738037109375e-05s
Believability | Calculation of trust value for France Telecom Recherche et Développement (RKBExplorer) took 7.62939453125e-06s
INFO | --- Analysis for rkb-explorer-ft took 1.9876718521118164s
Availability | SPARQL endpoint availability check for fun took 5.0067901611328125e-05s
Availability | VoID file availability check for fun took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for fun took 0.17534732818603516s
Reputation | Calculation of the PageRank for fun took 0.020916223526000977s
Interlinking | Calculation of Degree of Connection for fun took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for fun took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for fun took 7.271766662597656e-05s
Believability | Calculation of trust value for fun took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-fun took 2.0295557975769043s
Availability | SPARQL endpoint availability check for gdlc took 3.9577484130859375e-05s
Availability | VoID file availability check for gdlc took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for gdlc took 0.18428993225097656s
Reputation | Calculation of the PageRank for gdlc took 0.020404815673828125s
Interlinking | Calculation of Degree of Connection for gdlc took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for gdlc took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for gdlc took 6.842613220214844e-05s
Believability | Calculation of trust value for gdlc took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-gdlc took 2.141528844833374s
Availability | SPARQL endpoint availability check for IBM Research GmbH (RKBExplorer) took 5.984306335449219e-05s
Availability | VoID file availability check for IBM Research GmbH (RKBExplorer) took 0.00044918060302734375s
Completeness | Calculation of interlinking completeness for IBM Research GmbH (RKBExplorer) took 0.18055272102355957s
Reputation | Calculation of the PageRank for IBM Research GmbH (RKBExplorer) took 0.020360946655273438s
Interlinking | Calculation of Degree of Connection for IBM Research GmbH (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for IBM Research GmbH (RKBExplorer) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for IBM Research GmbH (RKBExplorer) took 0.00011205673217773438s
Believability | Calculation of trust value for IBM Research GmbH (RKBExplorer) took 9.775161743164062e-06s
INFO | --- Analysis for rkb-explorer-ibm took 1.9813766479492188s
Availability | SPARQL endpoint availability check for IEEE Papers (RKBExplorer) took 9.465217590332031e-05s
Availability | VoID file availability check for IEEE Papers (RKBExplorer) took 0.00046515464782714844s
Completeness | Calculation of interlinking completeness for IEEE Papers (RKBExplorer) took 0.18156743049621582s
Reputation | Calculation of the PageRank for IEEE Papers (RKBExplorer) took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for IEEE Papers (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IEEE Papers (RKBExplorer) took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for IEEE Papers (RKBExplorer) took 0.0001316070556640625s
Believability | Calculation of trust value for IEEE Papers (RKBExplorer) took 1.0251998901367188e-05s
INFO | --- Analysis for rkb-explorer-ieee took 1.9570024013519287s
Availability | SPARQL endpoint availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00013637542724609375s
Availability | VoID file availability check for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.17489933967590332s
Reputation | Calculation of the PageRank for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0203857421875s
Interlinking | Calculation of Degree of Connection for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0007374286651611328s
Interlinking | Calculation of Clustering coefficient for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 0.0001404285430908203s
Believability | Calculation of trust value for Université Paul Sabatier - Toulouse 3 (RKB Explorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-irit took 1.9841070175170898s
Availability | SPARQL endpoint availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 7.987022399902344e-05s
Availability | VoID file availability check for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.18165087699890137s
Reputation | Calculation of the PageRank for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.020227909088134766s
Interlinking | Calculation of Degree of Connection for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 6.222724914550781e-05s
Believability | Calculation of trust value for Diverse Italian ReSIST Partner Institutions (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-italy took 2.022141933441162s
Availability | SPARQL endpoint availability check for UK JISC (RKBExplorer) took 8.153915405273438e-05s
Availability | VoID file availability check for UK JISC (RKBExplorer) took 0.00043272972106933594s
Completeness | Calculation of interlinking completeness for UK JISC (RKBExplorer) took 0.1743946075439453s
Reputation | Calculation of the PageRank for UK JISC (RKBExplorer) took 0.02058720588684082s
Interlinking | Calculation of Degree of Connection for UK JISC (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for UK JISC (RKBExplorer) took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for UK JISC (RKBExplorer) took 7.295608520507812e-05s
Believability | Calculation of trust value for UK JISC (RKBExplorer) took 1.430511474609375e-05s
INFO | --- Analysis for rkb-explorer-jisc took 2.004992723464966s
Availability | SPARQL endpoint availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 8.058547973632812e-05s
Availability | VoID file availability check for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.00025653839111328125s
Completeness | Calculation of interlinking completeness for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.17626476287841797s
Reputation | Calculation of the PageRank for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.022274255752563477s
Interlinking | Calculation of Degree of Connection for Vytautas Magnus University, Kaunas (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Vytautas Magnus University, Kaunas (RKBExplorer) took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Vytautas Magnus University, Kaunas (RKBExplorer) took 4.673004150390625e-05s
Believability | Calculation of trust value for Vytautas Magnus University, Kaunas (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-kaunas took 2.004246950149536s
Availability | SPARQL endpoint availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 8.034706115722656e-05s
Availability | VoID file availability check for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for Korean Institute of Science Technology and Information (RKBExplorer) took 0.1792740821838379s
Reputation | Calculation of the PageRank for Korean Institute of Science Technology and Information (RKBExplorer) took 0.021191835403442383s
Interlinking | Calculation of Degree of Connection for Korean Institute of Science Technology and Information (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Korean Institute of Science Technology and Information (RKBExplorer) took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Korean Institute of Science Technology and Information (RKBExplorer) took 0.00016236305236816406s
Believability | Calculation of trust value for Korean Institute of Science Technology and Information (RKBExplorer) took 1.0967254638671875e-05s
INFO | --- Analysis for rkb-explorer-kisti took 1.9919028282165527s
Availability | SPARQL endpoint availability check for LAAS-CNRS (RKBExplorer) took 0.00015115737915039062s
Availability | VoID file availability check for LAAS-CNRS (RKBExplorer) took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for LAAS-CNRS (RKBExplorer) took 0.1752619743347168s
Reputation | Calculation of the PageRank for LAAS-CNRS (RKBExplorer) took 0.022418498992919922s
Interlinking | Calculation of Degree of Connection for LAAS-CNRS (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for LAAS-CNRS (RKBExplorer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for LAAS-CNRS (RKBExplorer) took 0.0001461505889892578s
Believability | Calculation of trust value for LAAS-CNRS (RKBExplorer) took 5.7220458984375e-06s
INFO | --- Analysis for rkb-explorer-laas took 1.9655041694641113s
Availability | SPARQL endpoint availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 4.124641418457031e-05s
Availability | VoID file availability check for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0005147457122802734s
Completeness | Calculation of interlinking completeness for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.17885327339172363s
Reputation | Calculation of the PageRank for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 6.413459777832031e-05s
Believability | Calculation of trust value for Fundação da Faculdade de Ciencas da Universidade de Lisboa (RKBExplorer) took 1.1205673217773438e-05s
INFO | --- Analysis for rkb-explorer-lisbon took 2.0180869102478027s
Availability | SPARQL endpoint availability check for University of Newcastle upon Tyne (RKBExplorer) took 3.9577484130859375e-05s
Availability | VoID file availability check for University of Newcastle upon Tyne (RKBExplorer) took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for University of Newcastle upon Tyne (RKBExplorer) took 0.1845409870147705s
Reputation | Calculation of the PageRank for University of Newcastle upon Tyne (RKBExplorer) took 0.020525455474853516s
Interlinking | Calculation of Degree of Connection for University of Newcastle upon Tyne (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for University of Newcastle upon Tyne (RKBExplorer) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for University of Newcastle upon Tyne (RKBExplorer) took 0.0001556873321533203s
Believability | Calculation of trust value for University of Newcastle upon Tyne (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-newcastle took 1.9879264831542969s
Availability | SPARQL endpoint availability check for notube took 4.100799560546875e-05s
Availability | VoID file availability check for notube took 0.0002110004425048828s
Completeness | Calculation of interlinking completeness for notube took 0.1755692958831787s
Reputation | Calculation of the PageRank for notube took 0.021167755126953125s
Interlinking | Calculation of Degree of Connection for notube took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for notube took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for notube took 4.1961669921875e-05s
Believability | Calculation of trust value for notube took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-notube took 1.9820582866668701s
Availability | SPARQL endpoint availability check for National Science Foundation (RKBExplorer) took 4.1961669921875e-05s
Availability | VoID file availability check for National Science Foundation (RKBExplorer) took 0.0010573863983154297s
Completeness | Calculation of interlinking completeness for National Science Foundation (RKBExplorer) took 0.1861107349395752s
Reputation | Calculation of the PageRank for National Science Foundation (RKBExplorer) took 0.02409219741821289s
Interlinking | Calculation of Degree of Connection for National Science Foundation (RKBExplorer) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for National Science Foundation (RKBExplorer) took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for National Science Foundation (RKBExplorer) took 0.00013136863708496094s
Believability | Calculation of trust value for National Science Foundation (RKBExplorer) took 1.2636184692382812e-05s
INFO | --- Analysis for rkb-explorer-nsf took 2.023709297180176s
Availability | SPARQL endpoint availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 4.38690185546875e-05s
Availability | VoID file availability check for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.17404460906982422s
Reputation | Calculation of the PageRank for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.02033829689025879s
Interlinking | Calculation of Degree of Connection for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.0007662773132324219s
Interlinking | Calculation of Clustering coefficient for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 0.000156402587890625s
Believability | Calculation of trust value for Open Archive Initiative Harvest over OAI-PMH (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-oai took 1.9920704364776611s
Availability | SPARQL endpoint availability check for OpenCyc (RKBExplorer) took 4.029273986816406e-05s
Availability | VoID file availability check for OpenCyc (RKBExplorer) took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for OpenCyc (RKBExplorer) took 0.18233537673950195s
Reputation | Calculation of the PageRank for OpenCyc (RKBExplorer) took 0.02046060562133789s
Interlinking | Calculation of Degree of Connection for OpenCyc (RKBExplorer) took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for OpenCyc (RKBExplorer) took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for OpenCyc (RKBExplorer) took 2.86102294921875e-05s
Believability | Calculation of trust value for OpenCyc (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-opencyc took 2.0093066692352295s
Availability | SPARQL endpoint availability check for Ordnance Survey (RKBExplorer) took 8.034706115722656e-05s
Availability | VoID file availability check for Ordnance Survey (RKBExplorer) took 0.0004336833953857422s
Completeness | Calculation of interlinking completeness for Ordnance Survey (RKBExplorer) took 0.174699068069458s
Reputation | Calculation of the PageRank for Ordnance Survey (RKBExplorer) took 0.021006345748901367s
Interlinking | Calculation of Degree of Connection for Ordnance Survey (RKBExplorer) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Ordnance Survey (RKBExplorer) took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Ordnance Survey (RKBExplorer) took 7.081031799316406e-05s
Believability | Calculation of trust value for Ordnance Survey (RKBExplorer) took 1.0728836059570312e-05s
INFO | --- Analysis for rkb-explorer-os took 1.9687116146087646s
Availability | SPARQL endpoint availability check for photos took 7.939338684082031e-05s
Availability | VoID file availability check for photos took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for photos took 0.18155813217163086s
Reputation | Calculation of the PageRank for photos took 0.022238492965698242s
Interlinking | Calculation of Degree of Connection for photos took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for photos took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for photos took 7.033348083496094e-05s
Believability | Calculation of trust value for photos took 1.049041748046875e-05s
INFO | --- Analysis for rkb-explorer-photos took 1.9754915237426758s
Availability | SPARQL endpoint availability check for Università di Pisa (RKBExplorer) took 4.100799560546875e-05s
Availability | VoID file availability check for Università di Pisa (RKBExplorer) took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Università di Pisa (RKBExplorer) took 0.1817636489868164s
Reputation | Calculation of the PageRank for Università di Pisa (RKBExplorer) took 0.02272510528564453s
Interlinking | Calculation of Degree of Connection for Università di Pisa (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Università di Pisa (RKBExplorer) took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Università di Pisa (RKBExplorer) took 0.00012040138244628906s
Believability | Calculation of trust value for Università di Pisa (RKBExplorer) took 1.0013580322265625e-05s
INFO | --- Analysis for rkb-explorer-pisa took 1.985966444015503s
Availability | SPARQL endpoint availability check for Research Assessment Exercise 2001 (RKBExplorer) took 4.00543212890625e-05s
Availability | VoID file availability check for Research Assessment Exercise 2001 (RKBExplorer) took 0.00048470497131347656s
Completeness | Calculation of interlinking completeness for Research Assessment Exercise 2001 (RKBExplorer) took 0.17923450469970703s
Reputation | Calculation of the PageRank for Research Assessment Exercise 2001 (RKBExplorer) took 0.020417451858520508s
Interlinking | Calculation of Degree of Connection for Research Assessment Exercise 2001 (RKBExplorer) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Research Assessment Exercise 2001 (RKBExplorer) took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Research Assessment Exercise 2001 (RKBExplorer) took 0.00019121170043945312s
Believability | Calculation of trust value for Research Assessment Exercise 2001 (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-rae2001 took 1.967606544494629s
Availability | SPARQL endpoint availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.00010704994201660156s
Availability | VoID file availability check for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.18310260772705078s
Reputation | Calculation of the PageRank for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.020710229873657227s
Interlinking | Calculation of Degree of Connection for ReSIST Resilience Mechanisms (RKBExplorer.com) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for ReSIST Resilience Mechanisms (RKBExplorer.com) took 0.0001373291015625s
Believability | Calculation of trust value for ReSIST Resilience Mechanisms (RKBExplorer.com) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-resex took 1.9630343914031982s
Availability | SPARQL endpoint availability check for RISKS Digest (RKBExplorer) took 4.076957702636719e-05s
Availability | VoID file availability check for RISKS Digest (RKBExplorer) took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for RISKS Digest (RKBExplorer) took 0.19041776657104492s
Reputation | Calculation of the PageRank for RISKS Digest (RKBExplorer) took 0.020665884017944336s
Interlinking | Calculation of Degree of Connection for RISKS Digest (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for RISKS Digest (RKBExplorer) took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for RISKS Digest (RKBExplorer) took 9.107589721679688e-05s
Believability | Calculation of trust value for RISKS Digest (RKBExplorer) took 1.1682510375976562e-05s
INFO | --- Analysis for rkb-explorer-risks took 2.0439422130584717s
Availability | SPARQL endpoint availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 8.082389831542969e-05s
Availability | VoID file availability check for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.17865872383117676s
Reputation | Calculation of the PageRank for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.020381450653076172s
Interlinking | Calculation of Degree of Connection for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 0.00012803077697753906s
Believability | Calculation of trust value for Università degli studi di Roma "La Sapienza" (RKBExplorer) took 1.2874603271484375e-05s
INFO | --- Analysis for rkb-explorer-roma took 1.9829111099243164s
Availability | SPARQL endpoint availability check for roni took 4.601478576660156e-05s
Availability | VoID file availability check for roni took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for roni took 0.17198753356933594s
Reputation | Calculation of the PageRank for roni took 0.020435094833374023s
Interlinking | Calculation of Degree of Connection for roni took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for roni took 0.0007679462432861328s
Interlinking | Calculation of Clustering coefficient for roni took 2.8848648071289062e-05s
Believability | Calculation of trust value for roni took 1.239776611328125e-05s
INFO | --- Analysis for rkb-explorer-roni took 1.9510412216186523s
Availability | SPARQL endpoint availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00012445449829101562s
Availability | VoID file availability check for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0004589557647705078s
Completeness | Calculation of interlinking completeness for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.17937755584716797s
Reputation | Calculation of the PageRank for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.02043914794921875s
Interlinking | Calculation of Degree of Connection for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.0006959438323974609s
Interlinking | Calculation of Clustering coefficient for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 0.00021696090698242188s
Believability | Calculation of trust value for School of Electronics and Computer Science, University of Southampton (RKBExplorer) took 1.3113021850585938e-05s
INFO | --- Analysis for rkb-explorer-southampton took 2.094473123550415s
Availability | SPARQL endpoint availability check for Universität Ulm (RKBExplorer) took 4.291534423828125e-05s
Availability | VoID file availability check for Universität Ulm (RKBExplorer) took 0.00023603439331054688s
Completeness | Calculation of interlinking completeness for Universität Ulm (RKBExplorer) took 0.17973661422729492s
Reputation | Calculation of the PageRank for Universität Ulm (RKBExplorer) took 0.020311832427978516s
Interlinking | Calculation of Degree of Connection for Universität Ulm (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universität Ulm (RKBExplorer) took 0.0007090568542480469s
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 1.9516613483428955s
Availability | SPARQL endpoint availability check for UN/LOCODE (RKBExplorer) took 3.981590270996094e-05s
Availability | VoID file availability check for UN/LOCODE (RKBExplorer) took 0.00022673606872558594s
Completeness | Calculation of interlinking completeness for UN/LOCODE (RKBExplorer) took 0.1753847599029541s
Reputation | Calculation of the PageRank for UN/LOCODE (RKBExplorer) took 0.020357370376586914s
Interlinking | Calculation of Degree of Connection for UN/LOCODE (RKBExplorer) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UN/LOCODE (RKBExplorer) took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for UN/LOCODE (RKBExplorer) took 9.632110595703125e-05s
Believability | Calculation of trust value for UN/LOCODE (RKBExplorer) took 8.106231689453125e-06s
INFO | --- Analysis for rkb-explorer-unlocode took 1.9389739036560059s
Availability | SPARQL endpoint availability check for webconf took 8.20159912109375e-05s
Availability | VoID file availability check for webconf took 0.0004749298095703125s
Completeness | Calculation of interlinking completeness for webconf took 0.1814265251159668s
Reputation | Calculation of the PageRank for webconf took 0.021036863327026367s
Interlinking | Calculation of Degree of Connection for webconf took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for webconf took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for webconf took 0.00010156631469726562s
Believability | Calculation of trust value for webconf took 1.1920928955078125e-05s
INFO | --- Analysis for rkb-explorer-webconf took 1.9824104309082031s
Availability | SPARQL endpoint availability check for Web Science Conference (RKBExplorer) took 8.392333984375e-05s
Availability | VoID file availability check for Web Science Conference (RKBExplorer) took 0.00046443939208984375s
Completeness | Calculation of interlinking completeness for Web Science Conference (RKBExplorer) took 0.1872878074645996s
Reputation | Calculation of the PageRank for Web Science Conference (RKBExplorer) took 0.020494461059570312s
Interlinking | Calculation of Degree of Connection for Web Science Conference (RKBExplorer) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Web Science Conference (RKBExplorer) took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Web Science Conference (RKBExplorer) took 6.604194641113281e-05s
Believability | Calculation of trust value for Web Science Conference (RKBExplorer) took 1.2159347534179688e-05s
INFO | --- Analysis for rkb-explorer-webscience took 1.9611306190490723s
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.00025272369384765625s
Completeness | Calculation of interlinking completeness for ReSIST Project Wiki (RKBExplorer) took 0.17186713218688965s
Reputation | Calculation of the PageRank for ReSIST Project Wiki (RKBExplorer) took 0.020222902297973633s
Interlinking | Calculation of Degree of Connection for ReSIST Project Wiki (RKBExplorer) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for ReSIST Project Wiki (RKBExplorer) took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for ReSIST Project Wiki (RKBExplorer) took 0.00019931793212890625s
Believability | Calculation of trust value for ReSIST Project Wiki (RKBExplorer) took 7.867813110351562e-06s
INFO | --- Analysis for rkb-explorer-wiki took 1.9451889991760254s
Availability | SPARQL endpoint availability check for WordNet (RKBExplorer) took 5.888938903808594e-05s
Availability | VoID file availability check for WordNet (RKBExplorer) took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for WordNet (RKBExplorer) took 0.17298245429992676s
Reputation | Calculation of the PageRank for WordNet (RKBExplorer) took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for WordNet (RKBExplorer) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for WordNet (RKBExplorer) took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for WordNet (RKBExplorer) took 9.012222290039062e-05s
Believability | Calculation of trust value for WordNet (RKBExplorer) took 1.33514404296875e-05s
INFO | --- Analysis for rkb-explorer-wordnet took 1.9673645496368408s
Availability | SPARQL endpoint availability check for RKB Explorer Data took 0.00010728836059570312s
Availability | VoID file availability check for RKB Explorer Data took 0.000209808349609375s
Completeness | Calculation of interlinking completeness for RKB Explorer Data took 0.1834874153137207s
Reputation | Calculation of the PageRank for RKB Explorer Data took 0.0207366943359375s
Interlinking | Calculation of Degree of Connection for RKB Explorer Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for RKB Explorer Data took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for RKB Explorer Data took 3.0517578125e-05s
Believability | Calculation of trust value for RKB Explorer Data took 1.1920928955078125e-05s
INFO | --- Analysis for rkb_explorer_data took 2.0008888244628906s
Availability | SPARQL endpoint availability check for ROCEEH Out of Africa Database (ROAD) took 0.44620609283447266s
Availability | VoID file availability check for ROCEEH Out of Africa Database (ROAD) took 0.00043511390686035156s
Completeness | Calculation of interlinking completeness for ROCEEH Out of Africa Database (ROAD) took 0.18517184257507324s
Reputation | Calculation of the PageRank for ROCEEH Out of Africa Database (ROAD) took 0.022313356399536133s
Interlinking | Calculation of Degree of Connection for ROCEEH Out of Africa Database (ROAD) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for ROCEEH Out of Africa Database (ROAD) took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for ROCEEH Out of Africa Database (ROAD) took 7.581710815429688e-05s
Believability | Calculation of trust value for ROCEEH Out of Africa Database (ROAD) took 1.1682510375976562e-05s
INFO | --- Analysis for roceeh-road took 3.2054760456085205s
Availability | SPARQL endpoint availability check for The Rosetta Project took 8.463859558105469e-05s
Availability | VoID file availability check for The Rosetta Project took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for The Rosetta Project took 0.1807105541229248s
Reputation | Calculation of the PageRank for The Rosetta Project took 0.02034902572631836s
Interlinking | Calculation of Degree of Connection for The Rosetta Project took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Rosetta Project took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for The Rosetta Project took 2.8848648071289062e-05s
Believability | Calculation of trust value for The Rosetta Project took 1.1682510375976562e-05s
INFO | --- Analysis for rosetta-project took 1.9926409721374512s
Availability | SPARQL endpoint availability check for ontology terrorist attack took 8.344650268554688e-05s
Availability | VoID file availability check for ontology terrorist attack took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for ontology terrorist attack took 0.17473340034484863s
Reputation | Calculation of the PageRank for ontology terrorist attack took 0.02017521858215332s
Interlinking | Calculation of Degree of Connection for ontology terrorist attack took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ontology terrorist attack took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for ontology terrorist attack took 2.7418136596679688e-05s
Believability | Calculation of trust value for ontology terrorist attack took 1.1444091796875e-05s
INFO | --- Analysis for ROSHANI took 1.9641456604003906s
Availability | SPARQL endpoint availability check for TERRORIST ATTACK ONTOLOGY took 8.273124694824219e-05s
Availability | VoID file availability check for TERRORIST ATTACK ONTOLOGY took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for TERRORIST ATTACK ONTOLOGY took 0.1775667667388916s
Reputation | Calculation of the PageRank for TERRORIST ATTACK ONTOLOGY took 0.02019524574279785s
Interlinking | Calculation of Degree of Connection for TERRORIST ATTACK ONTOLOGY took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TERRORIST ATTACK ONTOLOGY took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for TERRORIST ATTACK ONTOLOGY took 2.9802322387695312e-05s
Believability | Calculation of trust value for TERRORIST ATTACK ONTOLOGY took 1.1444091796875e-05s
INFO | --- Analysis for ROSHANI_SAHU took 1.9788734912872314s
Availability | SPARQL endpoint availability check for x took 4.458427429199219e-05s
Availability | VoID file availability check for x took 0.0005538463592529297s
Completeness | Calculation of interlinking completeness for x took 0.17710351943969727s
Reputation | Calculation of the PageRank for x took 0.020331382751464844s
Interlinking | Calculation of Degree of Connection for x took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for x took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for x took 2.7418136596679688e-05s
Believability | Calculation of trust value for x took 1.049041748046875e-05s
INFO | --- Analysis for Rozprawa,_artykuł took 1.9820153713226318s
Availability | SPARQL endpoint availability check for Rpm Find took 8.130073547363281e-05s
Availability | VoID file availability check for Rpm Find took 0.0002105236053466797s
Completeness | Calculation of interlinking completeness for Rpm Find took 0.18648362159729004s
Reputation | Calculation of the PageRank for Rpm Find took 0.020134925842285156s
Interlinking | Calculation of Degree of Connection for Rpm Find took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Rpm Find took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Rpm Find took 2.765655517578125e-05s
Believability | Calculation of trust value for Rpm Find took 1.1682510375976562e-05s
INFO | --- Analysis for rpm_find took 1.9676575660705566s
Availability | SPARQL endpoint availability check for RSS-500 NIF NER CORPUS took 4.0531158447265625e-05s
Availability | VoID file availability check for RSS-500 NIF NER CORPUS took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for RSS-500 NIF NER CORPUS took 0.17542457580566406s
Reputation | Calculation of the PageRank for RSS-500 NIF NER CORPUS took 0.02131962776184082s
Interlinking | Calculation of Degree of Connection for RSS-500 NIF NER CORPUS took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for RSS-500 NIF NER CORPUS took 0.0007271766662597656s
Interlinking | Calculation of Clustering coefficient for RSS-500 NIF NER CORPUS took 6.461143493652344e-05s
Believability | Calculation of trust value for RSS-500 NIF NER CORPUS took 1.1682510375976562e-05s
INFO | --- Analysis for rss-500-nif-ner-corpus took 1.9570231437683105s
Availability | SPARQL endpoint availability check for Ruben Taelman's Data took 8.344650268554688e-05s
Availability | VoID file availability check for Ruben Taelman's Data took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Ruben Taelman's Data took 0.17713046073913574s
Reputation | Calculation of the PageRank for Ruben Taelman's Data took 0.022687196731567383s
Interlinking | Calculation of Degree of Connection for Ruben Taelman's Data took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Ruben Taelman's Data took 0.0009205341339111328s
Interlinking | Calculation of Clustering coefficient for Ruben Taelman's Data took 8.606910705566406e-05s
Believability | Calculation of trust value for Ruben Taelman's Data took 1.1682510375976562e-05s
INFO | --- Analysis for rubentaelman took 2.027561902999878s
Availability | SPARQL endpoint availability check for Ruben Verborgh's data took 8.845329284667969e-05s
Availability | VoID file availability check for Ruben Verborgh's data took 0.0005233287811279297s
Completeness | Calculation of interlinking completeness for Ruben Verborgh's data took 0.17490220069885254s
Reputation | Calculation of the PageRank for Ruben Verborgh's data took 0.0222165584564209s
Interlinking | Calculation of Degree of Connection for Ruben Verborgh's data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Ruben Verborgh's data took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Ruben Verborgh's data took 8.678436279296875e-05s
Believability | Calculation of trust value for Ruben Verborgh's data took 7.62939453125e-06s
INFO | --- Analysis for rubenverborgh took 2.047837018966675s
Availability | SPARQL endpoint availability check for Russian Universities Specialities took 7.891654968261719e-05s
Availability | VoID file availability check for Russian Universities Specialities took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for Russian Universities Specialities took 0.17409968376159668s
Reputation | Calculation of the PageRank for Russian Universities Specialities took 0.02277231216430664s
Interlinking | Calculation of Degree of Connection for Russian Universities Specialities took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Russian Universities Specialities took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for Russian Universities Specialities took 3.218650817871094e-05s
Believability | Calculation of trust value for Russian Universities Specialities took 1.1205673217773438e-05s
INFO | --- Analysis for russian-universities-specialities took 2.0398199558258057s
Availability | SPARQL endpoint availability check for RuThes Cloud took 7.891654968261719e-05s
Availability | VoID file availability check for RuThes Cloud took 0.0004677772521972656s
Completeness | Calculation of interlinking completeness for RuThes Cloud took 0.1825711727142334s
Reputation | Calculation of the PageRank for RuThes Cloud took 0.02006363868713379s
Interlinking | Calculation of Degree of Connection for RuThes Cloud took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for RuThes Cloud took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for RuThes Cloud took 2.7894973754882812e-05s
Believability | Calculation of trust value for RuThes Cloud took 1.1444091796875e-05s
INFO | --- Analysis for ruthes took 2.00278639793396s
Availability | SPARQL endpoint availability check for RxNorm took 8.368492126464844e-05s
Availability | VoID file availability check for RxNorm took 0.00025725364685058594s
Completeness | Calculation of interlinking completeness for RxNorm took 0.17230463027954102s
Reputation | Calculation of the PageRank for RxNorm took 0.020125389099121094s
Interlinking | Calculation of Degree of Connection for RxNorm took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for RxNorm took 0.0007407665252685547s
Interlinking | Calculation of Clustering coefficient for RxNorm took 3.1948089599609375e-05s
Believability | Calculation of trust value for RxNorm took 1.3113021850585938e-05s
INFO | --- Analysis for rxnorm took 1.9972543716430664s
Availability | SPARQL endpoint availability check for SADI Semantic Web Services framework registry took 8.511543273925781e-05s
Availability | VoID file availability check for SADI Semantic Web Services framework registry took 0.0002455711364746094s
Completeness | Calculation of interlinking completeness for SADI Semantic Web Services framework registry took 0.18180012702941895s
Reputation | Calculation of the PageRank for SADI Semantic Web Services framework registry took 0.021457433700561523s
Interlinking | Calculation of Degree of Connection for SADI Semantic Web Services framework registry took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SADI Semantic Web Services framework registry took 0.0007266998291015625s
Interlinking | Calculation of Clustering coefficient for SADI Semantic Web Services framework registry took 2.7418136596679688e-05s
Believability | Calculation of trust value for SADI Semantic Web Services framework registry took 1.239776611328125e-05s
INFO | --- Analysis for sadi-semantic-web-services-framework-registry took 2.00260329246521s
Availability | SPARQL endpoint availability check for SALDO took 4.100799560546875e-05s
Availability | VoID file availability check for SALDO took 0.0005049705505371094s
Completeness | Calculation of interlinking completeness for SALDO took 0.20639443397521973s
Reputation | Calculation of the PageRank for SALDO took 0.020278215408325195s
Interlinking | Calculation of Degree of Connection for SALDO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SALDO took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for SALDO took 2.8133392333984375e-05s
Believability | Calculation of trust value for SALDO took 1.239776611328125e-05s
INFO | --- Analysis for saldo took 2.0054028034210205s
Availability | SPARQL endpoint availability check for SALDO-RDF took 8.344650268554688e-05s
Availability | VoID file availability check for SALDO-RDF took 0.0002415180206298828s
Completeness | Calculation of interlinking completeness for SALDO-RDF took 0.18732690811157227s
Reputation | Calculation of the PageRank for SALDO-RDF took 0.02247929573059082s
Interlinking | Calculation of Degree of Connection for SALDO-RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SALDO-RDF took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for SALDO-RDF took 3.7670135498046875e-05s
Believability | Calculation of trust value for SALDO-RDF took 1.2159347534179688e-05s
INFO | --- Analysis for saldo-rdf took 2.041510820388794s
Availability | SPARQL endpoint availability check for SALDOM-RDF took 8.249282836914062e-05s
Availability | VoID file availability check for SALDOM-RDF took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for SALDOM-RDF took 0.18520903587341309s
Reputation | Calculation of the PageRank for SALDOM-RDF took 0.021412134170532227s
Interlinking | Calculation of Degree of Connection for SALDOM-RDF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SALDOM-RDF took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for SALDOM-RDF took 3.2901763916015625e-05s
Believability | Calculation of trust value for SALDOM-RDF took 1.1205673217773438e-05s
INFO | --- Analysis for saldom-rdf took 2.049262762069702s
Availability | SPARQL endpoint availability check for Salzburgerland DE took 4.029273986816406e-05s
Availability | VoID file availability check for Salzburgerland DE took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Salzburgerland DE took 0.1867234706878662s
Reputation | Calculation of the PageRank for Salzburgerland DE took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for Salzburgerland DE took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Salzburgerland DE took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Salzburgerland DE took 0.00010156631469726562s
Believability | Calculation of trust value for Salzburgerland DE took 1.239776611328125e-05s
INFO | --- Analysis for salzburgerland-com-de took 2.0231544971466064s
Availability | SPARQL endpoint availability check for Salzburgerland EN took 8.034706115722656e-05s
Availability | VoID file availability check for Salzburgerland EN took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for Salzburgerland EN took 0.18479609489440918s
Reputation | Calculation of the PageRank for Salzburgerland EN took 0.020826101303100586s
Interlinking | Calculation of Degree of Connection for Salzburgerland EN took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Salzburgerland EN took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Salzburgerland EN took 0.00010371208190917969s
Believability | Calculation of trust value for Salzburgerland EN took 1.2159347534179688e-05s
INFO | --- Analysis for salzburgerland-com-en took 1.9672603607177734s
Availability | SPARQL endpoint availability check for Salzburgerland IT took 9.1552734375e-05s
Availability | VoID file availability check for Salzburgerland IT took 0.0002532005310058594s
Completeness | Calculation of interlinking completeness for Salzburgerland IT took 0.18313336372375488s
Reputation | Calculation of the PageRank for Salzburgerland IT took 0.020212650299072266s
Interlinking | Calculation of Degree of Connection for Salzburgerland IT took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Salzburgerland IT took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Salzburgerland IT took 0.00010752677917480469s
Believability | Calculation of trust value for Salzburgerland IT took 1.3828277587890625e-05s
INFO | --- Analysis for salzburgerland-com-it took 1.97330641746521s
Availability | SPARQL endpoint availability check for sameAs.org took 8.440017700195312e-05s
Availability | VoID file availability check for sameAs.org took 0.0011186599731445312s
Completeness | Calculation of interlinking completeness for sameAs.org took 0.18365764617919922s
Reputation | Calculation of the PageRank for sameAs.org took 0.02035045623779297s
Interlinking | Calculation of Degree of Connection for sameAs.org took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sameAs.org took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for sameAs.org took 2.8371810913085938e-05s
Believability | Calculation of trust value for sameAs.org took 1.239776611328125e-05s
INFO | --- Analysis for sameas-org took 2.025428056716919s
Availability | SPARQL endpoint availability check for sandrart.net took 8.440017700195312e-05s
Availability | VoID file availability check for sandrart.net took 0.00046944618225097656s
Completeness | Calculation of interlinking completeness for sandrart.net took 0.17423343658447266s
Reputation | Calculation of the PageRank for sandrart.net took 0.020346403121948242s
Interlinking | Calculation of Degree of Connection for sandrart.net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for sandrart.net took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for sandrart.net took 6.651878356933594e-05s
Believability | Calculation of trust value for sandrart.net took 1.3113021850585938e-05s
INFO | --- Analysis for sandrart-net took 1.978858470916748s
Availability | SPARQL endpoint availability check for Taxons  took 0.00012993812561035156s
Availability | VoID file availability check for Taxons  took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for Taxons  took 0.1805732250213623s
Reputation | Calculation of the PageRank for Taxons  took 0.021203279495239258s
Interlinking | Calculation of Degree of Connection for Taxons  took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Taxons  took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Taxons  took 8.869171142578125e-05s
Believability | Calculation of trust value for Taxons  took 1.2874603271484375e-05s
INFO | --- Analysis for sandre took 1.9628691673278809s
Availability | SPARQL endpoint availability check for Sanskrit English Lexicon took 8.630752563476562e-05s
Availability | VoID file availability check for Sanskrit English Lexicon took 0.00048160552978515625s
Completeness | Calculation of interlinking completeness for Sanskrit English Lexicon took 0.1794445514678955s
Reputation | Calculation of the PageRank for Sanskrit English Lexicon took 0.02075505256652832s
Interlinking | Calculation of Degree of Connection for Sanskrit English Lexicon took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Sanskrit English Lexicon took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Sanskrit English Lexicon took 2.9087066650390625e-05s
Believability | Calculation of trust value for Sanskrit English Lexicon took 1.3113021850585938e-05s
INFO | --- Analysis for sanskrit-english-lexicon took 2.021512746810913s
Availability | SPARQL endpoint availability check for Santillana Guide Dataset took 8.559226989746094e-05s
Availability | VoID file availability check for Santillana Guide Dataset took 0.0002567768096923828s
Completeness | Calculation of interlinking completeness for Santillana Guide Dataset took 0.17920947074890137s
Reputation | Calculation of the PageRank for Santillana Guide Dataset took 0.021680593490600586s
Interlinking | Calculation of Degree of Connection for Santillana Guide Dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Santillana Guide Dataset took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for Santillana Guide Dataset took 2.956390380859375e-05s
Believability | Calculation of trust value for Santillana Guide Dataset took 8.106231689453125e-06s
INFO | --- Analysis for santillana_guide_dataset took 1.9705240726470947s
Availability | SPARQL endpoint availability check for SATAR test  took 8.296966552734375e-05s
Availability | VoID file availability check for SATAR test  took 0.0007734298706054688s
Completeness | Calculation of interlinking completeness for SATAR test  took 0.17568731307983398s
Reputation | Calculation of the PageRank for SATAR test  took 0.022546052932739258s
Interlinking | Calculation of Degree of Connection for SATAR test  took 1.52587890625e-05s
Interlinking | Calculation of Centrality for SATAR test  took 0.0011975765228271484s
Interlinking | Calculation of Clustering coefficient for SATAR test  took 4.124641418457031e-05s
Believability | Calculation of trust value for SATAR test  took 1.2874603271484375e-05s
INFO | --- Analysis for SATAR_test took 2.052372455596924s
Availability | SPARQL endpoint availability check for SCBG Data took 8.273124694824219e-05s
Availability | VoID file availability check for SCBG Data took 0.0005004405975341797s
Completeness | Calculation of interlinking completeness for SCBG Data took 0.18853354454040527s
Reputation | Calculation of the PageRank for SCBG Data took 0.02079916000366211s
Interlinking | Calculation of Degree of Connection for SCBG Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SCBG Data took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for SCBG Data took 8.153915405273438e-05s
Believability | Calculation of trust value for SCBG Data took 1.239776611328125e-05s
INFO | --- Analysis for SCBG-Data took 1.9940197467803955s
Availability | SPARQL endpoint availability check for schema.org took 8.58306884765625e-05s
Availability | VoID file availability check for schema.org took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for schema.org took 0.17454051971435547s
Reputation | Calculation of the PageRank for schema.org took 0.020170211791992188s
Interlinking | Calculation of Degree of Connection for schema.org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for schema.org took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for schema.org took 3.123283386230469e-05s
Believability | Calculation of trust value for schema.org took 1.2636184692382812e-05s
INFO | --- Analysis for schema-org took 1.986856460571289s
Availability | SPARQL endpoint availability check for Schemantra took 8.606910705566406e-05s
Availability | VoID file availability check for Schemantra took 0.0004892349243164062s
Completeness | Calculation of interlinking completeness for Schemantra took 0.17032575607299805s
Reputation | Calculation of the PageRank for Schemantra took 0.02199840545654297s
Interlinking | Calculation of Degree of Connection for Schemantra took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Schemantra took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for Schemantra took 2.8371810913085938e-05s
Believability | Calculation of trust value for Schemantra took 1.3828277587890625e-05s
INFO | --- Analysis for Schemantra took 1.9827818870544434s
Availability | SPARQL endpoint availability check for Schemapedia: RDF schema compendium took 4.100799560546875e-05s
Availability | VoID file availability check for Schemapedia: RDF schema compendium took 0.0006754398345947266s
Completeness | Calculation of interlinking completeness for Schemapedia: RDF schema compendium took 0.17298340797424316s
Reputation | Calculation of the PageRank for Schemapedia: RDF schema compendium took 0.020479679107666016s
Interlinking | Calculation of Degree of Connection for Schemapedia: RDF schema compendium took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Schemapedia: RDF schema compendium took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for Schemapedia: RDF schema compendium took 3.314018249511719e-05s
Believability | Calculation of trust value for Schemapedia: RDF schema compendium took 1.33514404296875e-05s
INFO | --- Analysis for schemapedia took 1.941903829574585s
Availability | SPARQL endpoint availability check for scholarlydata took 8.440017700195312e-05s
Availability | VoID file availability check for scholarlydata took 0.0005490779876708984s
Completeness | Calculation of interlinking completeness for scholarlydata took 0.18163132667541504s
Reputation | Calculation of the PageRank for scholarlydata took 0.02242445945739746s
Interlinking | Calculation of Degree of Connection for scholarlydata took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for scholarlydata took 0.0007233619689941406s
Interlinking | Calculation of Clustering coefficient for scholarlydata took 3.0040740966796875e-05s
Believability | Calculation of trust value for scholarlydata took 1.3828277587890625e-05s
INFO | --- Analysis for scholarlydata took 1.993962287902832s
Availability | SPARQL endpoint availability check for Scholarometer took 4.076957702636719e-05s
Availability | VoID file availability check for Scholarometer took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Scholarometer took 0.17679667472839355s
Reputation | Calculation of the PageRank for Scholarometer took 0.020441293716430664s
Interlinking | Calculation of Degree of Connection for Scholarometer took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Scholarometer took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Scholarometer took 8.296966552734375e-05s
Believability | Calculation of trust value for Scholarometer took 1.2874603271484375e-05s
INFO | --- Analysis for scholarometer took 1.9620492458343506s
Availability | SPARQL endpoint availability check for Science Commons took 4.029273986816406e-05s
Availability | VoID file availability check for Science Commons took 0.00027298927307128906s
Completeness | Calculation of interlinking completeness for Science Commons took 0.1781754493713379s
Reputation | Calculation of the PageRank for Science Commons took 0.02041006088256836s
Interlinking | Calculation of Degree of Connection for Science Commons took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Science Commons took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Science Commons took 2.8133392333984375e-05s
Believability | Calculation of trust value for Science Commons took 1.2874603271484375e-05s
INFO | --- Analysis for science_commons took 1.9549567699432373s
Availability | SPARQL endpoint availability check for ScienceWise took 4.0531158447265625e-05s
Availability | VoID file availability check for ScienceWise took 0.00024890899658203125s
Completeness | Calculation of interlinking completeness for ScienceWise took 0.1761791706085205s
Reputation | Calculation of the PageRank for ScienceWise took 0.0219576358795166s
Interlinking | Calculation of Degree of Connection for ScienceWise took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ScienceWise took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for ScienceWise took 2.8848648071289062e-05s
Believability | Calculation of trust value for ScienceWise took 1.239776611328125e-05s
INFO | --- Analysis for sciencewise took 1.9747138023376465s
Availability | SPARQL endpoint availability check for The Digital Agenda Scoreboard of the European Commission took 3.933906555175781e-05s
Availability | VoID file availability check for The Digital Agenda Scoreboard of the European Commission took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for The Digital Agenda Scoreboard of the European Commission took 0.199293851852417s
Reputation | Calculation of the PageRank for The Digital Agenda Scoreboard of the European Commission took 0.02024555206298828s
Interlinking | Calculation of Degree of Connection for The Digital Agenda Scoreboard of the European Commission took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The Digital Agenda Scoreboard of the European Commission took 0.0007648468017578125s
Interlinking | Calculation of Clustering coefficient for The Digital Agenda Scoreboard of the European Commission took 2.7894973754882812e-05s
Believability | Calculation of trust value for The Digital Agenda Scoreboard of the European Commission took 1.2159347534179688e-05s
INFO | --- Analysis for scoreboard took 1.9856245517730713s
Availability | SPARQL endpoint availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.00010371208190917969s
Availability | VoID file availability check for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0004923343658447266s
Completeness | Calculation of interlinking completeness for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.18471455574035645s
Reputation | Calculation of the PageRank for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.02039337158203125s
Interlinking | Calculation of Degree of Connection for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 2.9802322387695312e-05s
Believability | Calculation of trust value for Simulation of desertification dynamics in Ordos City from 2000 to 2030 with coupled natural-human factors took 1.3113021850585938e-05s
INFO | --- Analysis for SDDEC took 1.9966802597045898s
Availability | SPARQL endpoint availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 4.00543212890625e-05s
Availability | VoID file availability check for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.17205595970153809s
Reputation | Calculation of the PageRank for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.020838260650634766s
Interlinking | Calculation of Degree of Connection for A Knowledge Organization System for the United Nations Sustainable Development Goals took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for A Knowledge Organization System for the United Nations Sustainable Development Goals took 0.0007243156433105469s
Interlinking | Calculation of Clustering coefficient for A Knowledge Organization System for the United Nations Sustainable Development Goals took 2.7418136596679688e-05s
Believability | Calculation of trust value for A Knowledge Organization System for the United Nations Sustainable Development Goals took 1.2874603271484375e-05s
INFO | --- Analysis for SDG took 1.981339693069458s
Availability | SPARQL endpoint availability check for sears.com took 8.845329284667969e-05s
Availability | VoID file availability check for sears.com took 0.0004956722259521484s
Completeness | Calculation of interlinking completeness for sears.com took 0.1777186393737793s
Reputation | Calculation of the PageRank for sears.com took 0.020172834396362305s
Interlinking | Calculation of Degree of Connection for sears.com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for sears.com took 0.00072479248046875s
Interlinking | Calculation of Clustering coefficient for sears.com took 6.365776062011719e-05s
Believability | Calculation of trust value for sears.com took 1.2874603271484375e-05s
INFO | --- Analysis for sears took 1.9867379665374756s
Availability | SPARQL endpoint availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.916854858398438e-05s
Availability | VoID file availability check for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0005118846893310547s
Completeness | Calculation of interlinking completeness for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.17516016960144043s
Reputation | Calculation of the PageRank for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.020657062530517578s
Interlinking | Calculation of Degree of Connection for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 8.106231689453125e-05s
Believability | Calculation of trust value for U.S. Securities and Exchange Commission Corporate Ownership RDF Data (rdfabout) took 1.3828277587890625e-05s
INFO | --- Analysis for sec-rdfabout took 1.9866352081298828s
Availability | SPARQL endpoint availability check for Source Code Ecosystem Linked Data took 8.20159912109375e-05s
Availability | VoID file availability check for Source Code Ecosystem Linked Data took 0.00044083595275878906s
Completeness | Calculation of interlinking completeness for Source Code Ecosystem Linked Data took 0.18100929260253906s
Reputation | Calculation of the PageRank for Source Code Ecosystem Linked Data took 0.021260976791381836s
Interlinking | Calculation of Degree of Connection for Source Code Ecosystem Linked Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Source Code Ecosystem Linked Data took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for Source Code Ecosystem Linked Data took 7.796287536621094e-05s
Believability | Calculation of trust value for Source Code Ecosystem Linked Data took 1.1205673217773438e-05s
INFO | --- Analysis for secold took 2.00000262260437s
Availability | SPARQL endpoint availability check for SEEK-AT-WD ICT tools for education - Web-Share took 3.910064697265625e-05s
Availability | VoID file availability check for SEEK-AT-WD ICT tools for education - Web-Share took 0.0004494190216064453s
Completeness | Calculation of interlinking completeness for SEEK-AT-WD ICT tools for education - Web-Share took 0.1780996322631836s
Reputation | Calculation of the PageRank for SEEK-AT-WD ICT tools for education - Web-Share took 0.021703004837036133s
Interlinking | Calculation of Degree of Connection for SEEK-AT-WD ICT tools for education - Web-Share took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SEEK-AT-WD ICT tools for education - Web-Share took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for SEEK-AT-WD ICT tools for education - Web-Share took 2.86102294921875e-05s
Believability | Calculation of trust value for SEEK-AT-WD ICT tools for education - Web-Share took 1.0967254638671875e-05s
INFO | --- Analysis for seek-at-wd-ict-tools-for-education-web-share took 1.9698872566223145s
Availability | SPARQL endpoint availability check for semanlink took 4.029273986816406e-05s
Availability | VoID file availability check for semanlink took 0.00020766258239746094s
Completeness | Calculation of interlinking completeness for semanlink took 0.17126059532165527s
Reputation | Calculation of the PageRank for semanlink took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for semanlink took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for semanlink took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for semanlink took 0.00013947486877441406s
Believability | Calculation of trust value for semanlink took 1.1682510375976562e-05s
INFO | --- Analysis for semanlink took 1.9611890316009521s
Availability | SPARQL endpoint availability check for Semantic Library took 4.0531158447265625e-05s
Availability | VoID file availability check for Semantic Library took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for Semantic Library took 0.17186403274536133s
Reputation | Calculation of the PageRank for Semantic Library took 0.020369291305541992s
Interlinking | Calculation of Degree of Connection for Semantic Library took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Semantic Library took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Semantic Library took 2.8371810913085938e-05s
Believability | Calculation of trust value for Semantic Library took 1.049041748046875e-05s
INFO | --- Analysis for semantic-library took 1.9696784019470215s
Availability | SPARQL endpoint availability check for Semantic Profiling Network took 8.344650268554688e-05s
Availability | VoID file availability check for Semantic Profiling Network took 0.0006237030029296875s
Completeness | Calculation of interlinking completeness for Semantic Profiling Network took 0.18002986907958984s
Reputation | Calculation of the PageRank for Semantic Profiling Network took 0.020438194274902344s
Interlinking | Calculation of Degree of Connection for Semantic Profiling Network took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Semantic Profiling Network took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Semantic Profiling Network took 3.0517578125e-05s
Believability | Calculation of trust value for Semantic Profiling Network took 1.3828277587890625e-05s
INFO | --- Analysis for semantic-profiling-network took 1.9683611392974854s
Availability | SPARQL endpoint availability check for Semantic Universe Data took 4.0531158447265625e-05s
Availability | VoID file availability check for Semantic Universe Data took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Semantic Universe Data took 0.19289636611938477s
Reputation | Calculation of the PageRank for Semantic Universe Data took 0.020290374755859375s
Interlinking | Calculation of Degree of Connection for Semantic Universe Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Semantic Universe Data took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Semantic Universe Data took 2.956390380859375e-05s
Believability | Calculation of trust value for Semantic Universe Data took 1.3113021850585938e-05s
INFO | --- Analysis for semantic-universe took 2.014094591140747s
Availability | SPARQL endpoint availability check for Semantic Web Dog Food Corpus took 8.535385131835938e-05s
Availability | VoID file availability check for Semantic Web Dog Food Corpus took 0.00113677978515625s
Completeness | Calculation of interlinking completeness for Semantic Web Dog Food Corpus took 0.17857027053833008s
Reputation | Calculation of the PageRank for Semantic Web Dog Food Corpus took 0.020734071731567383s
Interlinking | Calculation of Degree of Connection for Semantic Web Dog Food Corpus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic Web Dog Food Corpus took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Semantic Web Dog Food Corpus took 0.00011324882507324219s
Believability | Calculation of trust value for Semantic Web Dog Food Corpus took 1.3828277587890625e-05s
INFO | --- Analysis for semantic-web-dog-food took 2.00166916847229s
Availability | SPARQL endpoint availability check for semantic-web-grundlagen took 8.296966552734375e-05s
Availability | VoID file availability check for semantic-web-grundlagen took 0.00043582916259765625s
Completeness | Calculation of interlinking completeness for semantic-web-grundlagen took 0.1791553497314453s
Reputation | Calculation of the PageRank for semantic-web-grundlagen took 0.020167827606201172s
Interlinking | Calculation of Degree of Connection for semantic-web-grundlagen took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for semantic-web-grundlagen took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for semantic-web-grundlagen took 4.076957702636719e-05s
Believability | Calculation of trust value for semantic-web-grundlagen took 9.5367431640625e-06s
INFO | --- Analysis for semantic-web-grundlagen took 1.9414691925048828s
Availability | SPARQL endpoint availability check for semantic-web-journal took 4.363059997558594e-05s
Availability | VoID file availability check for semantic-web-journal took 0.00024509429931640625s
Completeness | Calculation of interlinking completeness for semantic-web-journal took 0.18034887313842773s
Reputation | Calculation of the PageRank for semantic-web-journal took 0.021135568618774414s
Interlinking | Calculation of Degree of Connection for semantic-web-journal took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for semantic-web-journal took 0.0007414817810058594s
Interlinking | Calculation of Clustering coefficient for semantic-web-journal took 3.170967102050781e-05s
Believability | Calculation of trust value for semantic-web-journal took 8.344650268554688e-06s
INFO | --- Analysis for semantic-web-journal took 1.9461030960083008s
Availability | SPARQL endpoint availability check for Semantic XBRL Financial Data took 4.00543212890625e-05s
Availability | VoID file availability check for Semantic XBRL Financial Data took 0.0004496574401855469s
Completeness | Calculation of interlinking completeness for Semantic XBRL Financial Data took 0.18139076232910156s
Reputation | Calculation of the PageRank for Semantic XBRL Financial Data took 0.020121335983276367s
Interlinking | Calculation of Degree of Connection for Semantic XBRL Financial Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Semantic XBRL Financial Data took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Semantic XBRL Financial Data took 7.987022399902344e-05s
Believability | Calculation of trust value for Semantic XBRL Financial Data took 1.1205673217773438e-05s
INFO | --- Analysis for semantic-xbrl took 2.011693239212036s
Availability | SPARQL endpoint availability check for Semantic Bible took 4.3392181396484375e-05s
Availability | VoID file availability check for Semantic Bible took 0.0005583763122558594s
Completeness | Calculation of interlinking completeness for Semantic Bible took 0.17383456230163574s
Reputation | Calculation of the PageRank for Semantic Bible took 0.02060413360595703s
Interlinking | Calculation of Degree of Connection for Semantic Bible took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Semantic Bible took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Semantic Bible took 2.8848648071289062e-05s
Believability | Calculation of trust value for Semantic Bible took 1.3828277587890625e-05s
INFO | --- Analysis for semantic_bible took 2.267652750015259s
Availability | SPARQL endpoint availability check for SemanticQuran took 8.273124694824219e-05s
Availability | VoID file availability check for SemanticQuran took 0.0004451274871826172s
Completeness | Calculation of interlinking completeness for SemanticQuran took 0.19836115837097168s
Reputation | Calculation of the PageRank for SemanticQuran took 0.020303964614868164s
Interlinking | Calculation of Degree of Connection for SemanticQuran took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SemanticQuran took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for SemanticQuran took 6.818771362304688e-05s
Believability | Calculation of trust value for SemanticQuran took 1.049041748046875e-05s
INFO | --- Analysis for semanticquran took 2.0494096279144287s
Availability | SPARQL endpoint availability check for SemanticTweet took 3.981590270996094e-05s
Availability | VoID file availability check for SemanticTweet took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for SemanticTweet took 0.1764976978302002s
Reputation | Calculation of the PageRank for SemanticTweet took 0.020152568817138672s
Interlinking | Calculation of Degree of Connection for SemanticTweet took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SemanticTweet took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SemanticTweet took 5.269050598144531e-05s
Believability | Calculation of trust value for SemanticTweet took 1.049041748046875e-05s
INFO | --- Analysis for semantictweet took 1.9573101997375488s
Availability | SPARQL endpoint availability check for semanticweb.org took 8.058547973632812e-05s
Availability | VoID file availability check for semanticweb.org took 0.0004527568817138672s
Completeness | Calculation of interlinking completeness for semanticweb.org took 0.18292021751403809s
Reputation | Calculation of the PageRank for semanticweb.org took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for semanticweb.org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for semanticweb.org took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for semanticweb.org took 7.557868957519531e-05s
Believability | Calculation of trust value for semanticweb.org took 1.1205673217773438e-05s
INFO | --- Analysis for semanticweb-org took 1.9670886993408203s
Availability | SPARQL endpoint availability check for Semantic CrunchBase took 0.00012159347534179688s
Availability | VoID file availability check for Semantic CrunchBase took 0.00048065185546875s
Completeness | Calculation of interlinking completeness for Semantic CrunchBase took 0.17309141159057617s
Reputation | Calculation of the PageRank for Semantic CrunchBase took 0.020965099334716797s
Interlinking | Calculation of Degree of Connection for Semantic CrunchBase took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Semantic CrunchBase took 0.0010008811950683594s
Interlinking | Calculation of Clustering coefficient for Semantic CrunchBase took 7.82012939453125e-05s
Believability | Calculation of trust value for Semantic CrunchBase took 1.430511474609375e-05s
INFO | --- Analysis for semsol-crunchbase took 1.9821076393127441s
Availability | SPARQL endpoint availability check for Sensores de IntelliDomo took 3.910064697265625e-05s
Availability | VoID file availability check for Sensores de IntelliDomo took 0.00044465065002441406s
Completeness | Calculation of interlinking completeness for Sensores de IntelliDomo took 0.17718935012817383s
Reputation | Calculation of the PageRank for Sensores de IntelliDomo took 0.020337343215942383s
Interlinking | Calculation of Degree of Connection for Sensores de IntelliDomo took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Sensores de IntelliDomo took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Sensores de IntelliDomo took 2.7179718017578125e-05s
Believability | Calculation of trust value for Sensores de IntelliDomo took 1.049041748046875e-05s
INFO | --- Analysis for sensores-de-intellidomo took 1.9692504405975342s
Availability | SPARQL endpoint availability check for SentimentWortschatz took 8.559226989746094e-05s
Availability | VoID file availability check for SentimentWortschatz took 0.0002713203430175781s
Completeness | Calculation of interlinking completeness for SentimentWortschatz took 0.17446565628051758s
Reputation | Calculation of the PageRank for SentimentWortschatz took 0.02107524871826172s
Interlinking | Calculation of Degree of Connection for SentimentWortschatz took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SentimentWortschatz took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for SentimentWortschatz took 4.00543212890625e-05s
Believability | Calculation of trust value for SentimentWortschatz took 1.3589859008789062e-05s
INFO | --- Analysis for sentiws took 1.9995231628417969s
Availability | SPARQL endpoint availability check for seoul-bike-data took 8.130073547363281e-05s
Availability | VoID file availability check for seoul-bike-data took 0.0002410411834716797s
Completeness | Calculation of interlinking completeness for seoul-bike-data took 0.1792912483215332s
Reputation | Calculation of the PageRank for seoul-bike-data took 0.022755146026611328s
Interlinking | Calculation of Degree of Connection for seoul-bike-data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for seoul-bike-data took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for seoul-bike-data took 2.8371810913085938e-05s
Believability | Calculation of trust value for seoul-bike-data took 1.2159347534179688e-05s
INFO | --- Analysis for seoul-bike-data took 1.9934260845184326s
Availability | SPARQL endpoint availability check for Serendipity took 4.0531158447265625e-05s
Availability | VoID file availability check for Serendipity took 0.00045561790466308594s
Completeness | Calculation of interlinking completeness for Serendipity took 0.17983269691467285s
Reputation | Calculation of the PageRank for Serendipity took 0.020107269287109375s
Interlinking | Calculation of Degree of Connection for Serendipity took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Serendipity took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for Serendipity took 6.771087646484375e-05s
Believability | Calculation of trust value for Serendipity took 1.1205673217773438e-05s
INFO | --- Analysis for serendipity took 1.975888729095459s
Availability | SPARQL endpoint availability check for Sherry Wine Vocabulary took 8.416175842285156e-05s
Availability | VoID file availability check for Sherry Wine Vocabulary took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Sherry Wine Vocabulary took 0.18159842491149902s
Reputation | Calculation of the PageRank for Sherry Wine Vocabulary took 0.020227670669555664s
Interlinking | Calculation of Degree of Connection for Sherry Wine Vocabulary took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine Vocabulary took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for Sherry Wine Vocabulary took 2.7418136596679688e-05s
Believability | Calculation of trust value for Sherry Wine Vocabulary took 1.0728836059570312e-05s
INFO | --- Analysis for Sherry_Wine took 2.037731647491455s
Availability | SPARQL endpoint availability check for Sherry Wine took 4.506111145019531e-05s
Availability | VoID file availability check for Sherry Wine took 0.00047206878662109375s
Completeness | Calculation of interlinking completeness for Sherry Wine took 0.17519760131835938s
Reputation | Calculation of the PageRank for Sherry Wine took 0.021655797958374023s
Interlinking | Calculation of Degree of Connection for Sherry Wine took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Sherry Wine took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Sherry Wine took 2.7418136596679688e-05s
Believability | Calculation of trust value for Sherry Wine took 1.1682510375976562e-05s
INFO | --- Analysis for Sherry_Wine_ took 1.9992597103118896s
Availability | SPARQL endpoint availability check for Shoah victims? names took 8.082389831542969e-05s
Availability | VoID file availability check for Shoah victims? names took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for Shoah victims? names took 0.17389202117919922s
Reputation | Calculation of the PageRank for Shoah victims? names took 0.020154953002929688s
Interlinking | Calculation of Degree of Connection for Shoah victims? names took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Shoah victims? names took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for Shoah victims? names took 3.528594970703125e-05s
Believability | Calculation of trust value for Shoah victims? names took 1.1920928955078125e-05s
INFO | --- Analysis for shoah-victims-names took 1.9915595054626465s
Availability | SPARQL endpoint availability check for Person took 4.172325134277344e-05s
Availability | VoID file availability check for Person took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Person took 0.17818021774291992s
Reputation | Calculation of the PageRank for Person took 0.0205838680267334s
Interlinking | Calculation of Degree of Connection for Person took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Person took 0.0007112026214599609s
Interlinking | Calculation of Clustering coefficient for Person took 2.7179718017578125e-05s
Believability | Calculation of trust value for Person took 1.2874603271484375e-05s
INFO | --- Analysis for Shripriya_Dubey took 2.004303455352783s
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.0002434253692626953s
Completeness | Calculation of interlinking completeness for Jishnu Raghavan (1976-2016) took 0.17700695991516113s
Reputation | Calculation of the PageRank for Jishnu Raghavan (1976-2016) took 0.020429611206054688s
Interlinking | Calculation of Degree of Connection for Jishnu Raghavan (1976-2016) took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Jishnu Raghavan (1976-2016) took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Jishnu Raghavan (1976-2016) took 2.9802322387695312e-05s
Believability | Calculation of trust value for Jishnu Raghavan (1976-2016) took 1.2159347534179688e-05s
INFO | --- Analysis for Shutterstock took 1.9568276405334473s
Availability | SPARQL endpoint availability check for SIMILE Data Collection took 4.00543212890625e-05s
Availability | VoID file availability check for SIMILE Data Collection took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for SIMILE Data Collection took 0.1774458885192871s
Reputation | Calculation of the PageRank for SIMILE Data Collection took 0.02031731605529785s
Interlinking | Calculation of Degree of Connection for SIMILE Data Collection took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for SIMILE Data Collection took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for SIMILE Data Collection took 2.6226043701171875e-05s
Believability | Calculation of trust value for SIMILE Data Collection took 1.1444091796875e-05s
INFO | --- Analysis for simile_data_collection took 1.993349552154541s
Availability | SPARQL endpoint availability check for SIMPLE took 8.225440979003906e-05s
Availability | VoID file availability check for SIMPLE took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for SIMPLE took 0.17409276962280273s
Reputation | Calculation of the PageRank for SIMPLE took 0.022051095962524414s
Interlinking | Calculation of Degree of Connection for SIMPLE took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for SIMPLE took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for SIMPLE took 3.647804260253906e-05s
Believability | Calculation of trust value for SIMPLE took 1.1444091796875e-05s
INFO | --- Analysis for simple took 1.962862491607666s
Availability | SPARQL endpoint availability check for SITC-V4 took 8.273124694824219e-05s
Availability | VoID file availability check for SITC-V4 took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for SITC-V4 took 0.1748213768005371s
Reputation | Calculation of the PageRank for SITC-V4 took 0.020214080810546875s
Interlinking | Calculation of Degree of Connection for SITC-V4 took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SITC-V4 took 0.0007443428039550781s
Interlinking | Calculation of Clustering coefficient for SITC-V4 took 3.3855438232421875e-05s
Believability | Calculation of trust value for SITC-V4 took 2.9087066650390625e-05s
INFO | --- Analysis for sitc-v4 took 1.9763765335083008s
Availability | SPARQL endpoint availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.0108642578125e-05s
Availability | VoID file availability check for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0004680156707763672s
Completeness | Calculation of interlinking completeness for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.18666839599609375s
Reputation | Calculation of the PageRank for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.020096778869628906s
Interlinking | Calculation of Degree of Connection for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 3.910064697265625e-05s
Believability | Calculation of trust value for SLI Galnet, the Galician wordnet, at version 3.0.26,  in RDF format took 1.2636184692382812e-05s
INFO | --- Analysis for sli_galnet_rdf took 2.0017378330230713s
Availability | SPARQL endpoint availability check for Slideshare2RDF Server took 7.867813110351562e-05s
Availability | VoID file availability check for Slideshare2RDF Server took 0.00044345855712890625s
Completeness | Calculation of interlinking completeness for Slideshare2RDF Server took 0.17347979545593262s
Reputation | Calculation of the PageRank for Slideshare2RDF Server took 0.020985841751098633s
Interlinking | Calculation of Degree of Connection for Slideshare2RDF Server took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Slideshare2RDF Server took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for Slideshare2RDF Server took 2.5987625122070312e-05s
Believability | Calculation of trust value for Slideshare2RDF Server took 9.775161743164062e-06s
INFO | --- Analysis for slideshare2rdf took 1.9463088512420654s
Availability | SPARQL endpoint availability check for Slidewiki (RDF/SPARQL) took 8.106231689453125e-05s
Availability | VoID file availability check for Slidewiki (RDF/SPARQL) took 0.00041556358337402344s
Completeness | Calculation of interlinking completeness for Slidewiki (RDF/SPARQL) took 0.17284893989562988s
Reputation | Calculation of the PageRank for Slidewiki (RDF/SPARQL) took 0.021445035934448242s
Interlinking | Calculation of Degree of Connection for Slidewiki (RDF/SPARQL) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Slidewiki (RDF/SPARQL) took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for Slidewiki (RDF/SPARQL) took 2.7179718017578125e-05s
Believability | Calculation of trust value for Slidewiki (RDF/SPARQL) took 1.1920928955078125e-05s
INFO | --- Analysis for slidewiki-rdf-sparql took 1.9897117614746094s
Availability | SPARQL endpoint availability check for Linked Stage Graph took 0.4531087875366211s
Availability | VoID file availability check for Linked Stage Graph took 0.0005066394805908203s
Extra | Recovery of all triples for Linked Stage Graph took 1.9560182094573975s
Performance | Total latancy measurement for Linked Stage Graph took 1.102189540863037s
Amount of data | Number of triples check for Linked Stage Graph took 0.24146437644958496s
Interoperability | New terms check for Linked Stage Graph took 1.6416077613830566s
Versatility | Languages check for Linked Stage Graph took 0.6713812351226807s
Interpretability | Number of blank nodes check for Linked Stage Graph took 0.2524070739746094s
Security | Check HTTPS for Linked Stage Graph took 0.14104866981506348s
Interpretability | RDF structures check for Linked Stage Graph took 0.28930115699768066s
Versatility | Serialization formats check for Linked Stage Graph took 0.29277515411376953s
Availability | RDF dump link check for Linked Stage Graph took 0.2214372158050537s
License | MR license check for Linked Stage Graph took 0.29616475105285645s
License | HR license check for Linked Stage Graph took 1.7660114765167236s
Amount of data | Number of property check for Linked Stage Graph took 0.22857356071472168s
Understandability | Number of label check for Linked Stage Graph took 0.415250301361084s
Understandability | URI regex check for Linked Stage Graph took 0.5028913021087646s
Understandability | Vocabs check for Linked Stage Graph took 0.22406625747680664s
Verifiability | Authors check for Linked Stage Graph took 0.23116350173950195s
Verifiability | Publishers check for Linked Stage Graph took 0.24979639053344727s
Performance | Throughput check for Linked Stage Graph took 11.111504793167114s
Amount of data | Check the number of entities for Linked Stage Graph took 7.557868957519531e-05s
Verifiability | Contribs. check for Linked Stage Graph took 0.2209153175354004s
Interlinking | sameAs chians check for Linked Stage Graph took 0.2846982479095459s
Interlinking | skos check for Linked Stage Graph took 0.25005102157592773s
Interlinking | skos check for Linked Stage Graph took 0.22016119956970215s
Timeliness | dataset update frequency check for Linked Stage Graph took 0.22420120239257812s
Currency | Creation date check for Linked Stage Graph took 0.4440138339996338s
Currency | Modification date check for Linked Stage Graph took 0.45014047622680664s
Rep.Conc. | URIs length for Linked Stage Graph took 1.6758027076721191s
Interoperability | New vocabularies check for Linked Stage Graph took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Linked Stage Graph took 0.22344970703125s
Accuracy | Check Functional Property for Linked Stage Graph took 0.22110462188720703s
Accuracy | Check Inverse Functional Property for Linked Stage Graph took 0.37560510635375977s
Accuracy | Check Empty annotation labels for Linked Stage Graph took 0.8277204036712646s
Accuracy | Check White space in annotation for Linked Stage Graph took 0.023593425750732422s
Accuracy | Check Datatype consistency for Linked Stage Graph took 0.02800440788269043s
Consistency | Disjoint class check for Linked Stage Graph took 0.22130441665649414s
Consistency | Check Misplaced properties for Linked Stage Graph took 0.989185094833374s
Consistency | Misplaced classes for Linked Stage Graph took 0.5859882831573486s
Consistency | Check Ontology hijacking for Linked Stage Graph took 2.1592652797698975s
Consistency | Check Invalid usage of undefined classes for Linked Stage Graph took 1.352712869644165s
Consistency | Check Invalid usage of undefined properties for Linked Stage Graph took 1.9190747737884521s
Conciseness | Check Extensional conciseness for Linked Stage Graph took 0.028697490692138672s
Conciseness | Check Intensional conciseness for Linked Stage Graph took 0.5767030715942383s
Security | Sign check for Linked Stage Graph took 0.3249475955963135s
Availability | Check URIs Dereferenciability for Linked Stage Graph took 1028.1131641864777s
Completeness | Calculation of interlinking completeness for Linked Stage Graph took 0.3071608543395996s
Reputation | Calculation of the PageRank for Linked Stage Graph took 0.02328777313232422s
Interlinking | Calculation of Degree of Connection for Linked Stage Graph took 1.7642974853515625e-05s
Interlinking | Calculation of Centrality for Linked Stage Graph took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Linked Stage Graph took 0.00014638900756835938s
Interoperability | Check the re-using of existing vocabs for Linked Stage Graph took 1.430511474609375e-06s
Believability | Calculation of trust value for Linked Stage Graph took 1.049041748046875e-05s
INFO | --- Analysis for slod took 1093.529613018036s
Availability | SPARQL endpoint availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 8.559226989746094e-05s
Availability | VoID file availability check for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.00023126602172851562s
Completeness | Calculation of interlinking completeness for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.2035520076751709s
Reputation | Calculation of the PageRank for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.020455598831176758s
Interlinking | Calculation of Degree of Connection for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 2.9087066650390625e-05s
Believability | Calculation of trust value for Slovník CPV 2008 - Common Procurement Vocabulary 2008 took 1.1444091796875e-05s
INFO | --- Analysis for slovn-k-cpv-2008---common-procurement-vocabulary-2008 took 2.0085694789886475s
Availability | SPARQL endpoint availability check for Smart Points Of Interest @PSNC took 8.034706115722656e-05s
Availability | VoID file availability check for Smart Points Of Interest @PSNC took 0.0005218982696533203s
Completeness | Calculation of interlinking completeness for Smart Points Of Interest @PSNC took 0.1802377700805664s
Reputation | Calculation of the PageRank for Smart Points Of Interest @PSNC took 0.022390127182006836s
Interlinking | Calculation of Degree of Connection for Smart Points Of Interest @PSNC took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Smart Points Of Interest @PSNC took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Smart Points Of Interest @PSNC took 9.34600830078125e-05s
Believability | Calculation of trust value for Smart Points Of Interest @PSNC took 1.2874603271484375e-05s
INFO | --- Analysis for Smart_POI_dataset took 1.9899847507476807s
Availability | SPARQL endpoint availability check for SmartLink: Linked Services Non-Functional Properties took 9.322166442871094e-05s
Availability | VoID file availability check for SmartLink: Linked Services Non-Functional Properties took 0.00043129920959472656s
Completeness | Calculation of interlinking completeness for SmartLink: Linked Services Non-Functional Properties took 0.20548009872436523s
Reputation | Calculation of the PageRank for SmartLink: Linked Services Non-Functional Properties took 0.0219266414642334s
Interlinking | Calculation of Degree of Connection for SmartLink: Linked Services Non-Functional Properties took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for SmartLink: Linked Services Non-Functional Properties took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for SmartLink: Linked Services Non-Functional Properties took 3.7670135498046875e-05s
Believability | Calculation of trust value for SmartLink: Linked Services Non-Functional Properties took 1.1205673217773438e-05s
INFO | --- Analysis for smartlink took 2.017514944076538s
Availability | SPARQL endpoint availability check for SNIK took 7.939338684082031e-05s
Availability | VoID file availability check for SNIK took 0.000316619873046875s
Completeness | Calculation of interlinking completeness for SNIK took 0.17993783950805664s
Reputation | Calculation of the PageRank for SNIK took 0.02045130729675293s
Interlinking | Calculation of Degree of Connection for SNIK took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for SNIK took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for SNIK took 7.390975952148438e-05s
Believability | Calculation of trust value for SNIK took 1.1205673217773438e-05s
INFO | --- Analysis for snik took 2.012157917022705s
Availability | SPARQL endpoint availability check for Social Networks and Archival Context Fall 2011 took 0.00011324882507324219s
Availability | VoID file availability check for Social Networks and Archival Context Fall 2011 took 0.00021457672119140625s
Completeness | Calculation of interlinking completeness for Social Networks and Archival Context Fall 2011 took 0.1808772087097168s
Reputation | Calculation of the PageRank for Social Networks and Archival Context Fall 2011 took 0.021613597869873047s
Interlinking | Calculation of Degree of Connection for Social Networks and Archival Context Fall 2011 took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Social Networks and Archival Context Fall 2011 took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for Social Networks and Archival Context Fall 2011 took 3.266334533691406e-05s
Believability | Calculation of trust value for Social Networks and Archival Context Fall 2011 took 1.0728836059570312e-05s
INFO | --- Analysis for social-networks-and-archival-context-fall-2011 took 2.024329423904419s
Availability | SPARQL endpoint availability check for SocialLink took 4.124641418457031e-05s
Availability | VoID file availability check for SocialLink took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for SocialLink took 0.18027639389038086s
Reputation | Calculation of the PageRank for SocialLink took 0.02016305923461914s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for SocialLink took 7.176399230957031e-05s
Believability | Calculation of trust value for SocialLink took 1.0967254638671875e-05s
INFO | --- Analysis for SocialLink took 1.9996592998504639s
Availability | SPARQL endpoint availability check for SocialLink took 8.058547973632812e-05s
Availability | VoID file availability check for SocialLink took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for SocialLink took 0.1791977882385254s
Reputation | Calculation of the PageRank for SocialLink took 0.021686792373657227s
Interlinking | Calculation of Degree of Connection for SocialLink took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for SocialLink took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for SocialLink took 3.0279159545898438e-05s
Believability | Calculation of trust value for SocialLink took 1.0728836059570312e-05s
INFO | --- Analysis for sociallink took 1.9941246509552002s
Availability | SPARQL endpoint availability check for FamilyRelations as SocialRole took 9.179115295410156e-05s
Availability | VoID file availability check for FamilyRelations as SocialRole took 0.0004303455352783203s
Completeness | Calculation of interlinking completeness for FamilyRelations as SocialRole took 0.17488741874694824s
Reputation | Calculation of the PageRank for FamilyRelations as SocialRole took 0.0229337215423584s
Interlinking | Calculation of Degree of Connection for FamilyRelations as SocialRole took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for FamilyRelations as SocialRole took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for FamilyRelations as SocialRole took 3.0517578125e-05s
Believability | Calculation of trust value for FamilyRelations as SocialRole took 1.0728836059570312e-05s
INFO | --- Analysis for SocialRoles took 1.974172592163086s
Availability | SPARQL endpoint availability check for Social Semantic Web Thesaurus took 4.0531158447265625e-05s
Availability | VoID file availability check for Social Semantic Web Thesaurus took 0.00044727325439453125s
Completeness | Calculation of interlinking completeness for Social Semantic Web Thesaurus took 0.18114638328552246s
Reputation | Calculation of the PageRank for Social Semantic Web Thesaurus took 0.020078420639038086s
Interlinking | Calculation of Degree of Connection for Social Semantic Web Thesaurus took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Social Semantic Web Thesaurus took 0.0007321834564208984s
Interlinking | Calculation of Clustering coefficient for Social Semantic Web Thesaurus took 8.96453857421875e-05s
Believability | Calculation of trust value for Social Semantic Web Thesaurus took 1.239776611328125e-05s
INFO | --- Analysis for socialsemweb-thesaurus took 1.9861094951629639s
Availability | SPARQL endpoint availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 4.00543212890625e-05s
Availability | VoID file availability check for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0004994869232177734s
Completeness | Calculation of interlinking completeness for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.18703508377075195s
Reputation | Calculation of the PageRank for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.02015542984008789s
Interlinking | Calculation of Degree of Connection for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 3.0994415283203125e-05s
Believability | Calculation of trust value for Erosion-endangered soil zones dataset from Czech Republic @PSNC took 1.1920928955078125e-05s
INFO | --- Analysis for Soil_maps took 2.0146749019622803s
Availability | SPARQL endpoint availability check for terrorrist ontology took 8.153915405273438e-05s
Availability | VoID file availability check for terrorrist ontology took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for terrorrist ontology took 0.17480969429016113s
Reputation | Calculation of the PageRank for terrorrist ontology took 0.02008962631225586s
Interlinking | Calculation of Degree of Connection for terrorrist ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for terrorrist ontology took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for terrorrist ontology took 2.9802322387695312e-05s
Believability | Calculation of trust value for terrorrist ontology took 1.1920928955078125e-05s
INFO | --- Analysis for somya_omer took 1.970625400543213s
Availability | SPARQL endpoint availability check for Sonclubcx took 9.942054748535156e-05s
Availability | VoID file availability check for Sonclubcx took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for Sonclubcx took 0.17858600616455078s
Reputation | Calculation of the PageRank for Sonclubcx took 0.020291566848754883s
Interlinking | Calculation of Degree of Connection for Sonclubcx took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Sonclubcx took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Sonclubcx took 1.1444091796875e-05s
Believability | Calculation of trust value for Sonclubcx took 1.0251998901367188e-05s
INFO | --- Analysis for sonclubcx took 1.9882864952087402s
Availability | SPARQL endpoint availability check for SORS took 0.00012159347534179688s
Availability | VoID file availability check for SORS took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for SORS took 0.18822169303894043s
Reputation | Calculation of the PageRank for SORS took 0.020147085189819336s
Interlinking | Calculation of Degree of Connection for SORS took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for SORS took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for SORS took 5.125999450683594e-05s
Believability | Calculation of trust value for SORS took 1.1205673217773438e-05s
INFO | --- Analysis for sors took 2.026803731918335s
Availability | SPARQL endpoint availability check for Soudy České republiky took 4.172325134277344e-05s
Availability | VoID file availability check for Soudy České republiky took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for Soudy České republiky took 0.17346429824829102s
Reputation | Calculation of the PageRank for Soudy České republiky took 0.02282857894897461s
Interlinking | Calculation of Degree of Connection for Soudy České republiky took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Soudy České republiky took 0.0007326602935791016s
Interlinking | Calculation of Clustering coefficient for Soudy České republiky took 2.8133392333984375e-05s
Believability | Calculation of trust value for Soudy České republiky took 1.1205673217773438e-05s
INFO | --- Analysis for soudy--esk--republiky took 1.9575273990631104s
Availability | SPARQL endpoint availability check for southampton-ac-uk took 8.034706115722656e-05s
Availability | VoID file availability check for southampton-ac-uk took 0.0004298686981201172s
Completeness | Calculation of interlinking completeness for southampton-ac-uk took 0.174757719039917s
Reputation | Calculation of the PageRank for southampton-ac-uk took 0.021299123764038086s
Interlinking | Calculation of Degree of Connection for southampton-ac-uk took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for southampton-ac-uk took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for southampton-ac-uk took 8.821487426757812e-05s
Believability | Calculation of trust value for southampton-ac-uk took 1.0728836059570312e-05s
INFO | --- Analysis for southampton-ac-uk took 1.9710443019866943s
Availability | SPARQL endpoint availability check for Apps using our data (University of Southampton) took 8.344650268554688e-05s
Availability | VoID file availability check for Apps using our data (University of Southampton) took 0.00043392181396484375s
Completeness | Calculation of interlinking completeness for Apps using our data (University of Southampton) took 0.18008160591125488s
Reputation | Calculation of the PageRank for Apps using our data (University of Southampton) took 0.020346879959106445s
Interlinking | Calculation of Degree of Connection for Apps using our data (University of Southampton) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Apps using our data (University of Southampton) took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Apps using our data (University of Southampton) took 2.9325485229492188e-05s
Believability | Calculation of trust value for Apps using our data (University of Southampton) took 1.049041748046875e-05s
INFO | --- Analysis for southampton-ac-uk-apps took 1.9844331741333008s
Availability | SPARQL endpoint availability check for ECS Southampton EPrints took 8.273124694824219e-05s
Availability | VoID file availability check for ECS Southampton EPrints took 0.0004372596740722656s
Completeness | Calculation of interlinking completeness for ECS Southampton EPrints took 0.17373967170715332s
Reputation | Calculation of the PageRank for ECS Southampton EPrints took 0.020375490188598633s
Interlinking | Calculation of Degree of Connection for ECS Southampton EPrints took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ECS Southampton EPrints took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for ECS Southampton EPrints took 9.369850158691406e-05s
Believability | Calculation of trust value for ECS Southampton EPrints took 1.1682510375976562e-05s
INFO | --- Analysis for southampton-ecs-eprints took 1.9767405986785889s
Availability | SPARQL endpoint availability check for Spanish Linguistic Datasets took 5.245208740234375e-05s
Availability | VoID file availability check for Spanish Linguistic Datasets took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Spanish Linguistic Datasets took 0.17946195602416992s
Reputation | Calculation of the PageRank for Spanish Linguistic Datasets took 0.02045583724975586s
Interlinking | Calculation of Degree of Connection for Spanish Linguistic Datasets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Spanish Linguistic Datasets took 0.0007345676422119141s
Interlinking | Calculation of Clustering coefficient for Spanish Linguistic Datasets took 3.1948089599609375e-05s
Believability | Calculation of trust value for Spanish Linguistic Datasets took 1.2636184692382812e-05s
INFO | --- Analysis for spanish-linguistic-datasets took 1.953012466430664s
Availability | SPARQL endpoint availability check for SPARQL Endpoint Status took 7.987022399902344e-05s
Availability | VoID file availability check for SPARQL Endpoint Status took 0.00044226646423339844s
Completeness | Calculation of interlinking completeness for SPARQL Endpoint Status took 0.19077181816101074s
Reputation | Calculation of the PageRank for SPARQL Endpoint Status took 0.021845340728759766s
Interlinking | Calculation of Degree of Connection for SPARQL Endpoint Status took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for SPARQL Endpoint Status took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for SPARQL Endpoint Status took 4.887580871582031e-05s
Believability | Calculation of trust value for SPARQL Endpoint Status took 5.245208740234375e-06s
INFO | --- Analysis for sparql-endpoint-status took 1.9933960437774658s
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.00047850608825683594s
Completeness | Calculation of interlinking completeness for SPC publikovaná SÚKL took 0.18335461616516113s
Reputation | Calculation of the PageRank for SPC publikovaná SÚKL took 0.02029109001159668s
Interlinking | Calculation of Degree of Connection for SPC publikovaná SÚKL took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for SPC publikovaná SÚKL took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for SPC publikovaná SÚKL took 3.0279159545898438e-05s
Believability | Calculation of trust value for SPC publikovaná SÚKL took 1.3589859008789062e-05s
INFO | --- Analysis for spc-publikovan--s-kl took 1.9562187194824219s
Availability | SPARQL endpoint availability check for SPQR took 8.153915405273438e-05s
Availability | VoID file availability check for SPQR took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for SPQR took 0.174055814743042s
Reputation | Calculation of the PageRank for SPQR took 0.021941661834716797s
Interlinking | Calculation of Degree of Connection for SPQR took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SPQR took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for SPQR took 3.1948089599609375e-05s
Believability | Calculation of trust value for SPQR took 1.0728836059570312e-05s
INFO | --- Analysis for spqr took 2.0454931259155273s
Availability | SPARQL endpoint availability check for Springer Nature SciGraph took 8.153915405273438e-05s
Availability | VoID file availability check for Springer Nature SciGraph took 0.0005385875701904297s
Completeness | Calculation of interlinking completeness for Springer Nature SciGraph took 0.17287659645080566s
Reputation | Calculation of the PageRank for Springer Nature SciGraph took 0.021458864212036133s
Interlinking | Calculation of Degree of Connection for Springer Nature SciGraph took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Springer Nature SciGraph took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for Springer Nature SciGraph took 8.416175842285156e-05s
Believability | Calculation of trust value for Springer Nature SciGraph took 1.0728836059570312e-05s
INFO | --- Analysis for springernaturescigraph took 1.9765207767486572s
Availability | SPARQL endpoint availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 6.842613220214844e-05s
Availability | VoID file availability check for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.0011019706726074219s
Completeness | Calculation of interlinking completeness for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.1884143352508545s
Reputation | Calculation of the PageRank for Syntactic Reference Corpus of Medieval French (SRCMF) took 0.020209312438964844s
Interlinking | Calculation of Degree of Connection for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.1205673217773438e-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 2.7418136596679688e-05s
Believability | Calculation of trust value for Syntactic Reference Corpus of Medieval French (SRCMF) took 1.2159347534179688e-05s
INFO | --- Analysis for srcmf took 2.0216715335845947s
Availability | SPARQL endpoint availability check for Lexicon of Syntactic and Semantic Framework took 4.100799560546875e-05s
Availability | VoID file availability check for Lexicon of Syntactic and Semantic Framework took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for Lexicon of Syntactic and Semantic Framework took 0.18137669563293457s
Reputation | Calculation of the PageRank for Lexicon of Syntactic and Semantic Framework took 0.020608901977539062s
Interlinking | Calculation of Degree of Connection for Lexicon of Syntactic and Semantic Framework took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Lexicon of Syntactic and Semantic Framework took 0.0007708072662353516s
Interlinking | Calculation of Clustering coefficient for Lexicon of Syntactic and Semantic Framework took 6.079673767089844e-05s
Believability | Calculation of trust value for Lexicon of Syntactic and Semantic Framework took 1.2636184692382812e-05s
INFO | --- Analysis for ssf took 2.0080127716064453s
Availability | SPARQL endpoint availability check for SSF took 4.267692565917969e-05s
Availability | VoID file availability check for SSF took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for SSF took 0.1766033172607422s
Reputation | Calculation of the PageRank for SSF took 0.020734310150146484s
Interlinking | Calculation of Degree of Connection for SSF took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for SSF took 0.0009419918060302734s
Interlinking | Calculation of Clustering coefficient for SSF took 3.5762786865234375e-05s
Believability | Calculation of trust value for SSF took 1.1205673217773438e-05s
INFO | --- Analysis for ssf-lexicon took 1.9830195903778076s
Availability | SPARQL endpoint availability check for St. Andrews University Resource Lists took 8.368492126464844e-05s
Availability | VoID file availability check for St. Andrews University Resource Lists took 0.0005099773406982422s
Completeness | Calculation of interlinking completeness for St. Andrews University Resource Lists took 0.17904353141784668s
Reputation | Calculation of the PageRank for St. Andrews University Resource Lists took 0.020439624786376953s
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.00070953369140625s
Interlinking | Calculation of Clustering coefficient for St. Andrews University Resource Lists took 3.743171691894531e-05s
Believability | Calculation of trust value for St. Andrews University Resource Lists took 1.2159347534179688e-05s
INFO | --- Analysis for st-andrews-resource-lists took 1.9761481285095215s
Availability | SPARQL endpoint availability check for STAC took 4.076957702636719e-05s
Availability | VoID file availability check for STAC took 0.0004711151123046875s
Completeness | Calculation of interlinking completeness for STAC took 0.1824033260345459s
Reputation | Calculation of the PageRank for STAC took 0.020111560821533203s
Interlinking | Calculation of Degree of Connection for STAC took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for STAC took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for STAC took 2.9802322387695312e-05s
Believability | Calculation of trust value for STAC took 1.1920928955078125e-05s
INFO | --- Analysis for stac took 2.051670551300049s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for The Scottish Government took 8.320808410644531e-05s
Availability | VoID file availability check for Organogram and staff pay data for The Scottish Government took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for The Scottish Government took 0.17866063117980957s
Reputation | Calculation of the PageRank for Organogram and staff pay data for The Scottish Government took 0.020415544509887695s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for The Scottish Government took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Organogram and staff pay data for The Scottish Government took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for The Scottish Government took 2.86102294921875e-05s
Believability | Calculation of trust value for Organogram and staff pay data for The Scottish Government took 1.2636184692382812e-05s
INFO | --- Analysis for staff-organograms-and-pay-scottish-government took 1.9899120330810547s
Availability | SPARQL endpoint availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 8.130073547363281e-05s
Availability | VoID file availability check for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0004918575286865234s
Completeness | Calculation of interlinking completeness for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.17413067817687988s
Reputation | Calculation of the PageRank for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.020738840103149414s
Interlinking | Calculation of Degree of Connection for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 3.528594970703125e-05s
Believability | Calculation of trust value for Organogram and staff pay data for Thurrock Thames Gateway Development Corporation took 1.1920928955078125e-05s
INFO | --- Analysis for staff-organograms-and-pay-thurrock-thames-gateway-development-corporation took 2.0062272548675537s
Availability | SPARQL endpoint availability check for Stammbuch took 4.172325134277344e-05s
Availability | VoID file availability check for Stammbuch took 0.0004725456237792969s
Completeness | Calculation of interlinking completeness for Stammbuch took 0.16947245597839355s
Reputation | Calculation of the PageRank for Stammbuch took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for Stammbuch took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Stammbuch took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Stammbuch took 2.765655517578125e-05s
Believability | Calculation of trust value for Stammbuch took 1.1920928955078125e-05s
INFO | --- Analysis for Stammbuch took 1.9623420238494873s
Availability | SPARQL endpoint availability check for statistics.data.gov.uk took 8.344650268554688e-05s
Availability | VoID file availability check for statistics.data.gov.uk took 0.0004754066467285156s
Completeness | Calculation of interlinking completeness for statistics.data.gov.uk took 0.1890125274658203s
Reputation | Calculation of the PageRank for statistics.data.gov.uk took 0.020183086395263672s
Interlinking | Calculation of Degree of Connection for statistics.data.gov.uk took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statistics.data.gov.uk took 0.0006887912750244141s
Interlinking | Calculation of Clustering coefficient for statistics.data.gov.uk took 0.00010251998901367188s
Believability | Calculation of trust value for statistics.data.gov.uk took 1.2636184692382812e-05s
INFO | --- Analysis for statistics-data-gov-uk took 1.96514892578125s
Availability | SPARQL endpoint availability check for Statistics on Fatal Traffic Accidents in greek roads took 8.034706115722656e-05s
Availability | VoID file availability check for Statistics on Fatal Traffic Accidents in greek roads took 0.00022268295288085938s
Completeness | Calculation of interlinking completeness for Statistics on Fatal Traffic Accidents in greek roads took 0.1736433506011963s
Reputation | Calculation of the PageRank for Statistics on Fatal Traffic Accidents in greek roads took 0.020683765411376953s
Interlinking | Calculation of Degree of Connection for Statistics on Fatal Traffic Accidents in greek roads took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Statistics on Fatal Traffic Accidents in greek roads took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for Statistics on Fatal Traffic Accidents in greek roads took 2.8848648071289062e-05s
Believability | Calculation of trust value for Statistics on Fatal Traffic Accidents in greek roads took 1.0013580322265625e-05s
INFO | --- Analysis for statistics-on-fatal-traffic-accidents-in-greek-roads took 1.960552453994751s
Availability | SPARQL endpoint availability check for statusnet-1w6-org took 9.441375732421875e-05s
Availability | VoID file availability check for statusnet-1w6-org took 0.0004210472106933594s
Completeness | Calculation of interlinking completeness for statusnet-1w6-org took 0.17230820655822754s
Reputation | Calculation of the PageRank for statusnet-1w6-org took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for statusnet-1w6-org took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-1w6-org took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for statusnet-1w6-org took 0.00010395050048828125s
Believability | Calculation of trust value for statusnet-1w6-org took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-1w6-org took 1.9725093841552734s
Availability | SPARQL endpoint availability check for statusnet-20100-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-20100-org took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for statusnet-20100-org took 0.18021726608276367s
Reputation | Calculation of the PageRank for statusnet-20100-org took 0.02056145668029785s
Interlinking | Calculation of Degree of Connection for statusnet-20100-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-20100-org took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for statusnet-20100-org took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-20100-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-20100-org took 1.9748525619506836s
Availability | SPARQL endpoint availability check for statusnet-alexandrefranke-com took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-alexandrefranke-com took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for statusnet-alexandrefranke-com took 0.17928647994995117s
Reputation | Calculation of the PageRank for statusnet-alexandrefranke-com took 0.020139217376708984s
Interlinking | Calculation of Degree of Connection for statusnet-alexandrefranke-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-alexandrefranke-com took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for statusnet-alexandrefranke-com took 6.604194641113281e-05s
Believability | Calculation of trust value for statusnet-alexandrefranke-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-alexandrefranke-com took 2.0084609985351562s
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.0004897117614746094s
Completeness | Calculation of interlinking completeness for statusnet-atari-frosch-de took 0.18584847450256348s
Reputation | Calculation of the PageRank for statusnet-atari-frosch-de took 0.020093679428100586s
Interlinking | Calculation of Degree of Connection for statusnet-atari-frosch-de took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-atari-frosch-de took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-atari-frosch-de took 7.772445678710938e-05s
Believability | Calculation of trust value for statusnet-atari-frosch-de took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-atari-frosch-de took 1.963273525238037s
Availability | SPARQL endpoint availability check for statusnet-belfalas-org took 8.153915405273438e-05s
Availability | VoID file availability check for statusnet-belfalas-org took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for statusnet-belfalas-org took 0.17180204391479492s
Reputation | Calculation of the PageRank for statusnet-belfalas-org took 0.020751237869262695s
Interlinking | Calculation of Degree of Connection for statusnet-belfalas-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-belfalas-org took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for statusnet-belfalas-org took 8.96453857421875e-05s
Believability | Calculation of trust value for statusnet-belfalas-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-belfalas-org took 2.2147057056427s
Availability | SPARQL endpoint availability check for statusnet-bka-li took 9.489059448242188e-05s
Availability | VoID file availability check for statusnet-bka-li took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for statusnet-bka-li took 0.17959165573120117s
Reputation | Calculation of the PageRank for statusnet-bka-li took 0.020150423049926758s
Interlinking | Calculation of Degree of Connection for statusnet-bka-li took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-bka-li took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for statusnet-bka-li took 0.00010371208190917969s
Believability | Calculation of trust value for statusnet-bka-li took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-bka-li took 1.9702799320220947s
Availability | SPARQL endpoint availability check for statusnet-bonifaz-ec took 8.082389831542969e-05s
Availability | VoID file availability check for statusnet-bonifaz-ec took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for statusnet-bonifaz-ec took 0.18175888061523438s
Reputation | Calculation of the PageRank for statusnet-bonifaz-ec took 0.02174830436706543s
Interlinking | Calculation of Degree of Connection for statusnet-bonifaz-ec took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-bonifaz-ec took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-bonifaz-ec took 3.719329833984375e-05s
Believability | Calculation of trust value for statusnet-bonifaz-ec took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-bonifaz-ec took 1.9839189052581787s
Availability | SPARQL endpoint availability check for statusnet-ced117-net took 5.245208740234375e-05s
Availability | VoID file availability check for statusnet-ced117-net took 0.0004401206970214844s
Completeness | Calculation of interlinking completeness for statusnet-ced117-net took 0.17404580116271973s
Reputation | Calculation of the PageRank for statusnet-ced117-net took 0.020159006118774414s
Interlinking | Calculation of Degree of Connection for statusnet-ced117-net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-ced117-net took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for statusnet-ced117-net took 4.649162292480469e-05s
Believability | Calculation of trust value for statusnet-ced117-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-ced117-net took 1.944823980331421s
Availability | SPARQL endpoint availability check for statusnet-chickenkiller-com took 3.9577484130859375e-05s
Availability | VoID file availability check for statusnet-chickenkiller-com took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for statusnet-chickenkiller-com took 0.17431068420410156s
Reputation | Calculation of the PageRank for statusnet-chickenkiller-com took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for statusnet-chickenkiller-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-chickenkiller-com took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-chickenkiller-com took 4.76837158203125e-05s
Believability | Calculation of trust value for statusnet-chickenkiller-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-chickenkiller-com took 1.988159418106079s
Availability | SPARQL endpoint availability check for statusnet-chromic-org took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-chromic-org took 0.00043964385986328125s
Completeness | Calculation of interlinking completeness for statusnet-chromic-org took 0.1673870086669922s
Reputation | Calculation of the PageRank for statusnet-chromic-org took 0.02023005485534668s
Interlinking | Calculation of Degree of Connection for statusnet-chromic-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-chromic-org took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-chromic-org took 0.00010824203491210938s
Believability | Calculation of trust value for statusnet-chromic-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-chromic-org took 1.9519939422607422s
Availability | SPARQL endpoint availability check for statusnet-cooleysekula-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-cooleysekula-net took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for statusnet-cooleysekula-net took 0.17552566528320312s
Reputation | Calculation of the PageRank for statusnet-cooleysekula-net took 0.020341873168945312s
Interlinking | Calculation of Degree of Connection for statusnet-cooleysekula-net took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-cooleysekula-net took 0.0007131099700927734s
Interlinking | Calculation of Clustering coefficient for statusnet-cooleysekula-net took 7.414817810058594e-05s
Believability | Calculation of trust value for statusnet-cooleysekula-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-cooleysekula-net took 1.9968621730804443s
Availability | SPARQL endpoint availability check for statusnet-coreyavis-com took 8.034706115722656e-05s
Availability | VoID file availability check for statusnet-coreyavis-com took 0.0004417896270751953s
Completeness | Calculation of interlinking completeness for statusnet-coreyavis-com took 0.18547773361206055s
Reputation | Calculation of the PageRank for statusnet-coreyavis-com took 0.02014303207397461s
Interlinking | Calculation of Degree of Connection for statusnet-coreyavis-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-coreyavis-com took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for statusnet-coreyavis-com took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-coreyavis-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-coreyavis-com took 1.976600170135498s
Availability | SPARQL endpoint availability check for statusnet-datenfahrt-org took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-datenfahrt-org took 0.0004456043243408203s
Completeness | Calculation of interlinking completeness for statusnet-datenfahrt-org took 0.18280315399169922s
Reputation | Calculation of the PageRank for statusnet-datenfahrt-org took 0.020409107208251953s
Interlinking | Calculation of Degree of Connection for statusnet-datenfahrt-org took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-datenfahrt-org took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for statusnet-datenfahrt-org took 6.29425048828125e-05s
Believability | Calculation of trust value for statusnet-datenfahrt-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-datenfahrt-org took 1.9986348152160645s
Availability | SPARQL endpoint availability check for statusnet-davidhaberthuer-ch took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-davidhaberthuer-ch took 0.0005068778991699219s
Completeness | Calculation of interlinking completeness for statusnet-davidhaberthuer-ch took 0.17438340187072754s
Reputation | Calculation of the PageRank for statusnet-davidhaberthuer-ch took 0.022763967514038086s
Interlinking | Calculation of Degree of Connection for statusnet-davidhaberthuer-ch took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-davidhaberthuer-ch took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for statusnet-davidhaberthuer-ch took 0.00010442733764648438s
Believability | Calculation of trust value for statusnet-davidhaberthuer-ch took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-davidhaberthuer-ch took 1.941180944442749s
Availability | SPARQL endpoint availability check for statusnet-deuxpi-ca took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-deuxpi-ca took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for statusnet-deuxpi-ca took 0.1758418083190918s
Reputation | Calculation of the PageRank for statusnet-deuxpi-ca took 0.022957324981689453s
Interlinking | Calculation of Degree of Connection for statusnet-deuxpi-ca took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-deuxpi-ca took 0.0006954669952392578s
Interlinking | Calculation of Clustering coefficient for statusnet-deuxpi-ca took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-deuxpi-ca took 9.775161743164062e-06s
INFO | --- Analysis for statusnet-deuxpi-ca took 2.0034291744232178s
Availability | SPARQL endpoint availability check for statusnet-doomicile-de took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-doomicile-de took 0.0004487037658691406s
Completeness | Calculation of interlinking completeness for statusnet-doomicile-de took 0.17981362342834473s
Reputation | Calculation of the PageRank for statusnet-doomicile-de took 0.022186279296875s
Interlinking | Calculation of Degree of Connection for statusnet-doomicile-de took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for statusnet-doomicile-de took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for statusnet-doomicile-de took 4.887580871582031e-05s
Believability | Calculation of trust value for statusnet-doomicile-de took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-doomicile-de took 1.9791004657745361s
Availability | SPARQL endpoint availability check for statusnet-dtdns-net took 8.654594421386719e-05s
Availability | VoID file availability check for statusnet-dtdns-net took 0.00023221969604492188s
Completeness | Calculation of interlinking completeness for statusnet-dtdns-net took 0.17769455909729004s
Reputation | Calculation of the PageRank for statusnet-dtdns-net took 0.020259618759155273s
Interlinking | Calculation of Degree of Connection for statusnet-dtdns-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-dtdns-net took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for statusnet-dtdns-net took 5.793571472167969e-05s
Believability | Calculation of trust value for statusnet-dtdns-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-dtdns-net took 2.004268169403076s
Availability | SPARQL endpoint availability check for statusnet-equestriarp-net took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-equestriarp-net took 0.0004432201385498047s
Completeness | Calculation of interlinking completeness for statusnet-equestriarp-net took 0.18796348571777344s
Reputation | Calculation of the PageRank for statusnet-equestriarp-net took 0.020132064819335938s
Interlinking | Calculation of Degree of Connection for statusnet-equestriarp-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-equestriarp-net took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for statusnet-equestriarp-net took 3.647804260253906e-05s
Believability | Calculation of trust value for statusnet-equestriarp-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-equestriarp-net took 1.9768872261047363s
Availability | SPARQL endpoint availability check for statusnet-exdc-net took 8.082389831542969e-05s
Availability | VoID file availability check for statusnet-exdc-net took 0.0004343986511230469s
Completeness | Calculation of interlinking completeness for statusnet-exdc-net took 0.17369794845581055s
Reputation | Calculation of the PageRank for statusnet-exdc-net took 0.021274805068969727s
Interlinking | Calculation of Degree of Connection for statusnet-exdc-net took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-exdc-net took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for statusnet-exdc-net took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-exdc-net took 1.5974044799804688e-05s
INFO | --- Analysis for statusnet-exdc-net took 2.0027310848236084s
Availability | SPARQL endpoint availability check for statusnet-fcac-com took 8.034706115722656e-05s
Availability | VoID file availability check for statusnet-fcac-com took 0.0004482269287109375s
Completeness | Calculation of interlinking completeness for statusnet-fcac-com took 0.17822957038879395s
Reputation | Calculation of the PageRank for statusnet-fcac-com took 0.022724390029907227s
Interlinking | Calculation of Degree of Connection for statusnet-fcac-com took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-fcac-com took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for statusnet-fcac-com took 9.107589721679688e-05s
Believability | Calculation of trust value for statusnet-fcac-com took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-fcac-com took 2.025782823562622s
Availability | SPARQL endpoint availability check for statusnet-fcestrada-com took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-fcestrada-com took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for statusnet-fcestrada-com took 0.1725928783416748s
Reputation | Calculation of the PageRank for statusnet-fcestrada-com took 0.020221948623657227s
Interlinking | Calculation of Degree of Connection for statusnet-fcestrada-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-fcestrada-com took 0.0007164478302001953s
Interlinking | Calculation of Clustering coefficient for statusnet-fcestrada-com took 5.054473876953125e-05s
Believability | Calculation of trust value for statusnet-fcestrada-com took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-fcestrada-com took 2.015904664993286s
Availability | SPARQL endpoint availability check for statusnet-fragdev-com took 8.535385131835938e-05s
Availability | VoID file availability check for statusnet-fragdev-com took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for statusnet-fragdev-com took 0.17961955070495605s
Reputation | Calculation of the PageRank for statusnet-fragdev-com took 0.022189617156982422s
Interlinking | Calculation of Degree of Connection for statusnet-fragdev-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-fragdev-com took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-fragdev-com took 0.000179290771484375s
Believability | Calculation of trust value for statusnet-fragdev-com took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-fragdev-com took 1.9896199703216553s
Availability | SPARQL endpoint availability check for statusnet-freelish-us took 8.416175842285156e-05s
Availability | VoID file availability check for statusnet-freelish-us took 0.0004913806915283203s
Completeness | Calculation of interlinking completeness for statusnet-freelish-us took 0.17552876472473145s
Reputation | Calculation of the PageRank for statusnet-freelish-us took 0.020200252532958984s
Interlinking | Calculation of Degree of Connection for statusnet-freelish-us took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-freelish-us took 0.0006940364837646484s
Interlinking | Calculation of Clustering coefficient for statusnet-freelish-us took 7.176399230957031e-05s
Believability | Calculation of trust value for statusnet-freelish-us took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-freelish-us took 1.9553282260894775s
Availability | SPARQL endpoint availability check for statusnet-gegeweb-org took 3.981590270996094e-05s
Availability | VoID file availability check for statusnet-gegeweb-org took 0.0004513263702392578s
Completeness | Calculation of interlinking completeness for statusnet-gegeweb-org took 0.1785433292388916s
Reputation | Calculation of the PageRank for statusnet-gegeweb-org took 0.023310422897338867s
Interlinking | Calculation of Degree of Connection for statusnet-gegeweb-org took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for statusnet-gegeweb-org took 0.0009107589721679688s
Interlinking | Calculation of Clustering coefficient for statusnet-gegeweb-org took 0.00011801719665527344s
Believability | Calculation of trust value for statusnet-gegeweb-org took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-gegeweb-org took 2.021522283554077s
Availability | SPARQL endpoint availability check for statusnet-glou-org took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-glou-org took 0.00043654441833496094s
Completeness | Calculation of interlinking completeness for statusnet-glou-org took 0.17505693435668945s
Reputation | Calculation of the PageRank for statusnet-glou-org took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for statusnet-glou-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-glou-org took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for statusnet-glou-org took 6.556510925292969e-05s
Believability | Calculation of trust value for statusnet-glou-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-glou-org took 1.968808650970459s
Availability | SPARQL endpoint availability check for statusnet-gomertronic-com took 4.029273986816406e-05s
Availability | VoID file availability check for statusnet-gomertronic-com took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for statusnet-gomertronic-com took 0.18619704246520996s
Reputation | Calculation of the PageRank for statusnet-gomertronic-com took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for statusnet-gomertronic-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-gomertronic-com took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for statusnet-gomertronic-com took 0.0001232624053955078s
Believability | Calculation of trust value for statusnet-gomertronic-com took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-gomertronic-com took 1.9775571823120117s
Availability | SPARQL endpoint availability check for statusnet-hackerposse-com took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-hackerposse-com took 0.0004391670227050781s
Completeness | Calculation of interlinking completeness for statusnet-hackerposse-com took 0.1810286045074463s
Reputation | Calculation of the PageRank for statusnet-hackerposse-com took 0.020433425903320312s
Interlinking | Calculation of Degree of Connection for statusnet-hackerposse-com took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-hackerposse-com took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for statusnet-hackerposse-com took 0.00010704994201660156s
Believability | Calculation of trust value for statusnet-hackerposse-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-hackerposse-com took 1.9547266960144043s
Availability | SPARQL endpoint availability check for statusnet-hii-co-il took 3.910064697265625e-05s
Availability | VoID file availability check for statusnet-hii-co-il took 0.0006268024444580078s
Completeness | Calculation of interlinking completeness for statusnet-hii-co-il took 0.20217037200927734s
Reputation | Calculation of the PageRank for statusnet-hii-co-il took 0.020737409591674805s
Interlinking | Calculation of Degree of Connection for statusnet-hii-co-il took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-hii-co-il took 0.0007472038269042969s
Interlinking | Calculation of Clustering coefficient for statusnet-hii-co-il took 4.6253204345703125e-05s
Believability | Calculation of trust value for statusnet-hii-co-il took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-hii-co-il took 1.998274564743042s
Availability | SPARQL endpoint availability check for statusnet-ilikefreedom-ro took 9.393692016601562e-05s
Availability | VoID file availability check for statusnet-ilikefreedom-ro took 0.00044536590576171875s
Completeness | Calculation of interlinking completeness for statusnet-ilikefreedom-ro took 0.17220592498779297s
Reputation | Calculation of the PageRank for statusnet-ilikefreedom-ro took 0.020325660705566406s
Interlinking | Calculation of Degree of Connection for statusnet-ilikefreedom-ro took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ilikefreedom-ro took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for statusnet-ilikefreedom-ro took 8.845329284667969e-05s
Believability | Calculation of trust value for statusnet-ilikefreedom-ro took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-ilikefreedom-ro took 1.9594852924346924s
Availability | SPARQL endpoint availability check for statusnet-imirhil-fr took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-imirhil-fr took 0.00044417381286621094s
Completeness | Calculation of interlinking completeness for statusnet-imirhil-fr took 0.17364859580993652s
Reputation | Calculation of the PageRank for statusnet-imirhil-fr took 0.02027726173400879s
Interlinking | Calculation of Degree of Connection for statusnet-imirhil-fr took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-imirhil-fr took 0.0007297992706298828s
Interlinking | Calculation of Clustering coefficient for statusnet-imirhil-fr took 5.817413330078125e-05s
Believability | Calculation of trust value for statusnet-imirhil-fr took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-imirhil-fr took 1.9648089408874512s
Availability | SPARQL endpoint availability check for statusnet-integralblue-com took 4.076957702636719e-05s
Availability | VoID file availability check for statusnet-integralblue-com took 0.0005083084106445312s
Completeness | Calculation of interlinking completeness for statusnet-integralblue-com took 0.17751455307006836s
Reputation | Calculation of the PageRank for statusnet-integralblue-com took 0.021792173385620117s
Interlinking | Calculation of Degree of Connection for statusnet-integralblue-com took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-integralblue-com took 0.0006937980651855469s
Interlinking | Calculation of Clustering coefficient for statusnet-integralblue-com took 3.790855407714844e-05s
Believability | Calculation of trust value for statusnet-integralblue-com took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-integralblue-com took 1.9868054389953613s
Availability | SPARQL endpoint availability check for statusnet-johndrinkwater-name took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-johndrinkwater-name took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for statusnet-johndrinkwater-name took 0.18323206901550293s
Reputation | Calculation of the PageRank for statusnet-johndrinkwater-name took 0.020276308059692383s
Interlinking | Calculation of Degree of Connection for statusnet-johndrinkwater-name took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-johndrinkwater-name took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for statusnet-johndrinkwater-name took 5.435943603515625e-05s
Believability | Calculation of trust value for statusnet-johndrinkwater-name took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-johndrinkwater-name took 1.982198715209961s
Availability | SPARQL endpoint availability check for statusnet-jonkman-ca took 4.267692565917969e-05s
Availability | VoID file availability check for statusnet-jonkman-ca took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for statusnet-jonkman-ca took 0.19384050369262695s
Reputation | Calculation of the PageRank for statusnet-jonkman-ca took 0.020132780075073242s
Interlinking | Calculation of Degree of Connection for statusnet-jonkman-ca took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-jonkman-ca took 0.0007188320159912109s
Interlinking | Calculation of Clustering coefficient for statusnet-jonkman-ca took 0.00012040138244628906s
Believability | Calculation of trust value for statusnet-jonkman-ca took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-jonkman-ca took 1.9817795753479004s
Availability | SPARQL endpoint availability check for statusnet-kaimi-cc took 8.893013000488281e-05s
Availability | VoID file availability check for statusnet-kaimi-cc took 0.0004551410675048828s
Completeness | Calculation of interlinking completeness for statusnet-kaimi-cc took 0.17784547805786133s
Reputation | Calculation of the PageRank for statusnet-kaimi-cc took 0.020104646682739258s
Interlinking | Calculation of Degree of Connection for statusnet-kaimi-cc took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-kaimi-cc took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for statusnet-kaimi-cc took 9.417533874511719e-05s
Believability | Calculation of trust value for statusnet-kaimi-cc took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-kaimi-cc took 1.9856321811676025s
Availability | SPARQL endpoint availability check for statusnet-kathryl-fr took 8.249282836914062e-05s
Availability | VoID file availability check for statusnet-kathryl-fr took 0.00051116943359375s
Completeness | Calculation of interlinking completeness for statusnet-kathryl-fr took 0.1728532314300537s
Reputation | Calculation of the PageRank for statusnet-kathryl-fr took 0.021095752716064453s
Interlinking | Calculation of Degree of Connection for statusnet-kathryl-fr took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-kathryl-fr took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for statusnet-kathryl-fr took 4.744529724121094e-05s
Believability | Calculation of trust value for statusnet-kathryl-fr took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-kathryl-fr took 1.9586293697357178s
Availability | SPARQL endpoint availability check for statusnet-kenzoid-com took 8.273124694824219e-05s
Availability | VoID file availability check for statusnet-kenzoid-com took 0.00022554397583007812s
Completeness | Calculation of interlinking completeness for statusnet-kenzoid-com took 0.18039703369140625s
Reputation | Calculation of the PageRank for statusnet-kenzoid-com took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for statusnet-kenzoid-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-kenzoid-com took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-kenzoid-com took 3.838539123535156e-05s
Believability | Calculation of trust value for statusnet-kenzoid-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-kenzoid-com took 1.963911533355713s
Availability | SPARQL endpoint availability check for statusnet-keuser-fr took 8.511543273925781e-05s
Availability | VoID file availability check for statusnet-keuser-fr took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for statusnet-keuser-fr took 0.18358397483825684s
Reputation | Calculation of the PageRank for statusnet-keuser-fr took 0.020171642303466797s
Interlinking | Calculation of Degree of Connection for statusnet-keuser-fr took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-keuser-fr took 0.0007724761962890625s
Interlinking | Calculation of Clustering coefficient for statusnet-keuser-fr took 8.630752563476562e-05s
Believability | Calculation of trust value for statusnet-keuser-fr took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-keuser-fr took 2.0349018573760986s
Availability | SPARQL endpoint availability check for statusnet-ldn-fai-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-ldn-fai-net took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for statusnet-ldn-fai-net took 0.1822357177734375s
Reputation | Calculation of the PageRank for statusnet-ldn-fai-net took 0.020823001861572266s
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.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for statusnet-ldn-fai-net took 5.5789947509765625e-05s
Believability | Calculation of trust value for statusnet-ldn-fai-net took 7.62939453125e-06s
INFO | --- Analysis for statusnet-ldn-fai-net took 1.9880447387695312s
Availability | SPARQL endpoint availability check for statusnet-lebsanft-org took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-lebsanft-org took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for statusnet-lebsanft-org took 0.1993873119354248s
Reputation | Calculation of the PageRank for statusnet-lebsanft-org took 0.0209195613861084s
Interlinking | Calculation of Degree of Connection for statusnet-lebsanft-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-lebsanft-org took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-lebsanft-org took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-lebsanft-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-lebsanft-org took 2.098814010620117s
Availability | SPARQL endpoint availability check for statusnet-legadolibre-com-ar took 5.316734313964844e-05s
Availability | VoID file availability check for statusnet-legadolibre-com-ar took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for statusnet-legadolibre-com-ar took 0.18740224838256836s
Reputation | Calculation of the PageRank for statusnet-legadolibre-com-ar took 0.020180225372314453s
Interlinking | Calculation of Degree of Connection for statusnet-legadolibre-com-ar took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-legadolibre-com-ar took 0.0007369518280029297s
Interlinking | Calculation of Clustering coefficient for statusnet-legadolibre-com-ar took 9.322166442871094e-05s
Believability | Calculation of trust value for statusnet-legadolibre-com-ar took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-legadolibre-com-ar took 2.0022664070129395s
Availability | SPARQL endpoint availability check for statusnet-linuxwrangling-com took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-linuxwrangling-com took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for statusnet-linuxwrangling-com took 0.17913317680358887s
Reputation | Calculation of the PageRank for statusnet-linuxwrangling-com took 0.020325899124145508s
Interlinking | Calculation of Degree of Connection for statusnet-linuxwrangling-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-linuxwrangling-com took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for statusnet-linuxwrangling-com took 0.00011420249938964844s
Believability | Calculation of trust value for statusnet-linuxwrangling-com took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-linuxwrangling-com took 2.078507423400879s
Availability | SPARQL endpoint availability check for statusnet-ludost-net took 3.933906555175781e-05s
Availability | VoID file availability check for statusnet-ludost-net took 0.00046539306640625s
Completeness | Calculation of interlinking completeness for statusnet-ludost-net took 0.17324328422546387s
Reputation | Calculation of the PageRank for statusnet-ludost-net took 0.020409345626831055s
Interlinking | Calculation of Degree of Connection for statusnet-ludost-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-ludost-net took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for statusnet-ludost-net took 5.269050598144531e-05s
Believability | Calculation of trust value for statusnet-ludost-net took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-ludost-net took 1.9574525356292725s
Availability | SPARQL endpoint availability check for statusnet-lydiastench-com took 4.00543212890625e-05s
Availability | VoID file availability check for statusnet-lydiastench-com took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for statusnet-lydiastench-com took 0.20482993125915527s
Reputation | Calculation of the PageRank for statusnet-lydiastench-com took 0.020180702209472656s
Interlinking | Calculation of Degree of Connection for statusnet-lydiastench-com took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-lydiastench-com took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for statusnet-lydiastench-com took 9.584426879882812e-05s
Believability | Calculation of trust value for statusnet-lydiastench-com took 1.3113021850585938e-05s
INFO | --- Analysis for statusnet-lydiastench-com took 2.029646396636963s
Availability | SPARQL endpoint availability check for statusnet-m-kuttner-com took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-m-kuttner-com took 0.000457763671875s
Completeness | Calculation of interlinking completeness for statusnet-m-kuttner-com took 0.1701054573059082s
Reputation | Calculation of the PageRank for statusnet-m-kuttner-com took 0.02027583122253418s
Interlinking | Calculation of Degree of Connection for statusnet-m-kuttner-com took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-m-kuttner-com took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for statusnet-m-kuttner-com took 5.125999450683594e-05s
Believability | Calculation of trust value for statusnet-m-kuttner-com took 1.2159347534179688e-05s
INFO | --- Analysis for statusnet-m-kuttner-com took 1.9885098934173584s
Availability | SPARQL endpoint availability check for statusnet-macno-org took 7.867813110351562e-05s
Availability | VoID file availability check for statusnet-macno-org took 0.00044798851013183594s
Completeness | Calculation of interlinking completeness for statusnet-macno-org took 0.17691731452941895s
Reputation | Calculation of the PageRank for statusnet-macno-org took 0.021258115768432617s
Interlinking | Calculation of Degree of Connection for statusnet-macno-org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for statusnet-macno-org took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for statusnet-macno-org took 0.00014519691467285156s
Believability | Calculation of trust value for statusnet-macno-org took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-macno-org took 1.9839446544647217s
Availability | SPARQL endpoint availability check for statusnet-mamalibre-com-ar took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-mamalibre-com-ar took 0.0002582073211669922s
Completeness | Calculation of interlinking completeness for statusnet-mamalibre-com-ar took 0.18196463584899902s
Reputation | Calculation of the PageRank for statusnet-mamalibre-com-ar took 0.021321535110473633s
Interlinking | Calculation of Degree of Connection for statusnet-mamalibre-com-ar took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for statusnet-mamalibre-com-ar took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-mamalibre-com-ar took 6.031990051269531e-05s
Believability | Calculation of trust value for statusnet-mamalibre-com-ar took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-mamalibre-com-ar took 1.9755001068115234s
Availability | SPARQL endpoint availability check for statusnet-maymay-net took 4.315376281738281e-05s
Availability | VoID file availability check for statusnet-maymay-net took 0.00043320655822753906s
Completeness | Calculation of interlinking completeness for statusnet-maymay-net took 0.18300867080688477s
Reputation | Calculation of the PageRank for statusnet-maymay-net took 0.02207469940185547s
Interlinking | Calculation of Degree of Connection for statusnet-maymay-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-maymay-net took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for statusnet-maymay-net took 7.510185241699219e-05s
Believability | Calculation of trust value for statusnet-maymay-net took 1.0013580322265625e-05s
INFO | --- Analysis for statusnet-maymay-net took 1.981588363647461s
Availability | SPARQL endpoint availability check for statusnet-morphtown-de took 8.463859558105469e-05s
Availability | VoID file availability check for statusnet-morphtown-de took 0.0004279613494873047s
Completeness | Calculation of interlinking completeness for statusnet-morphtown-de took 0.17165064811706543s
Reputation | Calculation of the PageRank for statusnet-morphtown-de took 0.022731542587280273s
Interlinking | Calculation of Degree of Connection for statusnet-morphtown-de took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-morphtown-de took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for statusnet-morphtown-de took 0.0001614093780517578s
Believability | Calculation of trust value for statusnet-morphtown-de took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-morphtown-de took 1.9777703285217285s
Availability | SPARQL endpoint availability check for statusnet-mrblog-nl took 8.177757263183594e-05s
Availability | VoID file availability check for statusnet-mrblog-nl took 0.0004448890686035156s
Completeness | Calculation of interlinking completeness for statusnet-mrblog-nl took 0.18498468399047852s
Reputation | Calculation of the PageRank for statusnet-mrblog-nl took 0.020159244537353516s
Interlinking | Calculation of Degree of Connection for statusnet-mrblog-nl took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-mrblog-nl took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for statusnet-mrblog-nl took 9.441375732421875e-05s
Believability | Calculation of trust value for statusnet-mrblog-nl took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-mrblog-nl took 1.9589858055114746s
Availability | SPARQL endpoint availability check for statusnet-mulestable-net took 8.082389831542969e-05s
Availability | VoID file availability check for statusnet-mulestable-net took 0.0005013942718505859s
Completeness | Calculation of interlinking completeness for statusnet-mulestable-net took 0.18239498138427734s
Reputation | Calculation of the PageRank for statusnet-mulestable-net took 0.02070164680480957s
Interlinking | Calculation of Degree of Connection for statusnet-mulestable-net took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for statusnet-mulestable-net took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for statusnet-mulestable-net took 5.650520324707031e-05s
Believability | Calculation of trust value for statusnet-mulestable-net took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-mulestable-net took 1.9832026958465576s
Availability | SPARQL endpoint availability check for statusnet-my-status-tk took 8.225440979003906e-05s
Availability | VoID file availability check for statusnet-my-status-tk took 0.000438690185546875s
Completeness | Calculation of interlinking completeness for statusnet-my-status-tk took 0.17399263381958008s
Reputation | Calculation of the PageRank for statusnet-my-status-tk took 0.02259540557861328s
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.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for statusnet-my-status-tk took 5.245208740234375e-05s
Believability | Calculation of trust value for statusnet-my-status-tk took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-my-status-tk took 1.9685449600219727s
Availability | SPARQL endpoint availability check for statusnet-opensim-chat-eu took 8.225440979003906e-05s
Availability | VoID file availability check for statusnet-opensim-chat-eu took 0.00023436546325683594s
Completeness | Calculation of interlinking completeness for statusnet-opensim-chat-eu took 0.17258310317993164s
Reputation | Calculation of the PageRank for statusnet-opensim-chat-eu took 0.021433115005493164s
Interlinking | Calculation of Degree of Connection for statusnet-opensim-chat-eu took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-opensim-chat-eu took 0.0007252693176269531s
Interlinking | Calculation of Clustering coefficient for statusnet-opensim-chat-eu took 0.00011515617370605469s
Believability | Calculation of trust value for statusnet-opensim-chat-eu took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-opensim-chat-eu took 1.9780666828155518s
Availability | SPARQL endpoint availability check for statusnet-orangeseeds-org took 8.058547973632812e-05s
Availability | VoID file availability check for statusnet-orangeseeds-org took 0.00049591064453125s
Completeness | Calculation of interlinking completeness for statusnet-orangeseeds-org took 0.18507742881774902s
Reputation | Calculation of the PageRank for statusnet-orangeseeds-org took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for statusnet-orangeseeds-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-orangeseeds-org took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-orangeseeds-org took 5.602836608886719e-05s
Believability | Calculation of trust value for statusnet-orangeseeds-org took 7.867813110351562e-06s
INFO | --- Analysis for statusnet-orangeseeds-org took 2.031074285507202s
Availability | SPARQL endpoint availability check for statusnet-otbm-fr took 8.296966552734375e-05s
Availability | VoID file availability check for statusnet-otbm-fr took 0.0005071163177490234s
Completeness | Calculation of interlinking completeness for statusnet-otbm-fr took 0.18686342239379883s
Reputation | Calculation of the PageRank for statusnet-otbm-fr took 0.020798683166503906s
Interlinking | Calculation of Degree of Connection for statusnet-otbm-fr took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-otbm-fr took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for statusnet-otbm-fr took 6.222724914550781e-05s
Believability | Calculation of trust value for statusnet-otbm-fr took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-otbm-fr took 2.0262551307678223s
Availability | SPARQL endpoint availability check for statusnet-ourcoffs-org-au took 0.00011587142944335938s
Availability | VoID file availability check for statusnet-ourcoffs-org-au took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for statusnet-ourcoffs-org-au took 0.2844271659851074s
Reputation | Calculation of the PageRank for statusnet-ourcoffs-org-au took 0.021759986877441406s
Interlinking | Calculation of Degree of Connection for statusnet-ourcoffs-org-au took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-ourcoffs-org-au took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for statusnet-ourcoffs-org-au took 0.00011086463928222656s
Believability | Calculation of trust value for statusnet-ourcoffs-org-au took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-ourcoffs-org-au took 2.0898988246917725s
Availability | SPARQL endpoint availability check for statusnet-panda-id-au took 8.487701416015625e-05s
Availability | VoID file availability check for statusnet-panda-id-au took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for statusnet-panda-id-au took 0.18175315856933594s
Reputation | Calculation of the PageRank for statusnet-panda-id-au took 0.02051544189453125s
Interlinking | Calculation of Degree of Connection for statusnet-panda-id-au took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-panda-id-au took 0.0007059574127197266s
Interlinking | Calculation of Clustering coefficient for statusnet-panda-id-au took 4.982948303222656e-05s
Believability | Calculation of trust value for statusnet-panda-id-au took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-panda-id-au took 2.036545753479004s
Availability | SPARQL endpoint availability check for statusnet-piana-eu took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-piana-eu took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for statusnet-piana-eu took 0.1834864616394043s
Reputation | Calculation of the PageRank for statusnet-piana-eu took 0.022131681442260742s
Interlinking | Calculation of Degree of Connection for statusnet-piana-eu took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-piana-eu took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for statusnet-piana-eu took 9.417533874511719e-05s
Believability | Calculation of trust value for statusnet-piana-eu took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-piana-eu took 1.9581973552703857s
Availability | SPARQL endpoint availability check for statusnet-planet-libre-org took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-planet-libre-org took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for statusnet-planet-libre-org took 0.18120861053466797s
Reputation | Calculation of the PageRank for statusnet-planet-libre-org took 0.02043294906616211s
Interlinking | Calculation of Degree of Connection for statusnet-planet-libre-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-planet-libre-org took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for statusnet-planet-libre-org took 7.581710815429688e-05s
Believability | Calculation of trust value for statusnet-planet-libre-org took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-planet-libre-org took 1.9818429946899414s
Availability | SPARQL endpoint availability check for statusnet-postblue-info took 4.4345855712890625e-05s
Availability | VoID file availability check for statusnet-postblue-info took 0.0005021095275878906s
Completeness | Calculation of interlinking completeness for statusnet-postblue-info took 0.18302655220031738s
Reputation | Calculation of the PageRank for statusnet-postblue-info took 0.02228999137878418s
Interlinking | Calculation of Degree of Connection for statusnet-postblue-info took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-postblue-info took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for statusnet-postblue-info took 0.0002307891845703125s
Believability | Calculation of trust value for statusnet-postblue-info took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-postblue-info took 1.9592392444610596s
Availability | SPARQL endpoint availability check for statusnet-progval-net took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-progval-net took 0.0006229877471923828s
Completeness | Calculation of interlinking completeness for statusnet-progval-net took 0.18530678749084473s
Reputation | Calculation of the PageRank for statusnet-progval-net took 0.02172565460205078s
Interlinking | Calculation of Degree of Connection for statusnet-progval-net took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-progval-net took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-progval-net took 6.866455078125e-05s
Believability | Calculation of trust value for statusnet-progval-net took 5.4836273193359375e-06s
INFO | --- Analysis for statusnet-progval-net took 1.9698030948638916s
Availability | SPARQL endpoint availability check for statusnet-qdnx-org took 4.1961669921875e-05s
Availability | VoID file availability check for statusnet-qdnx-org took 0.0004894733428955078s
Completeness | Calculation of interlinking completeness for statusnet-qdnx-org took 0.17522597312927246s
Reputation | Calculation of the PageRank for statusnet-qdnx-org took 0.020349979400634766s
Interlinking | Calculation of Degree of Connection for statusnet-qdnx-org took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for statusnet-qdnx-org took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for statusnet-qdnx-org took 0.00011134147644042969s
Believability | Calculation of trust value for statusnet-qdnx-org took 1.1444091796875e-05s
INFO | --- Analysis for statusnet-qdnx-org took 1.9662234783172607s
Availability | SPARQL endpoint availability check for statusnet-qth-fr took 9.012222290039062e-05s
Availability | VoID file availability check for statusnet-qth-fr took 0.0004379749298095703s
Completeness | Calculation of interlinking completeness for statusnet-qth-fr took 0.1788330078125s
Reputation | Calculation of the PageRank for statusnet-qth-fr took 0.020604610443115234s
Interlinking | Calculation of Degree of Connection for statusnet-qth-fr took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-qth-fr took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for statusnet-qth-fr took 6.270408630371094e-05s
Believability | Calculation of trust value for statusnet-qth-fr took 1.0967254638671875e-05s
INFO | --- Analysis for statusnet-qth-fr took 1.9842629432678223s
Availability | SPARQL endpoint availability check for statusnet-quitter-se took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-quitter-se took 0.0004429817199707031s
Completeness | Calculation of interlinking completeness for statusnet-quitter-se took 0.18360424041748047s
Reputation | Calculation of the PageRank for statusnet-quitter-se took 0.020264148712158203s
Interlinking | Calculation of Degree of Connection for statusnet-quitter-se took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for statusnet-quitter-se took 0.0007305145263671875s
Interlinking | Calculation of Clustering coefficient for statusnet-quitter-se took 0.000217437744140625s
Believability | Calculation of trust value for statusnet-quitter-se took 1.049041748046875e-05s
INFO | --- Analysis for statusnet-quitter-se took 1.9721477031707764s
Availability | SPARQL endpoint availability check for statusnet-rainbowdash-net took 8.177757263183594e-05s
Availability | VoID file availability check for statusnet-rainbowdash-net took 0.0005629062652587891s
Completeness | Calculation of interlinking completeness for statusnet-rainbowdash-net took 0.17554998397827148s
Reputation | Calculation of the PageRank for statusnet-rainbowdash-net took 0.020680665969848633s
Interlinking | Calculation of Degree of Connection for statusnet-rainbowdash-net took 5.054473876953125e-05s
Interlinking | Calculation of Centrality for statusnet-rainbowdash-net took 0.0007686614990234375s
Interlinking | Calculation of Clustering coefficient for statusnet-rainbowdash-net took 0.00011420249938964844s
Believability | Calculation of trust value for statusnet-rainbowdash-net took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-rainbowdash-net took 1.9739744663238525s
Availability | SPARQL endpoint availability check for statusnet-recit-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-recit-org took 0.0002238750457763672s
Completeness | Calculation of interlinking completeness for statusnet-recit-org took 0.18122172355651855s
Reputation | Calculation of the PageRank for statusnet-recit-org took 0.020235776901245117s
Interlinking | Calculation of Degree of Connection for statusnet-recit-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-recit-org took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for statusnet-recit-org took 5.745887756347656e-05s
Believability | Calculation of trust value for statusnet-recit-org took 1.239776611328125e-05s
INFO | --- Analysis for statusnet-recit-org took 1.9911141395568848s
Availability | SPARQL endpoint availability check for statusnet-russwurm-org took 8.153915405273438e-05s
Availability | VoID file availability check for statusnet-russwurm-org took 0.0005044937133789062s
Completeness | Calculation of interlinking completeness for statusnet-russwurm-org took 0.17806386947631836s
Reputation | Calculation of the PageRank for statusnet-russwurm-org took 0.02118849754333496s
Interlinking | Calculation of Degree of Connection for statusnet-russwurm-org took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for statusnet-russwurm-org took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for statusnet-russwurm-org took 0.00015044212341308594s
Believability | Calculation of trust value for statusnet-russwurm-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-russwurm-org took 1.968773603439331s
Availability | SPARQL endpoint availability check for statusnet-samnoble-org took 9.1552734375e-05s
Availability | VoID file availability check for statusnet-samnoble-org took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for statusnet-samnoble-org took 0.19014477729797363s
Reputation | Calculation of the PageRank for statusnet-samnoble-org took 0.020457983016967773s
Interlinking | Calculation of Degree of Connection for statusnet-samnoble-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-samnoble-org took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for statusnet-samnoble-org took 8.130073547363281e-05s
Believability | Calculation of trust value for statusnet-samnoble-org took 1.2874603271484375e-05s
INFO | --- Analysis for statusnet-samnoble-org took 1.9652550220489502s
Availability | SPARQL endpoint availability check for statusnet-schiessle-org took 4.100799560546875e-05s
Availability | VoID file availability check for statusnet-schiessle-org took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for statusnet-schiessle-org took 0.17558908462524414s
Reputation | Calculation of the PageRank for statusnet-schiessle-org took 0.020621299743652344s
Interlinking | Calculation of Degree of Connection for statusnet-schiessle-org took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for statusnet-schiessle-org took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-schiessle-org took 8.797645568847656e-05s
Believability | Calculation of trust value for statusnet-schiessle-org took 1.1682510375976562e-05s
INFO | --- Analysis for statusnet-schiessle-org took 2.0615527629852295s
Availability | SPARQL endpoint availability check for statusnet-scoffoni-net took 4.172325134277344e-05s
Availability | VoID file availability check for statusnet-scoffoni-net took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for statusnet-scoffoni-net took 0.18036746978759766s
Reputation | Calculation of the PageRank for statusnet-scoffoni-net took 0.02047252655029297s
Interlinking | Calculation of Degree of Connection for statusnet-scoffoni-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-scoffoni-net took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for statusnet-scoffoni-net took 9.703636169433594e-05s
Believability | Calculation of trust value for statusnet-scoffoni-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-scoffoni-net took 1.974064826965332s
Availability | SPARQL endpoint availability check for statusnet-sebseb01-net took 8.20159912109375e-05s
Availability | VoID file availability check for statusnet-sebseb01-net took 0.0004398822784423828s
Completeness | Calculation of interlinking completeness for statusnet-sebseb01-net took 0.1764390468597412s
Reputation | Calculation of the PageRank for statusnet-sebseb01-net took 0.020577192306518555s
Interlinking | Calculation of Degree of Connection for statusnet-sebseb01-net took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-sebseb01-net took 0.0007090568542480469s
Interlinking | Calculation of Clustering coefficient for statusnet-sebseb01-net took 6.413459777832031e-05s
Believability | Calculation of trust value for statusnet-sebseb01-net took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-sebseb01-net took 1.9685699939727783s
Availability | SPARQL endpoint availability check for statusnet-shnoulle-net took 8.153915405273438e-05s
Availability | VoID file availability check for statusnet-shnoulle-net took 0.0004801750183105469s
Completeness | Calculation of interlinking completeness for statusnet-shnoulle-net took 0.18025493621826172s
Reputation | Calculation of the PageRank for statusnet-shnoulle-net took 0.020498991012573242s
Interlinking | Calculation of Degree of Connection for statusnet-shnoulle-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-shnoulle-net took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for statusnet-shnoulle-net took 7.104873657226562e-05s
Believability | Calculation of trust value for statusnet-shnoulle-net took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-shnoulle-net took 1.9655821323394775s
Availability | SPARQL endpoint availability check for statusnet-skilledtests-com took 0.00019240379333496094s
Availability | VoID file availability check for statusnet-skilledtests-com took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for statusnet-skilledtests-com took 0.181565523147583s
Reputation | Calculation of the PageRank for statusnet-skilledtests-com took 0.02063274383544922s
Interlinking | Calculation of Degree of Connection for statusnet-skilledtests-com took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for statusnet-skilledtests-com took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for statusnet-skilledtests-com took 0.00021028518676757812s
Believability | Calculation of trust value for statusnet-skilledtests-com took 1.0251998901367188e-05s
INFO | --- Analysis for statusnet-skilledtests-com took 1.9940693378448486s
Availability | SPARQL endpoint availability check for statusnet-somsants-net took 3.9577484130859375e-05s
Availability | VoID file availability check for statusnet-somsants-net took 0.0004904270172119141s
Completeness | Calculation of interlinking completeness for statusnet-somsants-net took 0.18030047416687012s
Reputation | Calculation of the PageRank for statusnet-somsants-net took 0.020351171493530273s
Interlinking | Calculation of Degree of Connection for statusnet-somsants-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-somsants-net took 0.0007226467132568359s
Interlinking | Calculation of Clustering coefficient for statusnet-somsants-net took 0.00010609626770019531s
Believability | Calculation of trust value for statusnet-somsants-net took 1.0728836059570312e-05s
INFO | --- Analysis for statusnet-somsants-net took 2.019094944000244s
Availability | SPARQL endpoint availability check for statusnet-soucy-cc took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-soucy-cc took 0.0004706382751464844s
Completeness | Calculation of interlinking completeness for statusnet-soucy-cc took 0.19324088096618652s
Reputation | Calculation of the PageRank for statusnet-soucy-cc took 0.020423412322998047s
Interlinking | Calculation of Degree of Connection for statusnet-soucy-cc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-soucy-cc took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for statusnet-soucy-cc took 0.00013518333435058594s
Believability | Calculation of trust value for statusnet-soucy-cc took 7.152557373046875e-06s
INFO | --- Analysis for statusnet-soucy-cc took 1.9562160968780518s
Availability | SPARQL endpoint availability check for statusnet-spip-org took 4.124641418457031e-05s
Availability | VoID file availability check for statusnet-spip-org took 0.0002715587615966797s
Completeness | Calculation of interlinking completeness for statusnet-spip-org took 0.17420721054077148s
Reputation | Calculation of the PageRank for statusnet-spip-org took 0.02043938636779785s
Interlinking | Calculation of Degree of Connection for statusnet-spip-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-spip-org took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for statusnet-spip-org took 6.175041198730469e-05s
Believability | Calculation of trust value for statusnet-spip-org took 1.1205673217773438e-05s
INFO | --- Analysis for statusnet-spip-org took 2.0039095878601074s
Availability | SPARQL endpoint availability check for statusnet-spraci-org took 4.220008850097656e-05s
Availability | VoID file availability check for statusnet-spraci-org took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for statusnet-spraci-org took 0.17869925498962402s
Reputation | Calculation of the PageRank for statusnet-spraci-org took 0.020477294921875s
Interlinking | Calculation of Degree of Connection for statusnet-spraci-org took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-spraci-org took 0.0007255077362060547s
Interlinking | Calculation of Clustering coefficient for statusnet-spraci-org took 6.771087646484375e-05s
Believability | Calculation of trust value for statusnet-spraci-org took 1.2636184692382812e-05s
INFO | --- Analysis for statusnet-spraci-org took 1.9513342380523682s
Availability | SPARQL endpoint availability check for statusnet-ssweeny-net took 4.2438507080078125e-05s
Availability | VoID file availability check for statusnet-ssweeny-net took 0.0002143383026123047s
Completeness | Calculation of interlinking completeness for statusnet-ssweeny-net took 0.18410062789916992s
Reputation | Calculation of the PageRank for statusnet-ssweeny-net took 0.020564794540405273s
Interlinking | Calculation of Degree of Connection for statusnet-ssweeny-net took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for statusnet-ssweeny-net took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for statusnet-ssweeny-net took 0.00010991096496582031s
Believability | Calculation of trust value for statusnet-ssweeny-net took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-ssweeny-net took 1.9764535427093506s
Availability | SPARQL endpoint availability check for statusnet-status-net took 5.2928924560546875e-05s
Availability | VoID file availability check for statusnet-status-net took 0.00021219253540039062s
Completeness | Calculation of interlinking completeness for statusnet-status-net took 0.16947627067565918s
Reputation | Calculation of the PageRank for statusnet-status-net took 0.020412445068359375s
Interlinking | Calculation of Degree of Connection for statusnet-status-net took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-status-net took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for statusnet-status-net took 0.0002257823944091797s
Believability | Calculation of trust value for statusnet-status-net took 5.9604644775390625e-06s
INFO | --- Analysis for statusnet-status-net took 1.962010383605957s
Availability | SPARQL endpoint availability check for statusnet-sweetiebelle-net took 4.1484832763671875e-05s
Availability | VoID file availability check for statusnet-sweetiebelle-net took 0.0002315044403076172s
Completeness | Calculation of interlinking completeness for statusnet-sweetiebelle-net took 0.17557501792907715s
Reputation | Calculation of the PageRank for statusnet-sweetiebelle-net took 0.02044391632080078s
Interlinking | Calculation of Degree of Connection for statusnet-sweetiebelle-net took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-sweetiebelle-net took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for statusnet-sweetiebelle-net took 5.7697296142578125e-05s
Believability | Calculation of trust value for statusnet-sweetiebelle-net took 6.4373016357421875e-06s
INFO | --- Analysis for statusnet-sweetiebelle-net took 1.9464168548583984s
Availability | SPARQL endpoint availability check for statusnet-tekk-com-ar took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-tekk-com-ar took 0.0002484321594238281s
Completeness | Calculation of interlinking completeness for statusnet-tekk-com-ar took 0.17174577713012695s
Reputation | Calculation of the PageRank for statusnet-tekk-com-ar took 0.020466089248657227s
Interlinking | Calculation of Degree of Connection for statusnet-tekk-com-ar took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-tekk-com-ar took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for statusnet-tekk-com-ar took 9.250640869140625e-05s
Believability | Calculation of trust value for statusnet-tekk-com-ar took 8.106231689453125e-06s
INFO | --- Analysis for statusnet-tekk-com-ar took 1.9137108325958252s
Availability | SPARQL endpoint availability check for statusnet-thelovebug-org took 4.0531158447265625e-05s
Availability | VoID file availability check for statusnet-thelovebug-org took 0.00021195411682128906s
Completeness | Calculation of interlinking completeness for statusnet-thelovebug-org took 0.16879677772521973s
Reputation | Calculation of the PageRank for statusnet-thelovebug-org took 0.020343303680419922s
Interlinking | Calculation of Degree of Connection for statusnet-thelovebug-org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-thelovebug-org took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for statusnet-thelovebug-org took 0.0001270771026611328s
Believability | Calculation of trust value for statusnet-thelovebug-org took 7.62939453125e-06s
INFO | --- Analysis for statusnet-thelovebug-org took 1.9135773181915283s
Availability | SPARQL endpoint availability check for statusnet-thornton2-com took 4.9591064453125e-05s
Availability | VoID file availability check for statusnet-thornton2-com took 0.0004780292510986328s
Completeness | Calculation of interlinking completeness for statusnet-thornton2-com took 0.17611050605773926s
Reputation | Calculation of the PageRank for statusnet-thornton2-com took 0.021134376525878906s
Interlinking | Calculation of Degree of Connection for statusnet-thornton2-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-thornton2-com took 0.0007150173187255859s
Interlinking | Calculation of Clustering coefficient for statusnet-thornton2-com took 7.367134094238281e-05s
Believability | Calculation of trust value for statusnet-thornton2-com took 3.4809112548828125e-05s
INFO | --- Analysis for statusnet-thornton2-com took 2.0234429836273193s
Availability | SPARQL endpoint availability check for statusnet-timttmy-co-uk took 8.177757263183594e-05s
Availability | VoID file availability check for statusnet-timttmy-co-uk took 0.0004687309265136719s
Completeness | Calculation of interlinking completeness for statusnet-timttmy-co-uk took 0.1915140151977539s
Reputation | Calculation of the PageRank for statusnet-timttmy-co-uk took 0.020321130752563477s
Interlinking | Calculation of Degree of Connection for statusnet-timttmy-co-uk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for statusnet-timttmy-co-uk took 0.0007479190826416016s
Interlinking | Calculation of Clustering coefficient for statusnet-timttmy-co-uk took 0.00010776519775390625s
Believability | Calculation of trust value for statusnet-timttmy-co-uk took 1.3828277587890625e-05s
INFO | --- Analysis for statusnet-timttmy-co-uk took 1.9831407070159912s
Availability | SPARQL endpoint availability check for statusnet-tl1n-com took 8.320808410644531e-05s
Availability | VoID file availability check for statusnet-tl1n-com took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for statusnet-tl1n-com took 0.17773652076721191s
Reputation | Calculation of the PageRank for statusnet-tl1n-com took 0.0204470157623291s
Interlinking | Calculation of Degree of Connection for statusnet-tl1n-com took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-tl1n-com took 0.0007250308990478516s
Interlinking | Calculation of Clustering coefficient for statusnet-tl1n-com took 3.8623809814453125e-05s
Believability | Calculation of trust value for statusnet-tl1n-com took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-tl1n-com took 2.060375690460205s
Availability | SPARQL endpoint availability check for statusnet-tschlotfeldt-de took 8.368492126464844e-05s
Availability | VoID file availability check for statusnet-tschlotfeldt-de took 0.0004684925079345703s
Completeness | Calculation of interlinking completeness for statusnet-tschlotfeldt-de took 0.18123698234558105s
Reputation | Calculation of the PageRank for statusnet-tschlotfeldt-de took 0.020522356033325195s
Interlinking | Calculation of Degree of Connection for statusnet-tschlotfeldt-de took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for statusnet-tschlotfeldt-de took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for statusnet-tschlotfeldt-de took 6.651878356933594e-05s
Believability | Calculation of trust value for statusnet-tschlotfeldt-de took 1.33514404296875e-05s
INFO | --- Analysis for statusnet-tschlotfeldt-de took 1.9992542266845703s
Availability | SPARQL endpoint availability check for statusnet-uni-siegen-de took 8.606910705566406e-05s
Availability | VoID file availability check for statusnet-uni-siegen-de took 0.0004668235778808594s
Completeness | Calculation of interlinking completeness for statusnet-uni-siegen-de took 0.17748618125915527s
Reputation | Calculation of the PageRank for statusnet-uni-siegen-de took 0.020265579223632812s
Interlinking | Calculation of Degree of Connection for statusnet-uni-siegen-de took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for statusnet-uni-siegen-de took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for statusnet-uni-siegen-de took 3.743171691894531e-05s
Believability | Calculation of trust value for statusnet-uni-siegen-de took 1.1920928955078125e-05s
INFO | --- Analysis for statusnet-uni-siegen-de took 1.9848175048828125s
Availability | SPARQL endpoint availability check for Super Terminology System(STEAK) - Linked Open Data took 8.559226989746094e-05s
Availability | VoID file availability check for Super Terminology System(STEAK) - Linked Open Data took 0.0004718303680419922s
Completeness | Calculation of interlinking completeness for Super Terminology System(STEAK) - Linked Open Data took 0.18067264556884766s
Reputation | Calculation of the PageRank for Super Terminology System(STEAK) - Linked Open Data took 0.022165536880493164s
Interlinking | Calculation of Degree of Connection for Super Terminology System(STEAK) - Linked Open Data took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Super Terminology System(STEAK) - Linked Open Data took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Super Terminology System(STEAK) - Linked Open Data took 3.0279159545898438e-05s
Believability | Calculation of trust value for Super Terminology System(STEAK) - Linked Open Data took 1.5020370483398438e-05s
INFO | --- Analysis for steak took 2.0168910026550293s
Availability | SPARQL endpoint availability check for RAMEAU subject headings (STITCH) took 8.845329284667969e-05s
Availability | VoID file availability check for RAMEAU subject headings (STITCH) took 0.00020503997802734375s
Completeness | Calculation of interlinking completeness for RAMEAU subject headings (STITCH) took 0.18101811408996582s
Reputation | Calculation of the PageRank for RAMEAU subject headings (STITCH) took 0.02036261558532715s
Interlinking | Calculation of Degree of Connection for RAMEAU subject headings (STITCH) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for RAMEAU subject headings (STITCH) took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for RAMEAU subject headings (STITCH) took 5.2928924560546875e-05s
Believability | Calculation of trust value for RAMEAU subject headings (STITCH) took 1.2874603271484375e-05s
INFO | --- Analysis for stitch-rameau took 1.9843952655792236s
Availability | SPARQL endpoint availability check for Stone Tech Square took 4.172325134277344e-05s
Availability | VoID file availability check for Stone Tech Square took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Stone Tech Square took 0.18289875984191895s
Reputation | Calculation of the PageRank for Stone Tech Square took 0.02148890495300293s
Interlinking | Calculation of Degree of Connection for Stone Tech Square took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for Stone Tech Square took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Stone Tech Square took 1.3828277587890625e-05s
Believability | Calculation of trust value for Stone Tech Square took 5.7220458984375e-06s
INFO | --- Analysis for stone-tech-square-data took 1.9774458408355713s
Availability | SPARQL endpoint availability check for Strukturované popisy z FDA took 8.344650268554688e-05s
Availability | VoID file availability check for Strukturované popisy z FDA took 0.00044989585876464844s
Completeness | Calculation of interlinking completeness for Strukturované popisy z FDA took 0.17577266693115234s
Reputation | Calculation of the PageRank for Strukturované popisy z FDA took 0.023682355880737305s
Interlinking | Calculation of Degree of Connection for Strukturované popisy z FDA took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Strukturované popisy z FDA took 0.0013909339904785156s
Interlinking | Calculation of Clustering coefficient for Strukturované popisy z FDA took 4.2438507080078125e-05s
Believability | Calculation of trust value for Strukturované popisy z FDA took 8.58306884765625e-06s
INFO | --- Analysis for strukturovan--popisy-z-fda took 1.9762566089630127s
Availability | SPARQL endpoint availability check for STW Thesaurus for Economics took 8.440017700195312e-05s
Availability | VoID file availability check for STW Thesaurus for Economics took 0.00027179718017578125s
Completeness | Calculation of interlinking completeness for STW Thesaurus for Economics took 0.17426538467407227s
Reputation | Calculation of the PageRank for STW Thesaurus for Economics took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for STW Thesaurus for Economics took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for STW Thesaurus for Economics took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for STW Thesaurus for Economics took 0.0001087188720703125s
Believability | Calculation of trust value for STW Thesaurus for Economics took 1.2636184692382812e-05s
INFO | --- Analysis for stw-thesaurus-for-economics took 1.9669163227081299s
Availability | SPARQL endpoint availability check for SudershanTech took 4.38690185546875e-05s
Availability | VoID file availability check for SudershanTech took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for SudershanTech took 0.17992877960205078s
Reputation | Calculation of the PageRank for SudershanTech took 0.0206296443939209s
Interlinking | Calculation of Degree of Connection for SudershanTech took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for SudershanTech took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for SudershanTech took 3.0279159545898438e-05s
Believability | Calculation of trust value for SudershanTech took 5.7220458984375e-06s
INFO | --- Analysis for SudershanTech took 1.966768503189087s
Availability | SPARQL endpoint availability check for Sudoc bibliographic data took 4.57763671875e-05s
Availability | VoID file availability check for Sudoc bibliographic data took 0.00025534629821777344s
Completeness | Calculation of interlinking completeness for Sudoc bibliographic data took 0.2707102298736572s
Reputation | Calculation of the PageRank for Sudoc bibliographic data took 0.020274877548217773s
Interlinking | Calculation of Degree of Connection for Sudoc bibliographic data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sudoc bibliographic data took 0.0006918907165527344s
Interlinking | Calculation of Clustering coefficient for Sudoc bibliographic data took 4.5299530029296875e-05s
Believability | Calculation of trust value for Sudoc bibliographic data took 1.2874603271484375e-05s
INFO | --- Analysis for sudocfr took 2.088951587677002s
Availability | SPARQL endpoint availability check for Suface Forestière Mondiale 1990-2016 took 8.511543273925781e-05s
Availability | VoID file availability check for Suface Forestière Mondiale 1990-2016 took 0.00047087669372558594s
Completeness | Calculation of interlinking completeness for Suface Forestière Mondiale 1990-2016 took 0.17722177505493164s
Reputation | Calculation of the PageRank for Suface Forestière Mondiale 1990-2016 took 0.0205080509185791s
Interlinking | Calculation of Degree of Connection for Suface Forestière Mondiale 1990-2016 took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Suface Forestière Mondiale 1990-2016 took 0.0007162094116210938s
Interlinking | Calculation of Clustering coefficient for Suface Forestière Mondiale 1990-2016 took 7.510185241699219e-05s
Believability | Calculation of trust value for Suface Forestière Mondiale 1990-2016 took 8.58306884765625e-06s
INFO | --- Analysis for Suface_Forestière_Mondiale_1990-2016 took 2.007018804550171s
Availability | SPARQL endpoint availability check for Surge Radio took 8.440017700195312e-05s
Availability | VoID file availability check for Surge Radio took 0.0004630088806152344s
Completeness | Calculation of interlinking completeness for Surge Radio took 0.1759490966796875s
Reputation | Calculation of the PageRank for Surge Radio took 0.021202802658081055s
Interlinking | Calculation of Degree of Connection for Surge Radio took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Surge Radio took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for Surge Radio took 8.249282836914062e-05s
Believability | Calculation of trust value for Surge Radio took 1.239776611328125e-05s
INFO | --- Analysis for surge-radio took 1.9625818729400635s
Availability | SPARQL endpoint availability check for Soil & Water Assessment Tool took 8.082389831542969e-05s
Availability | VoID file availability check for Soil & Water Assessment Tool took 0.0004603862762451172s
Completeness | Calculation of interlinking completeness for Soil & Water Assessment Tool took 0.1725139617919922s
Reputation | Calculation of the PageRank for Soil & Water Assessment Tool took 0.02017045021057129s
Interlinking | Calculation of Degree of Connection for Soil & Water Assessment Tool took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Soil & Water Assessment Tool took 0.0006973743438720703s
Interlinking | Calculation of Clustering coefficient for Soil & Water Assessment Tool took 2.7418136596679688e-05s
Believability | Calculation of trust value for Soil & Water Assessment Tool took 1.4066696166992188e-05s
INFO | --- Analysis for SWAT took 1.9716572761535645s
Availability | SPARQL endpoint availability check for Swedish Open Cultural Heritage took 8.630752563476562e-05s
Availability | VoID file availability check for Swedish Open Cultural Heritage took 0.0004489421844482422s
Completeness | Calculation of interlinking completeness for Swedish Open Cultural Heritage took 0.17580199241638184s
Reputation | Calculation of the PageRank for Swedish Open Cultural Heritage took 0.021239519119262695s
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.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for Swedish Open Cultural Heritage took 7.081031799316406e-05s
Believability | Calculation of trust value for Swedish Open Cultural Heritage took 1.2159347534179688e-05s
INFO | --- Analysis for swedish-open-cultural-heritage took 2.001742362976074s
Availability | SPARQL endpoint availability check for SweFN-RDF took 8.034706115722656e-05s
Availability | VoID file availability check for SweFN-RDF took 0.0005011558532714844s
Completeness | Calculation of interlinking completeness for SweFN-RDF took 0.18704485893249512s
Reputation | Calculation of the PageRank for SweFN-RDF took 0.020466327667236328s
Interlinking | Calculation of Degree of Connection for SweFN-RDF took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for SweFN-RDF took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for SweFN-RDF took 3.8623809814453125e-05s
Believability | Calculation of trust value for SweFN-RDF took 1.1682510375976562e-05s
INFO | --- Analysis for swefn-rdf took 1.9814743995666504s
Availability | SPARQL endpoint availability check for SwetoDblp took 8.368492126464844e-05s
Availability | VoID file availability check for SwetoDblp took 0.00024366378784179688s
Completeness | Calculation of interlinking completeness for SwetoDblp took 0.40985608100891113s
Reputation | Calculation of the PageRank for SwetoDblp took 0.02246856689453125s
Interlinking | Calculation of Degree of Connection for SwetoDblp took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SwetoDblp took 0.00069427490234375s
Interlinking | Calculation of Clustering coefficient for SwetoDblp took 3.5762786865234375e-05s
Believability | Calculation of trust value for SwetoDblp took 1.2636184692382812e-05s
INFO | --- Analysis for sweto-dblp took 2.2732067108154297s
Availability | SPARQL endpoint availability check for Swift Vocabulary took 8.320808410644531e-05s
Availability | VoID file availability check for Swift Vocabulary took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for Swift Vocabulary took 0.18186736106872559s
Reputation | Calculation of the PageRank for Swift Vocabulary took 0.020555496215820312s
Interlinking | Calculation of Degree of Connection for Swift Vocabulary took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Swift Vocabulary took 0.0007176399230957031s
Interlinking | Calculation of Clustering coefficient for Swift Vocabulary took 6.699562072753906e-05s
Believability | Calculation of trust value for Swift Vocabulary took 1.33514404296875e-05s
INFO | --- Analysis for Swift took 2.0167806148529053s
Availability | SPARQL endpoint availability check for SymbolicData took 8.559226989746094e-05s
Availability | VoID file availability check for SymbolicData took 0.0004508495330810547s
Completeness | Calculation of interlinking completeness for SymbolicData took 0.18505144119262695s
Reputation | Calculation of the PageRank for SymbolicData took 0.021608352661132812s
Interlinking | Calculation of Degree of Connection for SymbolicData took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for SymbolicData took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for SymbolicData took 3.218650817871094e-05s
Believability | Calculation of trust value for SymbolicData took 1.2874603271484375e-05s
INFO | --- Analysis for symbolicdata took 1.998528003692627s
Availability | SPARQL endpoint availability check for Symptoms in Chinese took 8.249282836914062e-05s
Availability | VoID file availability check for Symptoms in Chinese took 0.0004558563232421875s
Completeness | Calculation of interlinking completeness for Symptoms in Chinese took 0.1764214038848877s
Reputation | Calculation of the PageRank for Symptoms in Chinese took 0.020438671112060547s
Interlinking | Calculation of Degree of Connection for Symptoms in Chinese took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Symptoms in Chinese took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Symptoms in Chinese took 3.0994415283203125e-05s
Believability | Calculation of trust value for Symptoms in Chinese took 1.1682510375976562e-05s
INFO | --- Analysis for symptoms-in-chinese took 1.990351915359497s
Availability | SPARQL endpoint availability check for National Digital Data Archive of Hungary (partial) took 0.46247172355651855s
Availability | VoID file availability check for National Digital Data Archive of Hungary (partial) took 0.00047898292541503906s
Extra | Recovery of all triples for National Digital Data Archive of Hungary (partial) took 0.5094423294067383s
Performance | Total latancy measurement for National Digital Data Archive of Hungary (partial) took 0.9367527961730957s
Amount of data | Number of triples check for National Digital Data Archive of Hungary (partial) took 11.751802921295166s
Interoperability | New terms check for National Digital Data Archive of Hungary (partial) took 18.780433416366577s
Versatility | Languages check for National Digital Data Archive of Hungary (partial) took 0.18346405029296875s
Interpretability | Number of blank nodes check for National Digital Data Archive of Hungary (partial) took 3.381510019302368s
Security | Check HTTPS for National Digital Data Archive of Hungary (partial) took 0.11511540412902832s
Interpretability | RDF structures check for National Digital Data Archive of Hungary (partial) took 0.37883877754211426s
Versatility | Serialization formats check for National Digital Data Archive of Hungary (partial) took 0.22971725463867188s
Availability | RDF dump link check for National Digital Data Archive of Hungary (partial) took 0.18600845336914062s
License | MR license check for National Digital Data Archive of Hungary (partial) took 0.36736106872558594s
License | HR license check for National Digital Data Archive of Hungary (partial) took 53.1194121837616s
Amount of data | Number of property check for National Digital Data Archive of Hungary (partial) took 0.5105071067810059s
Understandability | Number of label check for National Digital Data Archive of Hungary (partial) took 37.23187208175659s
Understandability | URI regex check for National Digital Data Archive of Hungary (partial) took 0.37253427505493164s
Understandability | Vocabs check for National Digital Data Archive of Hungary (partial) took 0.19081664085388184s
Verifiability | Authors check for National Digital Data Archive of Hungary (partial) took 0.18938899040222168s
Verifiability | Publishers check for National Digital Data Archive of Hungary (partial) took 0.18680930137634277s
Performance | Throughput check for National Digital Data Archive of Hungary (partial) took 13.629546880722046s
Amount of data | Check the number of entities for National Digital Data Archive of Hungary (partial) took 7.343292236328125e-05s
Verifiability | Contribs. check for National Digital Data Archive of Hungary (partial) took 1.8166594505310059s
Interlinking | sameAs chians check for National Digital Data Archive of Hungary (partial) took 1.8618311882019043s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.6402583122253418s
Interlinking | skos check for National Digital Data Archive of Hungary (partial) took 1.5873475074768066s
Timeliness | dataset update frequency check for National Digital Data Archive of Hungary (partial) took 1.563307762145996s
Currency | Creation date check for National Digital Data Archive of Hungary (partial) took 3.0316574573516846s
Currency | Modification date check for National Digital Data Archive of Hungary (partial) took 2.8766798973083496s
Rep.Conc. | URIs length for National Digital Data Archive of Hungary (partial) took 62.64484119415283s
Interoperability | New vocabularies check for National Digital Data Archive of Hungary (partial) took 1.1920928955078125e-06s
Consistency | Deprecated classes/propertiers check for National Digital Data Archive of Hungary (partial) took 0.18651819229125977s
Accuracy | Check Functional Property for National Digital Data Archive of Hungary (partial) took 0.21441435813903809s
Accuracy | Check Inverse Functional Property for National Digital Data Archive of Hungary (partial) took 0.18466782569885254s
Accuracy | Check Empty annotation labels for National Digital Data Archive of Hungary (partial) took 0.23696303367614746s
Accuracy | Check White space in annotation for National Digital Data Archive of Hungary (partial) took 0.002611875534057617s
Accuracy | Check Datatype consistency for National Digital Data Archive of Hungary (partial) took 0.002875804901123047s
Consistency | Disjoint class check for National Digital Data Archive of Hungary (partial) took 0.1856520175933838s
Consistency | Check Misplaced properties for National Digital Data Archive of Hungary (partial) took 45.102980613708496s
Consistency | Misplaced classes for National Digital Data Archive of Hungary (partial) took 0.2737159729003906s
Consistency | Check Ontology hijacking for National Digital Data Archive of Hungary (partial) took 1.6901934146881104s
Consistency | Check Invalid usage of undefined classes for National Digital Data Archive of Hungary (partial) took 1.394979476928711s
Consistency | Check Invalid usage of undefined properties for National Digital Data Archive of Hungary (partial) took 46.2333083152771s
Conciseness | Check Extensional conciseness for National Digital Data Archive of Hungary (partial) took 0.002111196517944336s
Conciseness | Check Intensional conciseness for National Digital Data Archive of Hungary (partial) took 0.3759186267852783s
Security | Sign check for National Digital Data Archive of Hungary (partial) took 0.18938541412353516s
Availability | Check URIs Dereferenciability for National Digital Data Archive of Hungary (partial) took 14.727230787277222s
Completeness | Calculation of interlinking completeness for National Digital Data Archive of Hungary (partial) took 0.25112152099609375s
Reputation | Calculation of the PageRank for National Digital Data Archive of Hungary (partial) took 0.02233290672302246s
Interlinking | Calculation of Degree of Connection for National Digital Data Archive of Hungary (partial) took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for National Digital Data Archive of Hungary (partial) took 0.0010230541229248047s
Interlinking | Calculation of Clustering coefficient for National Digital Data Archive of Hungary (partial) took 0.00010633468627929688s
Interoperability | Check the re-using of existing vocabs for National Digital Data Archive of Hungary (partial) took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Digital Data Archive of Hungary (partial) took 7.62939453125e-06s
INFO | --- Analysis for sztaki-lod took 482.9557845592499s
Availability | SPARQL endpoint availability check for Thesaurus for Graphic Materials (t4gm.info) took 4.315376281738281e-05s
Availability | VoID file availability check for Thesaurus for Graphic Materials (t4gm.info) took 0.00022220611572265625s
Completeness | Calculation of interlinking completeness for Thesaurus for Graphic Materials (t4gm.info) took 0.1742849349975586s
Reputation | Calculation of the PageRank for Thesaurus for Graphic Materials (t4gm.info) took 0.020630598068237305s
Interlinking | Calculation of Degree of Connection for Thesaurus for Graphic Materials (t4gm.info) took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Thesaurus for Graphic Materials (t4gm.info) took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Thesaurus for Graphic Materials (t4gm.info) took 5.078315734863281e-05s
Believability | Calculation of trust value for Thesaurus for Graphic Materials (t4gm.info) took 1.049041748046875e-05s
INFO | --- Analysis for t4gm-info took 1.973097562789917s
Availability | SPARQL endpoint availability check for tags2con delicious took 8.153915405273438e-05s
Availability | VoID file availability check for tags2con delicious took 0.0004189014434814453s
Completeness | Calculation of interlinking completeness for tags2con delicious took 0.17529773712158203s
Reputation | Calculation of the PageRank for tags2con delicious took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for tags2con delicious took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for tags2con delicious took 0.0007312297821044922s
Interlinking | Calculation of Clustering coefficient for tags2con delicious took 4.315376281738281e-05s
Believability | Calculation of trust value for tags2con delicious took 1.430511474609375e-05s
INFO | --- Analysis for tags2con-delicious took 1.9882609844207764s
Availability | SPARQL endpoint availability check for Taiwan geographic names took 4.482269287109375e-05s
Availability | VoID file availability check for Taiwan geographic names took 0.0005655288696289062s
Completeness | Calculation of interlinking completeness for Taiwan geographic names took 0.18438482284545898s
Reputation | Calculation of the PageRank for Taiwan geographic names took 0.020966768264770508s
Interlinking | Calculation of Degree of Connection for Taiwan geographic names took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for Taiwan geographic names took 0.0007338523864746094s
Interlinking | Calculation of Clustering coefficient for Taiwan geographic names took 6.103515625e-05s
Believability | Calculation of trust value for Taiwan geographic names took 1.2874603271484375e-05s
INFO | --- Analysis for taiwan-geographic-names took 1.996716022491455s
Availability | SPARQL endpoint availability check for Open Library data mirror in the Talis Platform took 4.57763671875e-05s
Availability | VoID file availability check for Open Library data mirror in the Talis Platform took 0.0008234977722167969s
Completeness | Calculation of interlinking completeness for Open Library data mirror in the Talis Platform took 0.1761183738708496s
Reputation | Calculation of the PageRank for Open Library data mirror in the Talis Platform took 0.02048325538635254s
Interlinking | Calculation of Degree of Connection for Open Library data mirror in the Talis Platform took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open Library data mirror in the Talis Platform took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Open Library data mirror in the Talis Platform took 8.845329284667969e-05s
Believability | Calculation of trust value for Open Library data mirror in the Talis Platform took 1.430511474609375e-05s
INFO | --- Analysis for talis-openlibrary took 3.1614632606506348s
Availability | SPARQL endpoint availability check for TalkBank took 4.458427429199219e-05s
Availability | VoID file availability check for TalkBank took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for TalkBank took 0.17608332633972168s
Reputation | Calculation of the PageRank for TalkBank took 0.020553112030029297s
Interlinking | Calculation of Degree of Connection for TalkBank took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TalkBank took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for TalkBank took 2.9325485229492188e-05s
Believability | Calculation of trust value for TalkBank took 1.1205673217773438e-05s
INFO | --- Analysis for talkbank took 1.9674360752105713s
Availability | SPARQL endpoint availability check for TaxonConcept Knowledge Base took 4.172325134277344e-05s
Availability | VoID file availability check for TaxonConcept Knowledge Base took 0.0004382133483886719s
Completeness | Calculation of interlinking completeness for TaxonConcept Knowledge Base took 0.17341995239257812s
Reputation | Calculation of the PageRank for TaxonConcept Knowledge Base took 0.020379304885864258s
Interlinking | Calculation of Degree of Connection for TaxonConcept Knowledge Base took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for TaxonConcept Knowledge Base took 0.0007753372192382812s
Interlinking | Calculation of Clustering coefficient for TaxonConcept Knowledge Base took 0.0001163482666015625s
Believability | Calculation of trust value for TaxonConcept Knowledge Base took 1.0728836059570312e-05s
INFO | --- Analysis for taxonconcept took 1.9417030811309814s
Availability | SPARQL endpoint availability check for taxonconcept-assets took 9.441375732421875e-05s
Availability | VoID file availability check for taxonconcept-assets took 0.0004265308380126953s
Completeness | Calculation of interlinking completeness for taxonconcept-assets took 0.18655061721801758s
Reputation | Calculation of the PageRank for taxonconcept-assets took 0.020345449447631836s
Interlinking | Calculation of Degree of Connection for taxonconcept-assets took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for taxonconcept-assets took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for taxonconcept-assets took 8.630752563476562e-05s
Believability | Calculation of trust value for taxonconcept-assets took 1.0251998901367188e-05s
INFO | --- Analysis for taxonconcept-assets took 2.0140702724456787s
Availability | SPARQL endpoint availability check for taxonconcept-occurences took 8.320808410644531e-05s
Availability | VoID file availability check for taxonconcept-occurences took 0.00041365623474121094s
Completeness | Calculation of interlinking completeness for taxonconcept-occurences took 0.18285608291625977s
Reputation | Calculation of the PageRank for taxonconcept-occurences took 0.020355224609375s
Interlinking | Calculation of Degree of Connection for taxonconcept-occurences took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for taxonconcept-occurences took 0.0007364749908447266s
Interlinking | Calculation of Clustering coefficient for taxonconcept-occurences took 5.030632019042969e-05s
Believability | Calculation of trust value for taxonconcept-occurences took 1.0251998901367188e-05s
INFO | --- Analysis for taxonconcept-occurences took 1.9794328212738037s
Availability | SPARQL endpoint availability check for TAXREF-LD: Linked Data French Taxonomic Register took 4.1961669921875e-05s
Availability | VoID file availability check for TAXREF-LD: Linked Data French Taxonomic Register took 0.00022864341735839844s
Completeness | Calculation of interlinking completeness for TAXREF-LD: Linked Data French Taxonomic Register took 0.17106127738952637s
Reputation | Calculation of the PageRank for TAXREF-LD: Linked Data French Taxonomic Register took 0.02025008201599121s
Interlinking | Calculation of Degree of Connection for TAXREF-LD: Linked Data French Taxonomic Register took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TAXREF-LD: Linked Data French Taxonomic Register took 0.0007181167602539062s
Interlinking | Calculation of Clustering coefficient for TAXREF-LD: Linked Data French Taxonomic Register took 4.935264587402344e-05s
Believability | Calculation of trust value for TAXREF-LD: Linked Data French Taxonomic Register took 1.049041748046875e-05s
INFO | --- Analysis for taxref-ld took 2.0414538383483887s
Availability | SPARQL endpoint availability check for The Cancer Genome Atlas took 4.0531158447265625e-05s
Availability | VoID file availability check for The Cancer Genome Atlas took 0.0002090930938720703s
Completeness | Calculation of interlinking completeness for The Cancer Genome Atlas took 0.18134593963623047s
Reputation | Calculation of the PageRank for The Cancer Genome Atlas took 0.020158767700195312s
Interlinking | Calculation of Degree of Connection for The Cancer Genome Atlas took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The Cancer Genome Atlas took 0.0007333755493164062s
Interlinking | Calculation of Clustering coefficient for The Cancer Genome Atlas took 2.9087066650390625e-05s
Believability | Calculation of trust value for The Cancer Genome Atlas took 5.9604644775390625e-06s
INFO | --- Analysis for tcga took 1.9122605323791504s
Availability | SPARQL endpoint availability check for TCGA Roadmap took 4.124641418457031e-05s
Availability | VoID file availability check for TCGA Roadmap took 0.0002124309539794922s
Completeness | Calculation of interlinking completeness for TCGA Roadmap took 0.1674816608428955s
Reputation | Calculation of the PageRank for TCGA Roadmap took 0.0203549861907959s
Interlinking | Calculation of Degree of Connection for TCGA Roadmap took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for TCGA Roadmap took 0.0007145404815673828s
Interlinking | Calculation of Clustering coefficient for TCGA Roadmap took 6.961822509765625e-05s
Believability | Calculation of trust value for TCGA Roadmap took 8.106231689453125e-06s
INFO | --- Analysis for tcga-roadmap took 1.936030626296997s
Availability | SPARQL endpoint availability check for TCMGeneDIT Dataset took 4.2438507080078125e-05s
Availability | VoID file availability check for TCMGeneDIT Dataset took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for TCMGeneDIT Dataset took 0.17425274848937988s
Reputation | Calculation of the PageRank for TCMGeneDIT Dataset took 0.022026538848876953s
Interlinking | Calculation of Degree of Connection for TCMGeneDIT Dataset took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TCMGeneDIT Dataset took 0.0007097721099853516s
Interlinking | Calculation of Clustering coefficient for TCMGeneDIT Dataset took 9.870529174804688e-05s
Believability | Calculation of trust value for TCMGeneDIT Dataset took 1.1920928955078125e-05s
INFO | --- Analysis for tcmgenedit_dataset took 2.0140604972839355s
Availability | SPARQL endpoint availability check for TDS took 8.106231689453125e-05s
Availability | VoID file availability check for TDS took 0.0004258155822753906s
Completeness | Calculation of interlinking completeness for TDS took 0.18314623832702637s
Reputation | Calculation of the PageRank for TDS took 0.020405292510986328s
Interlinking | Calculation of Degree of Connection for TDS took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TDS took 0.0007395744323730469s
Interlinking | Calculation of Clustering coefficient for TDS took 3.886222839355469e-05s
Believability | Calculation of trust value for TDS took 1.0728836059570312e-05s
INFO | --- Analysis for tds took 2.0146665573120117s
Availability | SPARQL endpoint availability check for TED Talks took 4.1484832763671875e-05s
Availability | VoID file availability check for TED Talks took 0.0004146099090576172s
Completeness | Calculation of interlinking completeness for TED Talks took 0.1842045783996582s
Reputation | Calculation of the PageRank for TED Talks took 0.020267486572265625s
Interlinking | Calculation of Degree of Connection for TED Talks took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TED Talks took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for TED Talks took 2.86102294921875e-05s
Believability | Calculation of trust value for TED Talks took 1.049041748046875e-05s
INFO | --- Analysis for ted-talks took 2.037578582763672s
Availability | SPARQL endpoint availability check for TEKORD took 4.363059997558594e-05s
Availability | VoID file availability check for TEKORD took 0.0005037784576416016s
Completeness | Calculation of interlinking completeness for TEKORD took 0.18175363540649414s
Reputation | Calculation of the PageRank for TEKORD took 0.021012306213378906s
Interlinking | Calculation of Degree of Connection for TEKORD took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TEKORD took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for TEKORD took 4.57763671875e-05s
Believability | Calculation of trust value for TEKORD took 1.33514404296875e-05s
INFO | --- Analysis for tekord took 2.074735403060913s
Availability | SPARQL endpoint availability check for Telegraphis Linked Data took 4.315376281738281e-05s
Availability | VoID file availability check for Telegraphis Linked Data took 0.0002624988555908203s
Completeness | Calculation of interlinking completeness for Telegraphis Linked Data took 0.18340015411376953s
Reputation | Calculation of the PageRank for Telegraphis Linked Data took 0.02010512351989746s
Interlinking | Calculation of Degree of Connection for Telegraphis Linked Data took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Telegraphis Linked Data took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Telegraphis Linked Data took 0.0001068115234375s
Believability | Calculation of trust value for Telegraphis Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for telegraphis took 1.9934227466583252s
Availability | SPARQL endpoint availability check for Temple ov thee Lemur took 8.940696716308594e-05s
Availability | VoID file availability check for Temple ov thee Lemur took 0.0004138946533203125s
Completeness | Calculation of interlinking completeness for Temple ov thee Lemur took 0.1806786060333252s
Reputation | Calculation of the PageRank for Temple ov thee Lemur took 0.020294189453125s
Interlinking | Calculation of Degree of Connection for Temple ov thee Lemur took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Temple ov thee Lemur took 0.0006935596466064453s
Interlinking | Calculation of Clustering coefficient for Temple ov thee Lemur took 6.604194641113281e-05s
Believability | Calculation of trust value for Temple ov thee Lemur took 1.0251998901367188e-05s
INFO | --- Analysis for temple-ov-thee-lemur-datasets took 1.9925692081451416s
Availability | SPARQL endpoint availability check for TERENCE Reading Comprehension Dataset took 8.225440979003906e-05s
Availability | VoID file availability check for TERENCE Reading Comprehension Dataset took 0.00042700767517089844s
Completeness | Calculation of interlinking completeness for TERENCE Reading Comprehension Dataset took 0.1751551628112793s
Reputation | Calculation of the PageRank for TERENCE Reading Comprehension Dataset took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for TERENCE Reading Comprehension Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TERENCE Reading Comprehension Dataset took 0.0007259845733642578s
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.0251998901367188e-05s
INFO | --- Analysis for terence-reading-comprehension-dataset took 1.9672019481658936s
Availability | SPARQL endpoint availability check for Terminesp Linked Data took 8.797645568847656e-05s
Availability | VoID file availability check for Terminesp Linked Data took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Terminesp Linked Data took 0.18353033065795898s
Reputation | Calculation of the PageRank for Terminesp Linked Data took 0.021548748016357422s
Interlinking | Calculation of Degree of Connection for Terminesp Linked Data took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Terminesp Linked Data took 0.001058340072631836s
Interlinking | Calculation of Clustering coefficient for Terminesp Linked Data took 4.124641418457031e-05s
Believability | Calculation of trust value for Terminesp Linked Data took 1.2874603271484375e-05s
INFO | --- Analysis for terminesp took 2.0301592350006104s
Availability | SPARQL endpoint availability check for Ontology took 4.2438507080078125e-05s
Availability | VoID file availability check for Ontology took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for Ontology took 0.17781448364257812s
Reputation | Calculation of the PageRank for Ontology took 0.020218372344970703s
Interlinking | Calculation of Degree of Connection for Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Ontology took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Ontology took 3.0040740966796875e-05s
Believability | Calculation of trust value for Ontology took 1.2636184692382812e-05s
INFO | --- Analysis for Terrorist_attack took 1.9845287799835205s
Availability | SPARQL endpoint availability check for Terrorist Attack1 took 8.606910705566406e-05s
Availability | VoID file availability check for Terrorist Attack1 took 0.0002474784851074219s
Completeness | Calculation of interlinking completeness for Terrorist Attack1 took 0.18631339073181152s
Reputation | Calculation of the PageRank for Terrorist Attack1 took 0.020337581634521484s
Interlinking | Calculation of Degree of Connection for Terrorist Attack1 took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Terrorist Attack1 took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for Terrorist Attack1 took 2.9802322387695312e-05s
Believability | Calculation of trust value for Terrorist Attack1 took 1.2636184692382812e-05s
INFO | --- Analysis for Terrorist_Attack_1 took 1.9809486865997314s
Availability | SPARQL endpoint availability check for Tesauro materias BUPM took 4.1961669921875e-05s
Availability | VoID file availability check for Tesauro materias BUPM took 0.000484466552734375s
Completeness | Calculation of interlinking completeness for Tesauro materias BUPM took 0.18401360511779785s
Reputation | Calculation of the PageRank for Tesauro materias BUPM took 0.020357608795166016s
Interlinking | Calculation of Degree of Connection for Tesauro materias BUPM took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Tesauro materias BUPM took 0.0007214546203613281s
Interlinking | Calculation of Clustering coefficient for Tesauro materias BUPM took 3.0279159545898438e-05s
Believability | Calculation of trust value for Tesauro materias BUPM took 1.2636184692382812e-05s
INFO | --- Analysis for tesauro-materias-bupm took 1.9934613704681396s
Availability | SPARQL endpoint availability check for Teseo took 8.273124694824219e-05s
Availability | VoID file availability check for Teseo took 0.000591278076171875s
Completeness | Calculation of interlinking completeness for Teseo took 0.17314362525939941s
Reputation | Calculation of the PageRank for Teseo took 0.020303726196289062s
Interlinking | Calculation of Degree of Connection for Teseo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Teseo took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for Teseo took 2.956390380859375e-05s
Believability | Calculation of trust value for Teseo took 1.0013580322265625e-05s
INFO | --- Analysis for teseo took 1.9685389995574951s
Availability | SPARQL endpoint availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 8.20159912109375e-05s
Availability | VoID file availability check for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0004150867462158203s
Completeness | Calculation of interlinking completeness for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.18593192100524902s
Reputation | Calculation of the PageRank for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.020690441131591797s
Interlinking | Calculation of Degree of Connection for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 0.0007557868957519531s
Interlinking | Calculation of Clustering coefficient for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 3.170967102050781e-05s
Believability | Calculation of trust value for Tesla Deaths: A digital record of Tesla accidents that involved a fatality took 9.775161743164062e-06s
INFO | --- Analysis for Tesla_Deaths took 1.976224660873413s
Availability | SPARQL endpoint availability check for test took 8.392333984375e-05s
Availability | VoID file availability check for test took 0.00043082237243652344s
Completeness | Calculation of interlinking completeness for test took 0.1801161766052246s
Reputation | Calculation of the PageRank for test took 0.022081375122070312s
Interlinking | Calculation of Degree of Connection for test took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for test took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for test took 2.7894973754882812e-05s
Believability | Calculation of trust value for test took 9.5367431640625e-06s
INFO | --- Analysis for test took 1.9838950634002686s
Availability | SPARQL endpoint availability check for Test took 4.220008850097656e-05s
Availability | VoID file availability check for Test took 0.000461578369140625s
Completeness | Calculation of interlinking completeness for Test took 0.17438936233520508s
Reputation | Calculation of the PageRank for Test took 0.0214383602142334s
Interlinking | Calculation of Degree of Connection for Test took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Test took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Test took 3.337860107421875e-05s
Believability | Calculation of trust value for Test took 1.430511474609375e-05s
INFO | --- Analysis for Test took 1.9586107730865479s
Availability | SPARQL endpoint availability check for test-svu took 8.702278137207031e-05s
Availability | VoID file availability check for test-svu took 0.00025177001953125s
Completeness | Calculation of interlinking completeness for test-svu took 0.17949700355529785s
Reputation | Calculation of the PageRank for test-svu took 0.020514249801635742s
Interlinking | Calculation of Degree of Connection for test-svu took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for test-svu took 0.0007116794586181641s
Interlinking | Calculation of Clustering coefficient for test-svu took 3.24249267578125e-05s
Believability | Calculation of trust value for test-svu took 1.430511474609375e-05s
INFO | --- Analysis for test-svu took 1.9829120635986328s
Availability | SPARQL endpoint availability check for Test took 4.4345855712890625e-05s
Availability | VoID file availability check for Test took 0.0004978179931640625s
Completeness | Calculation of interlinking completeness for Test took 0.18154335021972656s
Reputation | Calculation of the PageRank for Test took 0.02048349380493164s
Interlinking | Calculation of Degree of Connection for Test took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Test took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for Test took 3.457069396972656e-05s
Believability | Calculation of trust value for Test took 1.3589859008789062e-05s
INFO | --- Analysis for Test_ took 1.9824159145355225s
Availability | SPARQL endpoint availability check for xxxxx took 7.987022399902344e-05s
Availability | VoID file availability check for xxxxx took 0.00042939186096191406s
Completeness | Calculation of interlinking completeness for xxxxx took 0.17536401748657227s
Reputation | Calculation of the PageRank for xxxxx took 0.020676612854003906s
Interlinking | Calculation of Degree of Connection for xxxxx took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for xxxxx took 0.0007357597351074219s
Interlinking | Calculation of Clustering coefficient for xxxxx took 4.172325134277344e-05s
Believability | Calculation of trust value for xxxxx took 1.0013580322265625e-05s
INFO | --- Analysis for testee took 1.9892446994781494s
Availability | SPARQL endpoint availability check for Texai Lexicon took 4.410743713378906e-05s
Availability | VoID file availability check for Texai Lexicon took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Texai Lexicon took 0.17941522598266602s
Reputation | Calculation of the PageRank for Texai Lexicon took 0.021238088607788086s
Interlinking | Calculation of Degree of Connection for Texai Lexicon took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Texai Lexicon took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Texai Lexicon took 3.147125244140625e-05s
Believability | Calculation of trust value for Texai Lexicon took 8.344650268554688e-06s
INFO | --- Analysis for texai_lexicon took 1.9622600078582764s
Availability | SPARQL endpoint availability check for tharawat magazine took 8.678436279296875e-05s
Availability | VoID file availability check for tharawat magazine took 0.0005133152008056641s
Completeness | Calculation of interlinking completeness for tharawat magazine took 0.18017983436584473s
Reputation | Calculation of the PageRank for tharawat magazine took 0.02053666114807129s
Interlinking | Calculation of Degree of Connection for tharawat magazine took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for tharawat magazine took 0.0007257461547851562s
Interlinking | Calculation of Clustering coefficient for tharawat magazine took 0.00010514259338378906s
Believability | Calculation of trust value for tharawat magazine took 1.3589859008789062e-05s
INFO | --- Analysis for tharawat-magazine-com took 1.9629294872283936s
Availability | SPARQL endpoint availability check for The CIARD RING took 4.363059997558594e-05s
Availability | VoID file availability check for The CIARD RING took 0.0005526542663574219s
Completeness | Calculation of interlinking completeness for The CIARD RING took 0.18520545959472656s
Reputation | Calculation of the PageRank for The CIARD RING took 0.021281957626342773s
Interlinking | Calculation of Degree of Connection for The CIARD RING took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The CIARD RING took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for The CIARD RING took 3.0994415283203125e-05s
Believability | Calculation of trust value for The CIARD RING took 1.2874603271484375e-05s
INFO | --- Analysis for the-ciard-ring took 2.009004592895508s
Availability | SPARQL endpoint availability check for The Drug Interaction Knowledge Base took 4.482269287109375e-05s
Availability | VoID file availability check for The Drug Interaction Knowledge Base took 0.0004899501800537109s
Completeness | Calculation of interlinking completeness for The Drug Interaction Knowledge Base took 0.17455267906188965s
Reputation | Calculation of the PageRank for The Drug Interaction Knowledge Base took 0.02022862434387207s
Interlinking | Calculation of Degree of Connection for The Drug Interaction Knowledge Base took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for The Drug Interaction Knowledge Base took 0.0007274150848388672s
Interlinking | Calculation of Clustering coefficient for The Drug Interaction Knowledge Base took 3.170967102050781e-05s
Believability | Calculation of trust value for The Drug Interaction Knowledge Base took 9.059906005859375e-06s
INFO | --- Analysis for the-drug-interaction-knowledge-base took 2.0676023960113525s
Availability | SPARQL endpoint availability check for The European Library Open Dataset took 3.3158223628997803s
Availability | VoID file availability check for The European Library Open Dataset took 0.0005283355712890625s
Extra | Recovery of all triples for The European Library Open Dataset took 7.013179063796997s
Performance | Total latancy measurement for The European Library Open Dataset took 15.998934268951416s
Amount of data | Number of triples check for The European Library Open Dataset took 63.33345127105713s
Interoperability | New terms check for The European Library Open Dataset took 60.383647203445435s
Versatility | Languages check for The European Library Open Dataset took 3.193594455718994s
Interpretability | Number of blank nodes check for The European Library Open Dataset took 3.2015883922576904s
Interpretability | RDF structures check for The European Library Open Dataset took 3.2113327980041504s
Versatility | Serialization formats check for The European Library Open Dataset took 3.1900696754455566s
Availability | RDF dump link check for The European Library Open Dataset took 3.1992859840393066s
License | MR license check for The European Library Open Dataset took 3.202788829803467s
License | HR license check for The European Library Open Dataset took 3.2001724243164062s
Amount of data | Number of property check for The European Library Open Dataset took 3.203009605407715s
Understandability | Number of label check for The European Library Open Dataset took 3.702655076980591s
Understandability | URI regex check for The European Library Open Dataset took 6.339691877365112s
Understandability | Vocabs check for The European Library Open Dataset took 3.202134370803833s
Verifiability | Authors check for The European Library Open Dataset took 3.201451539993286s
Verifiability | Publishers check for The European Library Open Dataset took 3.1962790489196777s
Performance | Throughput check for The European Library Open Dataset took 32.00018858909607s
Amount of data | Check the number of entities for The European Library Open Dataset took 6.842613220214844e-05s
Verifiability | Contribs. check for The European Library Open Dataset took 3.2687783241271973s
Interlinking | sameAs chians check for The European Library Open Dataset took 3.302553176879883s
Interlinking | skos check for The European Library Open Dataset took 3.2656683921813965s
Interlinking | skos check for The European Library Open Dataset took 3.263150930404663s
Timeliness | dataset update frequency check for The European Library Open Dataset took 3.1925032138824463s
Currency | Creation date check for The European Library Open Dataset took 6.399624824523926s
Currency | Modification date check for The European Library Open Dataset took 6.399168491363525s
Rep.Conc. | URIs length for The European Library Open Dataset took 124.49679565429688s
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 3.2128584384918213s
Accuracy | Check Empty annotation labels for The European Library Open Dataset took 3.5159878730773926s
Accuracy | Check White space in annotation for The European Library Open Dataset took 0.02652287483215332s
Accuracy | Check Datatype consistency for The European Library Open Dataset took 0.02735614776611328s
Consistency | Disjoint class check for The European Library Open Dataset took 3.215867280960083s
Consistency | Check Misplaced properties for The European Library Open Dataset took 68.27374315261841s
Consistency | Misplaced classes for The European Library Open Dataset took 3.301241159439087s
Consistency | Check Ontology hijacking for The European Library Open Dataset took 4.960416078567505s
Consistency | Check Invalid usage of undefined classes for The European Library Open Dataset took 1.3572769165039062s
Consistency | Check Invalid usage of undefined properties for The European Library Open Dataset took 66.08192300796509s
Conciseness | Check Extensional conciseness for The European Library Open Dataset took 0.03169560432434082s
Conciseness | Check Intensional conciseness for The European Library Open Dataset took 3.1919612884521484s
Security | Sign check for The European Library Open Dataset took 3.202629804611206s
Availability | Check URIs Dereferenciability for The European Library Open Dataset took 16.019527673721313s
Completeness | Calculation of interlinking completeness for The European Library Open Dataset took 0.2313375473022461s
Reputation | Calculation of the PageRank for The European Library Open Dataset took 0.020926713943481445s
Interlinking | Calculation of Degree of Connection for The European Library Open Dataset took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for The European Library Open Dataset took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for The European Library Open Dataset took 6.198883056640625e-05s
Interoperability | Check the re-using of existing vocabs for The European Library Open Dataset took 1.6689300537109375e-06s
Believability | Calculation of trust value for The European Library Open Dataset took 1.1205673217773438e-05s
INFO | --- Analysis for the-european-library-open-dataset took 909.8958640098572s
Availability | SPARQL endpoint availability check for The Eurostat Linked Data took 4.5299530029296875e-05s
Availability | VoID file availability check for The Eurostat Linked Data took 0.0004982948303222656s
Completeness | Calculation of interlinking completeness for The Eurostat Linked Data took 0.1744060516357422s
Reputation | Calculation of the PageRank for The Eurostat Linked Data took 0.02267313003540039s
Interlinking | Calculation of Degree of Connection for The Eurostat Linked Data took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for The Eurostat Linked Data took 0.0007185935974121094s
Interlinking | Calculation of Clustering coefficient for The Eurostat Linked Data took 9.608268737792969e-05s
Believability | Calculation of trust value for The Eurostat Linked Data took 1.239776611328125e-05s
INFO | --- Analysis for the-eurostat-linked-data took 2.004272699356079s
Availability | SPARQL endpoint availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 4.00543212890625e-05s
Availability | VoID file availability check for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0004928112030029297s
Completeness | Calculation of interlinking completeness for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.19807696342468262s
Reputation | Calculation of the PageRank for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.020272016525268555s
Interlinking | Calculation of Degree of Connection for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 2.86102294921875e-05s
Believability | Calculation of trust value for The Kazan University Museum as Linked Open Data in the Europeana Data Model took 1.2874603271484375e-05s
INFO | --- Analysis for the-kazan-university-museum-as-linked-open-data-in-the-europeana-data-model took 1.9917263984680176s
Availability | SPARQL endpoint availability check for The Living LOD Cloud took 8.463859558105469e-05s
Availability | VoID file availability check for The Living LOD Cloud took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for The Living LOD Cloud took 0.18068385124206543s
Reputation | Calculation of the PageRank for The Living LOD Cloud took 0.020447969436645508s
Interlinking | Calculation of Degree of Connection for The Living LOD Cloud took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for The Living LOD Cloud took 0.0009093284606933594s
Interlinking | Calculation of Clustering coefficient for The Living LOD Cloud took 7.700920104980469e-05s
Believability | Calculation of trust value for The Living LOD Cloud took 1.2159347534179688e-05s
INFO | --- Analysis for the-living-lod-cloud took 1.9837846755981445s
Availability | SPARQL endpoint availability check for The MIDI Linked Data Cloud took 5.2928924560546875e-05s
Availability | VoID file availability check for The MIDI Linked Data Cloud took 0.00025272369384765625s
Completeness | Calculation of interlinking completeness for The MIDI Linked Data Cloud took 0.18101000785827637s
Reputation | Calculation of the PageRank for The MIDI Linked Data Cloud took 0.02027750015258789s
Interlinking | Calculation of Degree of Connection for The MIDI Linked Data Cloud took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for The MIDI Linked Data Cloud took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for The MIDI Linked Data Cloud took 2.9087066650390625e-05s
Believability | Calculation of trust value for The MIDI Linked Data Cloud took 7.152557373046875e-06s
INFO | --- Analysis for the-midi-linked-data-cloud took 1.955876111984253s
Availability | SPARQL endpoint availability check for The View From took 0.10125970840454102s
Availability | VoID file availability check for The View From took 0.00024628639221191406s
Completeness | Calculation of interlinking completeness for The View From took 0.16956472396850586s
Reputation | Calculation of the PageRank for The View From took 0.02034473419189453s
Interlinking | Calculation of Degree of Connection for The View From took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for The View From took 0.0007302761077880859s
Interlinking | Calculation of Clustering coefficient for The View From took 8.606910705566406e-05s
Believability | Calculation of trust value for The View From took 7.3909759521484375e-06s
INFO | --- Analysis for the-view-from took 2.059420585632324s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 9.1552734375e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0006375312805175781s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.17619943618774414s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020212411880493164s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.9087066650390625e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.2636184692382812e-05s
INFO | --- Analysis for The_Central_Bank_of_the_Republic_of_Uzbekistan took 1.9571583271026611s
Availability | SPARQL endpoint availability check for Open data of Uzbekistan took 8.320808410644531e-05s
Availability | VoID file availability check for Open data of Uzbekistan took 0.0004825592041015625s
Completeness | Calculation of interlinking completeness for Open data of Uzbekistan took 0.17724132537841797s
Reputation | Calculation of the PageRank for Open data of Uzbekistan took 0.020107746124267578s
Interlinking | Calculation of Degree of Connection for Open data of Uzbekistan took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Open data of Uzbekistan took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for Open data of Uzbekistan took 2.765655517578125e-05s
Believability | Calculation of trust value for Open data of Uzbekistan took 1.2636184692382812e-05s
INFO | --- Analysis for The_Respublic_of_Uzbekistan took 1.9491400718688965s
Availability | SPARQL endpoint availability check for The Content Wrangler took 4.1484832763671875e-05s
Availability | VoID file availability check for The Content Wrangler took 0.00046825408935546875s
Completeness | Calculation of interlinking completeness for The Content Wrangler took 0.17190217971801758s
Reputation | Calculation of the PageRank for The Content Wrangler took 0.020366430282592773s
Interlinking | Calculation of Degree of Connection for The Content Wrangler took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for The Content Wrangler took 0.0007207393646240234s
Interlinking | Calculation of Clustering coefficient for The Content Wrangler took 0.000102996826171875s
Believability | Calculation of trust value for The Content Wrangler took 1.3113021850585938e-05s
INFO | --- Analysis for thecontentwrangler-com took 2.025747537612915s
Availability | SPARQL endpoint availability check for Thesaurus BNCF took 4.0531158447265625e-05s
Availability | VoID file availability check for Thesaurus BNCF took 0.0004875659942626953s
Completeness | Calculation of interlinking completeness for Thesaurus BNCF took 0.1765451431274414s
Reputation | Calculation of the PageRank for Thesaurus BNCF took 0.02043604850769043s
Interlinking | Calculation of Degree of Connection for Thesaurus BNCF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Thesaurus BNCF took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for Thesaurus BNCF took 3.0279159545898438e-05s
Believability | Calculation of trust value for Thesaurus BNCF took 7.3909759521484375e-06s
INFO | --- Analysis for thesaurus-bncf took 1.9531409740447998s
Availability | SPARQL endpoint availability check for Thesaurus Datenwissen took 3.933906555175781e-05s
Availability | VoID file availability check for Thesaurus Datenwissen took 0.00025081634521484375s
Completeness | Calculation of interlinking completeness for Thesaurus Datenwissen took 0.17553353309631348s
Reputation | Calculation of the PageRank for Thesaurus Datenwissen took 0.022191286087036133s
Interlinking | Calculation of Degree of Connection for Thesaurus Datenwissen took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Thesaurus Datenwissen took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Thesaurus Datenwissen took 2.86102294921875e-05s
Believability | Calculation of trust value for Thesaurus Datenwissen took 1.1920928955078125e-05s
INFO | --- Analysis for thesaurus-datenwissen took 2.0101253986358643s
Availability | SPARQL endpoint availability check for Thesaurus W for Local Archives took 0.9942498207092285s
Availability | VoID file availability check for Thesaurus W for Local Archives took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for Thesaurus W for Local Archives took 0.17447996139526367s
Reputation | Calculation of the PageRank for Thesaurus W for Local Archives took 0.02161264419555664s
Interlinking | Calculation of Degree of Connection for Thesaurus W for Local Archives took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Thesaurus W for Local Archives took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Thesaurus W for Local Archives took 7.009506225585938e-05s
Believability | Calculation of trust value for Thesaurus W for Local Archives took 6.4373016357421875e-06s
INFO | --- Analysis for thesaurus-w took 3.9389703273773193s
Availability | SPARQL endpoint availability check for theses.fr took 4.00543212890625e-05s
Availability | VoID file availability check for theses.fr took 0.0004506111145019531s
Completeness | Calculation of interlinking completeness for theses.fr took 0.17663264274597168s
Reputation | Calculation of the PageRank for theses.fr took 0.020625591278076172s
Interlinking | Calculation of Degree of Connection for theses.fr took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for theses.fr took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for theses.fr took 4.887580871582031e-05s
Believability | Calculation of trust value for theses.fr took 1.4066696166992188e-05s
INFO | --- Analysis for thesesfr took 1.9911646842956543s
Availability | SPARQL endpoint availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 4.267692565917969e-05s
Availability | VoID file availability check for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0005109310150146484s
Completeness | Calculation of interlinking completeness for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.23977398872375488s
Reputation | Calculation of the PageRank for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.020426511764526367s
Interlinking | Calculation of Degree of Connection for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 3.3855438232421875e-05s
Believability | Calculation of trust value for ThinkPhile (Publisher | Blog , Content ,News , and Media Website) took 1.33514404296875e-05s
INFO | --- Analysis for Thinkphile took 2.0279500484466553s
Availability | SPARQL endpoint availability check for ThIST took 0.00011205673217773438s
Availability | VoID file availability check for ThIST took 0.00046563148498535156s
Completeness | Calculation of interlinking completeness for ThIST took 0.17439055442810059s
Reputation | Calculation of the PageRank for ThIST took 0.020469188690185547s
Interlinking | Calculation of Degree of Connection for ThIST took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for ThIST took 0.0007028579711914062s
Interlinking | Calculation of Clustering coefficient for ThIST took 8.320808410644531e-05s
Believability | Calculation of trust value for ThIST took 1.0728836059570312e-05s
INFO | --- Analysis for thist took 1.9692580699920654s
Availability | SPARQL endpoint availability check for TIP took 39.00126767158508s
Availability | VoID file availability check for TIP took 0.0005128383636474609s
Completeness | Calculation of interlinking completeness for TIP took 0.1795792579650879s
Reputation | Calculation of the PageRank for TIP took 0.021275758743286133s
Interlinking | Calculation of Degree of Connection for TIP took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for TIP took 0.0007293224334716797s
Interlinking | Calculation of Clustering coefficient for TIP took 0.0001049041748046875s
Believability | Calculation of trust value for TIP took 1.2874603271484375e-05s
INFO | --- Analysis for tip took 79.65262341499329s
Availability | SPARQL endpoint availability check for Topography based Hydrological Model took 8.511543273925781e-05s
Availability | VoID file availability check for Topography based Hydrological Model took 0.00023102760314941406s
Completeness | Calculation of interlinking completeness for Topography based Hydrological Model took 0.1728653907775879s
Reputation | Calculation of the PageRank for Topography based Hydrological Model took 0.021734237670898438s
Interlinking | Calculation of Degree of Connection for Topography based Hydrological Model took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Topography based Hydrological Model took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for Topography based Hydrological Model took 3.933906555175781e-05s
Believability | Calculation of trust value for Topography based Hydrological Model took 1.1444091796875e-05s
INFO | --- Analysis for TOPMODEL took 1.9765563011169434s
Availability | SPARQL endpoint availability check for Tourpedia took 8.559226989746094e-05s
Availability | VoID file availability check for Tourpedia took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Tourpedia took 0.17379498481750488s
Reputation | Calculation of the PageRank for Tourpedia took 0.021310091018676758s
Interlinking | Calculation of Degree of Connection for Tourpedia took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Tourpedia took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for Tourpedia took 3.0040740966796875e-05s
Believability | Calculation of trust value for Tourpedia took 1.1205673217773438e-05s
INFO | --- Analysis for tourpedia took 2.003511428833008s
Availability | SPARQL endpoint availability check for Observation dataset of forest ecosystems  took 4.100799560546875e-05s
Availability | VoID file availability check for Observation dataset of forest ecosystems  took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for Observation dataset of forest ecosystems  took 0.1857895851135254s
Reputation | Calculation of the PageRank for Observation dataset of forest ecosystems  took 0.020236492156982422s
Interlinking | Calculation of Degree of Connection for Observation dataset of forest ecosystems  took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for Observation dataset of forest ecosystems  took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for Observation dataset of forest ecosystems  took 3.218650817871094e-05s
Believability | Calculation of trust value for Observation dataset of forest ecosystems  took 1.2636184692382812e-05s
INFO | --- Analysis for TP-data took 2.090141773223877s
Availability | SPARQL endpoint availability check for Traditional Korean Medicine Ontology took 3.9577484130859375e-05s
Availability | VoID file availability check for Traditional Korean Medicine Ontology took 0.0004935264587402344s
Completeness | Calculation of interlinking completeness for Traditional Korean Medicine Ontology took 0.1748957633972168s
Reputation | Calculation of the PageRank for Traditional Korean Medicine Ontology took 0.02028059959411621s
Interlinking | Calculation of Degree of Connection for Traditional Korean Medicine Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Traditional Korean Medicine Ontology took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Traditional Korean Medicine Ontology took 4.1961669921875e-05s
Believability | Calculation of trust value for Traditional Korean Medicine Ontology took 1.239776611328125e-05s
INFO | --- Analysis for traditional-korean-medicine took 1.9851047992706299s
Availability | SPARQL endpoint availability check for Traffic Scotland took 4.4345855712890625e-05s
Availability | VoID file availability check for Traffic Scotland took 0.0009984970092773438s
Completeness | Calculation of interlinking completeness for Traffic Scotland took 0.18215155601501465s
Reputation | Calculation of the PageRank for Traffic Scotland took 0.0204923152923584s
Interlinking | Calculation of Degree of Connection for Traffic Scotland took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Traffic Scotland took 0.0006909370422363281s
Interlinking | Calculation of Clustering coefficient for Traffic Scotland took 3.4332275390625e-05s
Believability | Calculation of trust value for Traffic Scotland took 1.239776611328125e-05s
INFO | --- Analysis for traffic-scotland took 2.0001909732818604s
Availability | SPARQL endpoint availability check for Transparency International Linked Data took 4.076957702636719e-05s
Availability | VoID file availability check for Transparency International Linked Data took 0.00048542022705078125s
Completeness | Calculation of interlinking completeness for Transparency International Linked Data took 0.18274426460266113s
Reputation | Calculation of the PageRank for Transparency International Linked Data took 0.020628690719604492s
Interlinking | Calculation of Degree of Connection for Transparency International Linked Data took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Transparency International Linked Data took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for Transparency International Linked Data took 9.870529174804688e-05s
Believability | Calculation of trust value for Transparency International Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for transparency-linked-data took 1.9866325855255127s
Availability | SPARQL endpoint availability check for transport.data.gov.uk took 8.535385131835938e-05s
Availability | VoID file availability check for transport.data.gov.uk took 0.00030541419982910156s
Completeness | Calculation of interlinking completeness for transport.data.gov.uk took 0.17491769790649414s
Reputation | Calculation of the PageRank for transport.data.gov.uk took 0.020323753356933594s
Interlinking | Calculation of Degree of Connection for transport.data.gov.uk took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for transport.data.gov.uk took 0.0007350444793701172s
Interlinking | Calculation of Clustering coefficient for transport.data.gov.uk took 8.487701416015625e-05s
Believability | Calculation of trust value for transport.data.gov.uk took 1.2874603271484375e-05s
INFO | --- Analysis for transport-data-gov-uk took 1.984018325805664s
Availability | SPARQL endpoint availability check for OpenUpLabs Transport took 4.0531158447265625e-05s
Availability | VoID file availability check for OpenUpLabs Transport took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for OpenUpLabs Transport took 0.175581693649292s
Reputation | Calculation of the PageRank for OpenUpLabs Transport took 0.022196531295776367s
Interlinking | Calculation of Degree of Connection for OpenUpLabs Transport took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for OpenUpLabs Transport took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for OpenUpLabs Transport took 2.7179718017578125e-05s
Believability | Calculation of trust value for OpenUpLabs Transport took 1.1920928955078125e-05s
INFO | --- Analysis for transport-openuplabs took 1.9921975135803223s
Availability | SPARQL endpoint availability check for Trelios took 8.487701416015625e-05s
Availability | VoID file availability check for Trelios took 0.0005125999450683594s
Completeness | Calculation of interlinking completeness for Trelios took 0.18225431442260742s
Reputation | Calculation of the PageRank for Trelios took 0.020195960998535156s
Interlinking | Calculation of Degree of Connection for Trelios took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Trelios took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Trelios took 1.1205673217773438e-05s
Believability | Calculation of trust value for Trelios took 1.239776611328125e-05s
INFO | --- Analysis for Trelios took 1.954038143157959s
Availability | SPARQL endpoint availability check for Twarql took 8.58306884765625e-05s
Availability | VoID file availability check for Twarql took 0.000469207763671875s
Completeness | Calculation of interlinking completeness for Twarql took 0.18909287452697754s
Reputation | Calculation of the PageRank for Twarql took 0.020261287689208984s
Interlinking | Calculation of Degree of Connection for Twarql took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Twarql took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Twarql took 6.461143493652344e-05s
Believability | Calculation of trust value for Twarql took 1.2159347534179688e-05s
INFO | --- Analysis for twarql took 2.001089572906494s
Availability | SPARQL endpoint availability check for TWC Data-gov took 8.249282836914062e-05s
Availability | VoID file availability check for TWC Data-gov took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for TWC Data-gov took 0.18192648887634277s
Reputation | Calculation of the PageRank for TWC Data-gov took 0.021671295166015625s
Interlinking | Calculation of Degree of Connection for TWC Data-gov took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for TWC Data-gov took 0.0007193088531494141s
Interlinking | Calculation of Clustering coefficient for TWC Data-gov took 3.4809112548828125e-05s
Believability | Calculation of trust value for TWC Data-gov took 7.867813110351562e-06s
INFO | --- Analysis for twc-data-gov took 2.0049617290496826s
Availability | SPARQL endpoint availability check for Tetherless World Constellation Demonstrations took 8.225440979003906e-05s
Availability | VoID file availability check for Tetherless World Constellation Demonstrations took 0.0004868507385253906s
Completeness | Calculation of interlinking completeness for Tetherless World Constellation Demonstrations took 0.17347478866577148s
Reputation | Calculation of the PageRank for Tetherless World Constellation Demonstrations took 0.020524024963378906s
Interlinking | Calculation of Degree of Connection for Tetherless World Constellation Demonstrations took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Tetherless World Constellation Demonstrations took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Tetherless World Constellation Demonstrations took 3.0040740966796875e-05s
Believability | Calculation of trust value for Tetherless World Constellation Demonstrations took 1.3113021850585938e-05s
INFO | --- Analysis for twc-demos took 2.025686740875244s
Availability | SPARQL endpoint availability check for HealthData.gov Platform (HDP) on the Semantic Web took 8.249282836914062e-05s
Availability | VoID file availability check for HealthData.gov Platform (HDP) on the Semantic Web took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for HealthData.gov Platform (HDP) on the Semantic Web took 0.1793503761291504s
Reputation | Calculation of the PageRank for HealthData.gov Platform (HDP) on the Semantic Web took 0.022168874740600586s
Interlinking | Calculation of Degree of Connection for HealthData.gov Platform (HDP) on the Semantic Web took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for HealthData.gov Platform (HDP) on the Semantic Web took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for HealthData.gov Platform (HDP) on the Semantic Web took 3.3855438232421875e-05s
Believability | Calculation of trust value for HealthData.gov Platform (HDP) on the Semantic Web took 1.1205673217773438e-05s
INFO | --- Analysis for twc-healthdata took 2.0306503772735596s
Availability | SPARQL endpoint availability check for Instance Hub (all) took 8.416175842285156e-05s
Availability | VoID file availability check for Instance Hub (all) took 0.0006077289581298828s
Completeness | Calculation of interlinking completeness for Instance Hub (all) took 0.18537688255310059s
Reputation | Calculation of the PageRank for Instance Hub (all) took 0.02034783363342285s
Interlinking | Calculation of Degree of Connection for Instance Hub (all) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Instance Hub (all) took 0.0007622241973876953s
Interlinking | Calculation of Clustering coefficient for Instance Hub (all) took 7.224082946777344e-05s
Believability | Calculation of trust value for Instance Hub (all) took 1.1920928955078125e-05s
INFO | --- Analysis for twc-hub took 1.973785400390625s
Availability | SPARQL endpoint availability check for IEEE VIS Source Data took 0.00010395050048828125s
Availability | VoID file availability check for IEEE VIS Source Data took 0.00089263916015625s
Completeness | Calculation of interlinking completeness for IEEE VIS Source Data took 0.1751859188079834s
Reputation | Calculation of the PageRank for IEEE VIS Source Data took 0.020458459854125977s
Interlinking | Calculation of Degree of Connection for IEEE VIS Source Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for IEEE VIS Source Data took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for IEEE VIS Source Data took 0.00010418891906738281s
Believability | Calculation of trust value for IEEE VIS Source Data took 1.3589859008789062e-05s
INFO | --- Analysis for twc-ieeevis took 1.97762131690979s
Availability | SPARQL endpoint availability check for TWC: Linking Open Government Data took 7.963180541992188e-05s
Availability | VoID file availability check for TWC: Linking Open Government Data took 0.0005469322204589844s
Completeness | Calculation of interlinking completeness for TWC: Linking Open Government Data took 0.17928624153137207s
Reputation | Calculation of the PageRank for TWC: Linking Open Government Data took 0.02056288719177246s
Interlinking | Calculation of Degree of Connection for TWC: Linking Open Government Data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for TWC: Linking Open Government Data took 0.0007007122039794922s
Interlinking | Calculation of Clustering coefficient for TWC: Linking Open Government Data took 8.654594421386719e-05s
Believability | Calculation of trust value for TWC: Linking Open Government Data took 9.059906005859375e-06s
INFO | --- Analysis for twc-logd took 2.009242296218872s
Availability | SPARQL endpoint availability check for twc-opendap took 4.291534423828125e-05s
Availability | VoID file availability check for twc-opendap took 0.0005040168762207031s
Completeness | Calculation of interlinking completeness for twc-opendap took 0.17420220375061035s
Reputation | Calculation of the PageRank for twc-opendap took 0.0205230712890625s
Interlinking | Calculation of Degree of Connection for twc-opendap took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for twc-opendap took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for twc-opendap took 6.794929504394531e-05s
Believability | Calculation of trust value for twc-opendap took 1.0967254638671875e-05s
INFO | --- Analysis for twc-opendap took 2.000612497329712s
Availability | SPARQL endpoint availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 8.440017700195312e-05s
Availability | VoID file availability check for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0004723072052001953s
Completeness | Calculation of interlinking completeness for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.20524144172668457s
Reputation | Calculation of the PageRank for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.02047562599182129s
Interlinking | Calculation of Degree of Connection for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 3.170967102050781e-05s
Believability | Calculation of trust value for TweetsKB - A Public and Large-Scale RDF Corpus of Annotated Tweets took 1.0251998901367188e-05s
INFO | --- Analysis for tweetskb took 2.00370454788208s
Availability | SPARQL endpoint availability check for Twitter Linked Data Service took 4.124641418457031e-05s
Availability | VoID file availability check for Twitter Linked Data Service took 0.00021409988403320312s
Completeness | Calculation of interlinking completeness for Twitter Linked Data Service took 0.21374201774597168s
Reputation | Calculation of the PageRank for Twitter Linked Data Service took 0.022001981735229492s
Interlinking | Calculation of Degree of Connection for Twitter Linked Data Service took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Twitter Linked Data Service took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Twitter Linked Data Service took 3.147125244140625e-05s
Believability | Calculation of trust value for Twitter Linked Data Service took 5.7220458984375e-06s
INFO | --- Analysis for twitter-lids took 2.008490800857544s
Availability | SPARQL endpoint availability check for typepad took 8.463859558105469e-05s
Availability | VoID file availability check for typepad took 0.0004425048828125s
Completeness | Calculation of interlinking completeness for typepad took 0.1748976707458496s
Reputation | Calculation of the PageRank for typepad took 0.02130270004272461s
Interlinking | Calculation of Degree of Connection for typepad took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for typepad took 0.0007388591766357422s
Interlinking | Calculation of Clustering coefficient for typepad took 5.173683166503906e-05s
Believability | Calculation of trust value for typepad took 1.0728836059570312e-05s
INFO | --- Analysis for typepad took 1.975553274154663s
Availability | SPARQL endpoint availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.8925175666809082s
Availability | VoID file availability check for Linked Data Service der Universitätsbibliothek Mannheim took 0.00046896934509277344s
Completeness | Calculation of interlinking completeness for Linked Data Service der Universitätsbibliothek Mannheim took 0.18362832069396973s
Reputation | Calculation of the PageRank for Linked Data Service der Universitätsbibliothek Mannheim took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for Linked Data Service der Universitätsbibliothek Mannheim took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Linked Data Service der Universitätsbibliothek Mannheim took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Linked Data Service der Universitätsbibliothek Mannheim took 4.220008850097656e-05s
Believability | Calculation of trust value for Linked Data Service der Universitätsbibliothek Mannheim took 1.2636184692382812e-05s
INFO | --- Analysis for ub-mannheim-linked-data took 3.6057004928588867s
Availability | SPARQL endpoint availability check for Uberblic.org took 8.320808410644531e-05s
Availability | VoID file availability check for Uberblic.org took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Uberblic.org took 0.18178915977478027s
Reputation | Calculation of the PageRank for Uberblic.org took 0.022092819213867188s
Interlinking | Calculation of Degree of Connection for Uberblic.org took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Uberblic.org took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Uberblic.org took 0.00010228157043457031s
Believability | Calculation of trust value for Uberblic.org took 1.0967254638671875e-05s
INFO | --- Analysis for uberblic took 1.9742755889892578s
Availability | SPARQL endpoint availability check for UDante in LiLa took 0.5872702598571777s
Availability | VoID file availability check for UDante in LiLa took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for UDante in LiLa took 0.18380284309387207s
Reputation | Calculation of the PageRank for UDante in LiLa took 0.020433902740478516s
Interlinking | Calculation of Degree of Connection for UDante in LiLa took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UDante in LiLa took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for UDante in LiLa took 3.600120544433594e-05s
Believability | Calculation of trust value for UDante in LiLa took 1.049041748046875e-05s
INFO | --- Analysis for UDante took 2.9502577781677246s
Availability | SPARQL endpoint availability check for Unified Foundational Ontology took 8.296966552734375e-05s
Availability | VoID file availability check for Unified Foundational Ontology took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Unified Foundational Ontology took 0.1747734546661377s
Reputation | Calculation of the PageRank for Unified Foundational Ontology took 0.020465612411499023s
Interlinking | Calculation of Degree of Connection for Unified Foundational Ontology took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Unified Foundational Ontology took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Unified Foundational Ontology took 3.0994415283203125e-05s
Believability | Calculation of trust value for Unified Foundational Ontology took 1.0728836059570312e-05s
INFO | --- Analysis for ufo took 1.9743590354919434s
Availability | SPARQL endpoint availability check for Uganda Disasters took 8.511543273925781e-05s
Availability | VoID file availability check for Uganda Disasters took 0.0004515647888183594s
Completeness | Calculation of interlinking completeness for Uganda Disasters took 0.18781733512878418s
Reputation | Calculation of the PageRank for Uganda Disasters took 0.021168947219848633s
Interlinking | Calculation of Degree of Connection for Uganda Disasters took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Uganda Disasters took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Uganda Disasters took 4.673004150390625e-05s
Believability | Calculation of trust value for Uganda Disasters took 1.0728836059570312e-05s
INFO | --- Analysis for Uganda-Disasters-rdf-data_ took 2.016291618347168s
Availability | SPARQL endpoint availability check for UNESCO Institute for Statistics (UIS) Linked Data took 8.20159912109375e-05s
Availability | VoID file availability check for UNESCO Institute for Statistics (UIS) Linked Data took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for UNESCO Institute for Statistics (UIS) Linked Data took 0.1780078411102295s
Reputation | Calculation of the PageRank for UNESCO Institute for Statistics (UIS) Linked Data took 0.02028512954711914s
Interlinking | Calculation of Degree of Connection for UNESCO Institute for Statistics (UIS) Linked Data took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for UNESCO Institute for Statistics (UIS) Linked Data took 0.000728607177734375s
Interlinking | Calculation of Clustering coefficient for UNESCO Institute for Statistics (UIS) Linked Data took 9.72747802734375e-05s
Believability | Calculation of trust value for UNESCO Institute for Statistics (UIS) Linked Data took 1.0967254638671875e-05s
INFO | --- Analysis for uis-linked-data took 2.0024404525756836s
Availability | SPARQL endpoint availability check for UK Legislation took 8.225440979003906e-05s
Availability | VoID file availability check for UK Legislation took 0.00021123886108398438s
Completeness | Calculation of interlinking completeness for UK Legislation took 0.18720197677612305s
Reputation | Calculation of the PageRank for UK Legislation took 0.020388126373291016s
Interlinking | Calculation of Degree of Connection for UK Legislation took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UK Legislation took 0.0007109642028808594s
Interlinking | Calculation of Clustering coefficient for UK Legislation took 8.606910705566406e-05s
Believability | Calculation of trust value for UK Legislation took 1.049041748046875e-05s
INFO | --- Analysis for uk-legislation-api took 1.980567216873169s
Availability | SPARQL endpoint availability check for UK Postcodes took 8.034706115722656e-05s
Availability | VoID file availability check for UK Postcodes took 0.000453948974609375s
Completeness | Calculation of interlinking completeness for UK Postcodes took 0.1837632656097412s
Reputation | Calculation of the PageRank for UK Postcodes took 0.02222132682800293s
Interlinking | Calculation of Degree of Connection for UK Postcodes took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for UK Postcodes took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for UK Postcodes took 5.698204040527344e-05s
Believability | Calculation of trust value for UK Postcodes took 1.1682510375976562e-05s
INFO | --- Analysis for uk-postcodes took 1.9841153621673584s
Availability | SPARQL endpoint availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 4.00543212890625e-05s
Availability | VoID file availability check for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.1747274398803711s
Reputation | Calculation of the PageRank for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.020614147186279297s
Interlinking | Calculation of Degree of Connection for UMBEL (Upper Mapping and Binding Exchange Layer) took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for UMBEL (Upper Mapping and Binding Exchange Layer) took 0.00011801719665527344s
Believability | Calculation of trust value for UMBEL (Upper Mapping and Binding Exchange Layer) took 1.049041748046875e-05s
INFO | --- Analysis for umbel took 1.9461839199066162s
Availability | SPARQL endpoint availability check for UMTHES took 3.886222839355469e-05s
Availability | VoID file availability check for UMTHES took 0.00046133995056152344s
Completeness | Calculation of interlinking completeness for UMTHES took 0.1747877597808838s
Reputation | Calculation of the PageRank for UMTHES took 0.0204620361328125s
Interlinking | Calculation of Degree of Connection for UMTHES took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for UMTHES took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for UMTHES took 4.0531158447265625e-05s
Believability | Calculation of trust value for UMTHES took 1.1682510375976562e-05s
INFO | --- Analysis for umthes took 1.9793331623077393s
Availability | SPARQL endpoint availability check for UN Hazardous Materials Numbers took 4.00543212890625e-05s
Availability | VoID file availability check for UN Hazardous Materials Numbers took 0.00046181678771972656s
Completeness | Calculation of interlinking completeness for UN Hazardous Materials Numbers took 0.1830766201019287s
Reputation | Calculation of the PageRank for UN Hazardous Materials Numbers took 0.020424365997314453s
Interlinking | Calculation of Degree of Connection for UN Hazardous Materials Numbers took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UN Hazardous Materials Numbers took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for UN Hazardous Materials Numbers took 3.123283386230469e-05s
Believability | Calculation of trust value for UN Hazardous Materials Numbers took 1.0728836059570312e-05s
INFO | --- Analysis for un-hazardous-numbers took 1.9883408546447754s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 8.106231689453125e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.000457763671875s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.1741328239440918s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.020419597625732422s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 8.106231689453125e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0007314682006835938s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.0994415283203125e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.0967254638671875e-05s
INFO | --- Analysis for unesco-thesaurus took 2.0038583278656006s
Availability | SPARQL endpoint availability check for UNESCO Thesaurus took 8.273124694824219e-05s
Availability | VoID file availability check for UNESCO Thesaurus took 0.001041412353515625s
Completeness | Calculation of interlinking completeness for UNESCO Thesaurus took 0.17484712600708008s
Reputation | Calculation of the PageRank for UNESCO Thesaurus took 0.021279573440551758s
Interlinking | Calculation of Degree of Connection for UNESCO Thesaurus took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNESCO Thesaurus took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for UNESCO Thesaurus took 3.266334533691406e-05s
Believability | Calculation of trust value for UNESCO Thesaurus took 1.33514404296875e-05s
INFO | --- Analysis for unescothes took 2.0132057666778564s
Availability | SPARQL endpoint availability check for UniProt took 8.296966552734375e-05s
Availability | VoID file availability check for UniProt took 0.00024175643920898438s
Completeness | Calculation of interlinking completeness for UniProt took 0.1811976432800293s
Reputation | Calculation of the PageRank for UniProt took 0.02146768569946289s
Interlinking | Calculation of Degree of Connection for UniProt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UniProt took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for UniProt took 3.743171691894531e-05s
Believability | Calculation of trust value for UniProt took 1.2874603271484375e-05s
INFO | --- Analysis for UniProt took 1.9860365390777588s
Availability | SPARQL endpoint availability check for UniProt took 8.344650268554688e-05s
Availability | VoID file availability check for UniProt took 0.0005154609680175781s
Completeness | Calculation of interlinking completeness for UniProt took 0.18346738815307617s
Reputation | Calculation of the PageRank for UniProt took 0.020223379135131836s
Interlinking | Calculation of Degree of Connection for UniProt took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UniProt took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for UniProt took 4.792213439941406e-05s
Believability | Calculation of trust value for UniProt took 1.2874603271484375e-05s
INFO | --- Analysis for uniprot took 1.985954999923706s
Availability | SPARQL endpoint availability check for UniProt citations took 8.249282836914062e-05s
Availability | VoID file availability check for UniProt citations took 0.0004901885986328125s
Completeness | Calculation of interlinking completeness for UniProt citations took 0.1819756031036377s
Reputation | Calculation of the PageRank for UniProt citations took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for UniProt citations took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UniProt citations took 0.0006966590881347656s
Interlinking | Calculation of Clustering coefficient for UniProt citations took 3.123283386230469e-05s
Believability | Calculation of trust value for UniProt citations took 1.2636184692382812e-05s
INFO | --- Analysis for uniprot-citations took 2.009742259979248s
Availability | SPARQL endpoint availability check for UniProt databases took 4.029273986816406e-05s
Availability | VoID file availability check for UniProt databases took 0.0004985332489013672s
Completeness | Calculation of interlinking completeness for UniProt databases took 0.17255187034606934s
Reputation | Calculation of the PageRank for UniProt databases took 0.02036118507385254s
Interlinking | Calculation of Degree of Connection for UniProt databases took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for UniProt databases took 0.0007419586181640625s
Interlinking | Calculation of Clustering coefficient for UniProt databases took 3.0517578125e-05s
Believability | Calculation of trust value for UniProt databases took 1.2159347534179688e-05s
INFO | --- Analysis for uniprot-databases took 1.9948046207427979s
Availability | SPARQL endpoint availability check for uniprot-metadata took 8.0108642578125e-05s
Availability | VoID file availability check for uniprot-metadata took 0.0004980564117431641s
Completeness | Calculation of interlinking completeness for uniprot-metadata took 0.18186688423156738s
Reputation | Calculation of the PageRank for uniprot-metadata took 0.02254462242126465s
Interlinking | Calculation of Degree of Connection for uniprot-metadata took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for uniprot-metadata took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for uniprot-metadata took 6.270408630371094e-05s
Believability | Calculation of trust value for uniprot-metadata took 1.0967254638671875e-05s
INFO | --- Analysis for uniprot-metadata took 2.0017306804656982s
Availability | SPARQL endpoint availability check for UniProtKB Taxonomy took 3.981590270996094e-05s
Availability | VoID file availability check for UniProtKB Taxonomy took 0.0004572868347167969s
Completeness | Calculation of interlinking completeness for UniProtKB Taxonomy took 0.17427897453308105s
Reputation | Calculation of the PageRank for UniProtKB Taxonomy took 0.020442485809326172s
Interlinking | Calculation of Degree of Connection for UniProtKB Taxonomy took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProtKB Taxonomy took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for UniProtKB Taxonomy took 3.1948089599609375e-05s
Believability | Calculation of trust value for UniProtKB Taxonomy took 1.049041748046875e-05s
INFO | --- Analysis for uniprot-taxonomy took 1.9555742740631104s
Availability | SPARQL endpoint availability check for UniProt UniParc took 3.886222839355469e-05s
Availability | VoID file availability check for UniProt UniParc took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for UniProt UniParc took 0.17914772033691406s
Reputation | Calculation of the PageRank for UniProt UniParc took 0.020525693893432617s
Interlinking | Calculation of Degree of Connection for UniProt UniParc took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UniProt UniParc took 0.0007190704345703125s
Interlinking | Calculation of Clustering coefficient for UniProt UniParc took 3.123283386230469e-05s
Believability | Calculation of trust value for UniProt UniParc took 1.3589859008789062e-05s
INFO | --- Analysis for uniprot-uniparc took 2.002762794494629s
Availability | SPARQL endpoint availability check for UniProt UniPathway took 4.172325134277344e-05s
Availability | VoID file availability check for UniProt UniPathway took 0.0004947185516357422s
Completeness | Calculation of interlinking completeness for UniProt UniPathway took 0.17315340042114258s
Reputation | Calculation of the PageRank for UniProt UniPathway took 0.021270275115966797s
Interlinking | Calculation of Degree of Connection for UniProt UniPathway took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UniProt UniPathway took 0.0006961822509765625s
Interlinking | Calculation of Clustering coefficient for UniProt UniPathway took 3.0994415283203125e-05s
Believability | Calculation of trust value for UniProt UniPathway took 1.3828277587890625e-05s
INFO | --- Analysis for uniprot-unipathway took 2.063983917236328s
Availability | SPARQL endpoint availability check for UniProtKB took 0.00010132789611816406s
Availability | VoID file availability check for UniProtKB took 0.0004849433898925781s
Completeness | Calculation of interlinking completeness for UniProtKB took 0.1805129051208496s
Reputation | Calculation of the PageRank for UniProtKB took 0.022023439407348633s
Interlinking | Calculation of Degree of Connection for UniProtKB took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for UniProtKB took 0.0007195472717285156s
Interlinking | Calculation of Clustering coefficient for UniProtKB took 5.4836273193359375e-05s
Believability | Calculation of trust value for UniProtKB took 1.33514404296875e-05s
INFO | --- Analysis for uniprotkb took 2.0273072719573975s
Availability | SPARQL endpoint availability check for UniProt UniRef took 8.225440979003906e-05s
Availability | VoID file availability check for UniProt UniRef took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for UniProt UniRef took 0.18504548072814941s
Reputation | Calculation of the PageRank for UniProt UniRef took 0.021176576614379883s
Interlinking | Calculation of Degree of Connection for UniProt UniRef took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UniProt UniRef took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for UniProt UniRef took 3.0994415283203125e-05s
Believability | Calculation of trust value for UniProt UniRef took 1.3113021850585938e-05s
INFO | --- Analysis for uniref took 1.9673926830291748s
Availability | SPARQL endpoint availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 4.124641418457031e-05s
Availability | VoID file availability check for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.1758408546447754s
Reputation | Calculation of the PageRank for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.020506620407104492s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 0.0007202625274658203s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 3.0279159545898438e-05s
Believability | Calculation of trust value for UNISTAT-KIS 2011/2012 in RDF (Key Information Set - UK Universities) took 1.430511474609375e-05s
INFO | --- Analysis for unistat-kis-2011-2012-in-rdf-key-information-set-uk-universities took 2.063620090484619s
Availability | SPARQL endpoint availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.886222839355469e-05s
Availability | VoID file availability check for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.1796557903289795s
Reputation | Calculation of the PageRank for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.02049541473388672s
Interlinking | Calculation of Degree of Connection for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 0.0007119178771972656s
Interlinking | Calculation of Clustering coefficient for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 3.719329833984375e-05s
Believability | Calculation of trust value for UNISTAT-KIS in RDF (Key Information Set - UK Universities) took 1.239776611328125e-05s
INFO | --- Analysis for unistat-kis-in-rdf-key-information-set-uk-universities took 1.941053867340088s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek took 3.886222839355469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek took 0.0004601478576660156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek took 0.17431950569152832s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek took 0.02041316032409668s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek took 1.9629268646240234s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.00045943260192871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.17387175559997559s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.02226996421813965s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ancient_Greek-PROIEL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ancient_Greek-PROIEL took 0.0007450580596923828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ancient_Greek-PROIEL took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ancient_Greek-PROIEL took 1.0967254638671875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ancient-greek-proiel took 1.9860122203826904s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Arabic took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Arabic took 0.0002143383026123047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Arabic took 0.17268991470336914s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Arabic took 0.021300554275512695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Arabic took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Arabic took 0.0007171630859375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Arabic took 5.984306335449219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Arabic took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-arabic took 1.9660804271697998s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Basque took 8.130073547363281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Basque took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Basque took 0.17263245582580566s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Basque took 0.020356178283691406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Basque took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Basque took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Basque took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Basque took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-basque took 2.02009916305542s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Bulgarian took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Bulgarian took 0.0005252361297607422s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Bulgarian took 0.1752769947052002s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Bulgarian took 0.021358013153076172s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Bulgarian took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Bulgarian took 0.0006964206695556641s
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 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-bulgarian took 1.961061716079712s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Catalan took 4.100799560546875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Catalan took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Catalan took 0.18327593803405762s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Catalan took 0.02061176300048828s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Catalan took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Catalan took 0.0007212162017822266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Catalan took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Catalan took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-catalan took 2.0327067375183105s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Chinese took 3.981590270996094e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Chinese took 0.0004830360412597656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Chinese took 0.17197060585021973s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Chinese took 0.020320653915405273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Chinese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Chinese took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Chinese took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Chinese took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-chinese took 1.9709796905517578s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Coptic took 4.7206878662109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Coptic took 0.00048613548278808594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Coptic took 0.17741727828979492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Coptic took 0.021108150482177734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Coptic took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Coptic took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Coptic took 4.1961669921875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Coptic took 1.0013580322265625e-05s
INFO | --- Analysis for universal-dependencies-treebank-coptic took 1.991807222366333s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Croatian took 8.440017700195312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Croatian took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Croatian took 0.19154119491577148s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Croatian took 0.020910978317260742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Croatian took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Croatian took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Croatian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Croatian took 1.2159347534179688e-05s
INFO | --- Analysis for universal-dependencies-treebank-croatian took 2.007960557937622s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech took 9.608268737792969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech took 0.0004596710205078125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech took 0.17467927932739258s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech took 0.020696163177490234s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech took 0.0006976127624511719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech took 1.9689829349517822s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CAC took 4.482269287109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CAC took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CAC took 0.1791238784790039s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CAC took 0.02138233184814453s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CAC took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CAC took 0.0007030963897705078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CAC took 4.220008850097656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CAC took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-czech-cac took 1.9882378578186035s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Czech-CLTT took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Czech-CLTT took 0.0004544258117675781s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Czech-CLTT took 0.18870234489440918s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Czech-CLTT took 0.02169966697692871s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Czech-CLTT took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Czech-CLTT took 0.0010068416595458984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Czech-CLTT took 5.340576171875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Czech-CLTT took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-czech-cltt took 1.9770853519439697s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Danish took 5.626678466796875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Danish took 0.0004971027374267578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Danish took 0.17503690719604492s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Danish took 0.02188897132873535s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Danish took 1.1444091796875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Danish took 0.0007004737854003906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Danish took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Danish took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-danish took 1.9573678970336914s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch took 8.130073547363281e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch took 0.1788923740386963s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch took 0.020631790161132812s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch took 0.0007071495056152344s
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 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch took 1.9708213806152344s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Dutch-LassySmall took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Dutch-LassySmall took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Dutch-LassySmall took 0.1749868392944336s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Dutch-LassySmall took 0.020519256591796875s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Dutch-LassySmall took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Dutch-LassySmall took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Dutch-LassySmall took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Dutch-LassySmall took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-dutch-lassysmall took 1.976933240890503s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English took 0.00011801719665527344s
Availability | VoID file availability check for Universal Dependencies Treebank English took 0.0004520416259765625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English took 0.17749643325805664s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English took 0.022088050842285156s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English took 0.0007121562957763672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-english took 1.9896886348724365s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-ESL took 8.153915405273438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-ESL took 0.0004639625549316406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-ESL took 0.17445731163024902s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-ESL took 0.020467042922973633s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-ESL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-ESL took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-ESL took 4.2438507080078125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-ESL took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-english-esl took 1.9944157600402832s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank English-LinES took 8.869171142578125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank English-LinES took 0.00028133392333984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank English-LinES took 0.18780136108398438s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank English-LinES took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank English-LinES took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank English-LinES took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank English-LinES took 4.291534423828125e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank English-LinES took 8.821487426757812e-06s
INFO | --- Analysis for universal-dependencies-treebank-english-lines took 1.9979286193847656s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Estonian took 8.153915405273438e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Estonian took 0.000507354736328125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Estonian took 0.174943208694458s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Estonian took 0.021412134170532227s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Estonian took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Estonian took 0.0008072853088378906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Estonian took 4.935264587402344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Estonian took 8.106231689453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-estonian took 1.9689891338348389s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish took 4.291534423828125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish took 0.18169164657592773s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish took 0.0205843448638916s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-finnish took 1.9564428329467773s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Finnish-FTB took 0.00014734268188476562s
Availability | VoID file availability check for Universal Dependencies Treebank Finnish-FTB took 0.0011014938354492188s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Finnish-FTB took 0.17324066162109375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Finnish-FTB took 0.02144455909729004s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Finnish-FTB took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Finnish-FTB took 0.0007259845733642578s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Finnish-FTB took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Finnish-FTB took 8.58306884765625e-06s
INFO | --- Analysis for universal-dependencies-treebank-finnish-ftb took 2.010145664215088s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank French took 5.4836273193359375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank French took 0.0004792213439941406s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank French took 0.1835935115814209s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank French took 0.02196526527404785s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank French took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank French took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank French took 4.100799560546875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank French took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-french took 1.9853861331939697s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Galician took 4.1484832763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Galician took 0.00047659873962402344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician took 0.1785869598388672s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician took 0.02106165885925293s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician took 0.0006968975067138672s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician took 2.01173734664917s
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.0002589225769042969s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Galician-TreeGal took 0.1777338981628418s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Galician-TreeGal took 0.023431062698364258s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Galician-TreeGal took 1.1205673217773438e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Galician-TreeGal took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Galician-TreeGal took 4.601478576660156e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Galician-TreeGal took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-galician-treegal took 1.987574577331543s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank German took 8.296966552734375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank German took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank German took 0.1912672519683838s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank German took 0.02042365074157715s
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.0007352828979492188s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank German took 4.506111145019531e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank German took 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-german took 1.9901070594787598s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Gothic took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Gothic took 0.0011684894561767578s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Gothic took 0.1814281940460205s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Gothic took 0.020617008209228516s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Gothic took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Gothic took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Gothic took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Gothic took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-gothic took 1.9795284271240234s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Greek took 3.838539123535156e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Greek took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Greek took 0.182905912399292s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Greek took 0.021924495697021484s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Greek took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Greek took 0.0007159709930419922s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Greek took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Greek took 1.1682510375976562e-05s
INFO | --- Analysis for universal-dependencies-treebank-greek took 1.9992756843566895s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hebrew took 8.273124694824219e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hebrew took 0.0004470348358154297s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hebrew took 0.18210721015930176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hebrew took 0.020394325256347656s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hebrew took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hebrew took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hebrew took 3.886222839355469e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hebrew took 1.430511474609375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hebrew took 2.0079963207244873s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hindi took 8.392333984375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hindi took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hindi took 0.18175244331359863s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hindi took 0.022220373153686523s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hindi took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hindi took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hindi took 4.363059997558594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hindi took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-hindi took 1.9651246070861816s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Hungarian took 8.344650268554688e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Hungarian took 0.0005238056182861328s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Hungarian took 0.19138455390930176s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Hungarian took 0.02105093002319336s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Hungarian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Hungarian took 0.0007147789001464844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Hungarian took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Hungarian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-hungarian took 2.020709276199341s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Indonesian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Indonesian took 0.0007653236389160156s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Indonesian took 0.17674469947814941s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Indonesian took 0.020630836486816406s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Indonesian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Indonesian took 0.0006999969482421875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Indonesian took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Indonesian took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-indonesian took 1.9756968021392822s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Irish took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Irish took 0.0004811286926269531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Irish took 0.1796875s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Irish took 0.020432233810424805s
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.0006968975067138672s
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 1.239776611328125e-05s
INFO | --- Analysis for universal-dependencies-treebank-irish took 1.9959502220153809s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Italian took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Italian took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Italian took 0.18363523483276367s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Italian took 0.020948171615600586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Italian took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Italian took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Italian took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Italian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-italian took 2.077171564102173s
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.0005159378051757812s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese took 0.17530155181884766s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese took 0.02110147476196289s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Japanese took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Japanese took 0.0007045269012451172s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese took 4.673004150390625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese took 2.0084493160247803s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Japanese-KTC took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Japanese-KTC took 0.0002548694610595703s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Japanese-KTC took 0.1729288101196289s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Japanese-KTC took 0.020417451858520508s
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.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Japanese-KTC took 4.482269287109375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Japanese-KTC took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-japanese-ktc took 1.9867758750915527s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Kazakh took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Kazakh took 0.0005245208740234375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Kazakh took 0.17573833465576172s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Kazakh took 0.020754337310791016s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Kazakh took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Kazakh took 0.0007584095001220703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Kazakh took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Kazakh took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-kazakh took 1.9711768627166748s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin took 6.389617919921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin took 0.0004889965057373047s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin took 0.18047785758972168s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin took 0.020728111267089844s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin took 1.430511474609375e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin took 0.0009605884552001953s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin took 5.125999450683594e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin took 1.975198745727539s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-ITTB took 8.082389831542969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-ITTB took 0.0004756450653076172s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-ITTB took 0.1828169822692871s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-ITTB took 0.02065563201904297s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-ITTB took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-ITTB took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-ITTB took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-ITTB took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-ittb took 2.0161516666412354s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latin-PROIEL took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latin-PROIEL took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latin-PROIEL took 0.18334436416625977s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latin-PROIEL took 0.02050948143005371s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latin-PROIEL took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latin-PROIEL took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latin-PROIEL took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latin-PROIEL took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-latin-proiel took 1.9882924556732178s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Latvian took 8.177757263183594e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Latvian took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Latvian took 0.18405818939208984s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Latvian took 0.020472049713134766s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Latvian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Latvian took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Latvian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Latvian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-latvian took 2.0304954051971436s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Norwegian took 4.172325134277344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Norwegian took 0.0005505084991455078s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Norwegian took 0.18695664405822754s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Norwegian took 0.02039790153503418s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Norwegian took 1.049041748046875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Norwegian took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Norwegian took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Norwegian took 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-norwegian took 1.9725608825683594s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Old_Church_Slavonic took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Old_Church_Slavonic took 0.0004444122314453125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Old_Church_Slavonic took 0.18948745727539062s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Old_Church_Slavonic took 0.020871877670288086s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Old_Church_Slavonic took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Old_Church_Slavonic took 0.0009500980377197266s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Old_Church_Slavonic took 4.982948303222656e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Old_Church_Slavonic took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-old-church-slavonic took 2.022824764251709s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Persian took 8.368492126464844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Persian took 0.00048804283142089844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Persian took 0.17541289329528809s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Persian took 0.0204927921295166s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Persian took 1.0967254638671875e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Persian took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Persian took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Persian took 1.2636184692382812e-05s
INFO | --- Analysis for universal-dependencies-treebank-persian took 1.9811294078826904s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Polish took 8.20159912109375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Polish took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Polish took 0.17821955680847168s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Polish took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Polish took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Polish took 0.0007081031799316406s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Polish took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Polish took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-polish took 1.9972786903381348s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese took 4.267692565917969e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese took 0.1875462532043457s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese took 0.02140331268310547s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese took 4.172325134277344e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese took 2.096641778945923s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-Bosque took 8.368492126464844e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-Bosque took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-Bosque took 0.18054842948913574s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-Bosque took 0.020483732223510742s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-Bosque took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-Bosque took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-Bosque took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Portuguese-Bosque took 1.33514404296875e-05s
INFO | --- Analysis for universal-dependencies-treebank-portuguese-bosque took 1.9864356517791748s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Portuguese-BR took 8.463859558105469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Portuguese-BR took 0.0004761219024658203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Portuguese-BR took 0.18485236167907715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Portuguese-BR took 0.022593259811401367s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Portuguese-BR took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Portuguese-BR took 0.0007889270782470703s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Portuguese-BR took 4.6253204345703125e-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.0413897037506104s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Romanian took 8.225440979003906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Romanian took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Romanian took 0.18279814720153809s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Romanian took 0.020435094833374023s
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.0007030963897705078s
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 1.3113021850585938e-05s
INFO | --- Analysis for universal-dependencies-treebank-romanian took 2.0393924713134766s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian took 4.2438507080078125e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian took 0.18428897857666016s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian took 0.020497798919677734s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian took 0.0007300376892089844s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian took 4.553794860839844e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian took 1.9802796840667725s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Russian-SynTagRus took 8.487701416015625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Russian-SynTagRus took 0.0004763603210449219s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Russian-SynTagRus took 0.18148398399353027s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Russian-SynTagRus took 0.020704030990600586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Russian-SynTagRus took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Russian-SynTagRus took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Russian-SynTagRus took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Russian-SynTagRus took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-russian-syntagrus took 2.0157294273376465s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Sanskrit took 9.512901306152344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Sanskrit took 0.0005261898040771484s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Sanskrit took 0.1830904483795166s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Sanskrit took 0.02045607566833496s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Sanskrit took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Sanskrit took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Sanskrit took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Sanskrit took 1.2874603271484375e-05s
INFO | --- Analysis for universal-dependencies-treebank-sanskrit took 2.001404285430908s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovak took 0.00011944770812988281s
Availability | VoID file availability check for Universal Dependencies Treebank Slovak took 0.0002434253692626953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovak took 0.17770004272460938s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovak took 0.02237701416015625s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovak took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovak took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovak took 4.1484832763671875e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovak took 7.867813110351562e-06s
INFO | --- Analysis for universal-dependencies-treebank-slovak took 2.0130770206451416s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian took 9.202957153320312e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian took 0.0004658699035644531s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian took 0.1899862289428711s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian took 0.02283763885498047s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian took 4.0531158447265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian took 1.3828277587890625e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian took 1.974388837814331s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Slovenian-SST took 4.124641418457031e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Slovenian-SST took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Slovenian-SST took 0.1804332733154297s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Slovenian-SST took 0.020748615264892578s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Slovenian-SST took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Slovenian-SST took 0.0008046627044677734s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Slovenian-SST took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Slovenian-SST took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-slovenian-sst took 1.959853172302246s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish took 0.17415261268615723s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish took 0.02054572105407715s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish took 3.933906555175781e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish took 5.0067901611328125e-06s
INFO | --- Analysis for universal-dependencies-treebank-spanish took 1.9763269424438477s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Spanish-AnCora took 8.225440979003906e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Spanish-AnCora took 0.00044035911560058594s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Spanish-AnCora took 0.1783771514892578s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Spanish-AnCora took 0.021456003189086914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Spanish-AnCora took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Spanish-AnCora took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Spanish-AnCora took 4.00543212890625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Spanish-AnCora took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-spanish-ancora took 2.008061647415161s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish took 3.9577484130859375e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish took 0.00020956993103027344s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish took 0.17604827880859375s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish took 0.020276784896850586s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish took 3.9577484130859375e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish took 1.0728836059570312e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish took 1.9906868934631348s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish-LinES took 4.57763671875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish-LinES took 0.0004787445068359375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish-LinES took 0.17541146278381348s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish-LinES took 0.021849393844604492s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish-LinES took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish-LinES took 0.0007073879241943359s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish-LinES took 4.458427429199219e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish-LinES took 7.62939453125e-06s
INFO | --- Analysis for universal-dependencies-treebank-swedish-lines took 2.0057015419006348s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Swedish_Sign_Language took 3.886222839355469e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Swedish_Sign_Language took 0.0004634857177734375s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Swedish_Sign_Language took 0.17520880699157715s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Swedish_Sign_Language took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Swedish_Sign_Language took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Swedish_Sign_Language took 0.0006957054138183594s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Swedish_Sign_Language took 4.029273986816406e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Swedish_Sign_Language took 1.1444091796875e-05s
INFO | --- Analysis for universal-dependencies-treebank-swedish-sign-language took 1.9969639778137207s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Tamil took 7.987022399902344e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Tamil took 0.0004570484161376953s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Tamil took 0.18219399452209473s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Tamil took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Tamil took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Tamil took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Tamil took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Tamil took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-tamil took 2.0363991260528564s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Turkish took 4.220008850097656e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Turkish took 0.0005388259887695312s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Turkish took 0.2050631046295166s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Turkish took 0.020572185516357422s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Turkish took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Turkish took 0.0007281303405761719s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Turkish took 3.981590270996094e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Turkish took 1.4066696166992188e-05s
INFO | --- Analysis for universal-dependencies-treebank-turkish took 2.015634059906006s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Ukrainian took 4.0531158447265625e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Ukrainian took 0.0004565715789794922s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Ukrainian took 0.19197392463684082s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Ukrainian took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Ukrainian took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Ukrainian took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Ukrainian took 3.910064697265625e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Ukrainian took 1.049041748046875e-05s
INFO | --- Analysis for universal-dependencies-treebank-ukrainian took 2.0073602199554443s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Uyghur took 0.0001761913299560547s
Availability | VoID file availability check for Universal Dependencies Treebank Uyghur took 0.0004553794860839844s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Uyghur took 0.17626667022705078s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Uyghur took 0.0204925537109375s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Uyghur took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Uyghur took 0.0007205009460449219s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Uyghur took 4.076957702636719e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Uyghur took 1.0251998901367188e-05s
INFO | --- Analysis for universal-dependencies-treebank-uyghur took 1.9899306297302246s
Availability | SPARQL endpoint availability check for Universal Dependencies Treebank Vietnamese took 4.1961669921875e-05s
Availability | VoID file availability check for Universal Dependencies Treebank Vietnamese took 0.0004885196685791016s
Completeness | Calculation of interlinking completeness for Universal Dependencies Treebank Vietnamese took 0.17677879333496094s
Reputation | Calculation of the PageRank for Universal Dependencies Treebank Vietnamese took 0.020723581314086914s
Interlinking | Calculation of Degree of Connection for Universal Dependencies Treebank Vietnamese took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Universal Dependencies Treebank Vietnamese took 0.0007376670837402344s
Interlinking | Calculation of Clustering coefficient for Universal Dependencies Treebank Vietnamese took 4.124641418457031e-05s
Believability | Calculation of trust value for Universal Dependencies Treebank Vietnamese took 1.3589859008789062e-05s
INFO | --- Analysis for universal-dependencies-treebank-vietnamese took 1.9863784313201904s
Availability | SPARQL endpoint availability check for Universidad de Cuenca - LinkedData took 4.2438507080078125e-05s
Availability | VoID file availability check for Universidad de Cuenca - LinkedData took 0.0004782676696777344s
Completeness | Calculation of interlinking completeness for Universidad de Cuenca - LinkedData took 0.18264079093933105s
Reputation | Calculation of the PageRank for Universidad de Cuenca - LinkedData took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for Universidad de Cuenca - LinkedData took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universidad de Cuenca - LinkedData took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Universidad de Cuenca - LinkedData took 6.4849853515625e-05s
Believability | Calculation of trust value for Universidad de Cuenca - LinkedData took 1.33514404296875e-05s
INFO | --- Analysis for universidad-de-cuenca-linkeddata took 2.025744676589966s
Availability | SPARQL endpoint availability check for Universitat Pompeu Fabra - linked data took 8.416175842285156e-05s
Availability | VoID file availability check for Universitat Pompeu Fabra - linked data took 0.0002491474151611328s
Completeness | Calculation of interlinking completeness for Universitat Pompeu Fabra - linked data took 0.1880474090576172s
Reputation | Calculation of the PageRank for Universitat Pompeu Fabra - linked data took 0.021637678146362305s
Interlinking | Calculation of Degree of Connection for Universitat Pompeu Fabra - linked data took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Universitat Pompeu Fabra - linked data took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Universitat Pompeu Fabra - linked data took 3.814697265625e-05s
Believability | Calculation of trust value for Universitat Pompeu Fabra - linked data took 7.62939453125e-06s
INFO | --- Analysis for universitat-pompeu-fabra-linked-data took 1.990293264389038s
Availability | SPARQL endpoint availability check for University of Bristol took 8.273124694824219e-05s
Availability | VoID file availability check for University of Bristol took 0.00026345252990722656s
Completeness | Calculation of interlinking completeness for University of Bristol took 0.17577672004699707s
Reputation | Calculation of the PageRank for University of Bristol took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for University of Bristol took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for University of Bristol took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for University of Bristol took 3.337860107421875e-05s
Believability | Calculation of trust value for University of Bristol took 7.867813110351562e-06s
INFO | --- Analysis for university-of-bristol took 1.9845259189605713s
Availability | SPARQL endpoint availability check for University of Plymouth Reading Lists took 8.296966552734375e-05s
Availability | VoID file availability check for University of Plymouth Reading Lists took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for University of Plymouth Reading Lists took 0.17536711692810059s
Reputation | Calculation of the PageRank for University of Plymouth Reading Lists took 0.020584583282470703s
Interlinking | Calculation of Degree of Connection for University of Plymouth Reading Lists took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for University of Plymouth Reading Lists took 0.0007157325744628906s
Interlinking | Calculation of Clustering coefficient for University of Plymouth Reading Lists took 5.078315734863281e-05s
Believability | Calculation of trust value for University of Plymouth Reading Lists took 1.1444091796875e-05s
INFO | --- Analysis for university-plymouth-reading-lists took 1.990626335144043s
Availability | SPARQL endpoint availability check for University of Sussex Reading Lists took 4.887580871582031e-05s
Availability | VoID file availability check for University of Sussex Reading Lists took 0.0004940032958984375s
Completeness | Calculation of interlinking completeness for University of Sussex Reading Lists took 0.18180537223815918s
Reputation | Calculation of the PageRank for University of Sussex Reading Lists took 0.020750999450683594s
Interlinking | Calculation of Degree of Connection for University of Sussex Reading Lists took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for University of Sussex Reading Lists took 0.0007071495056152344s
Interlinking | Calculation of Clustering coefficient for University of Sussex Reading Lists took 3.528594970703125e-05s
Believability | Calculation of trust value for University of Sussex Reading Lists took 8.106231689453125e-06s
INFO | --- Analysis for university-sussex-reading-lists took 2.0026092529296875s
Availability | SPARQL endpoint availability check for UNODC - Statistics on criminal justice took 4.172325134277344e-05s
Availability | VoID file availability check for UNODC - Statistics on criminal justice took 0.0006175041198730469s
Completeness | Calculation of interlinking completeness for UNODC - Statistics on criminal justice took 0.18214797973632812s
Reputation | Calculation of the PageRank for UNODC - Statistics on criminal justice took 0.02068781852722168s
Interlinking | Calculation of Degree of Connection for UNODC - Statistics on criminal justice took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for UNODC - Statistics on criminal justice took 0.0009541511535644531s
Interlinking | Calculation of Clustering coefficient for UNODC - Statistics on criminal justice took 8.797645568847656e-05s
Believability | Calculation of trust value for UNODC - Statistics on criminal justice took 1.3113021850585938e-05s
INFO | --- Analysis for unodc took 1.9780771732330322s
Availability | SPARQL endpoint availability check for Super Ontology took 8.20159912109375e-05s
Availability | VoID file availability check for Super Ontology took 0.00048279762268066406s
Completeness | Calculation of interlinking completeness for Super Ontology took 0.18288731575012207s
Reputation | Calculation of the PageRank for Super Ontology took 0.02156376838684082s
Interlinking | Calculation of Degree of Connection for Super Ontology took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Super Ontology took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Super Ontology took 7.915496826171875e-05s
Believability | Calculation of trust value for Super Ontology took 1.33514404296875e-05s
INFO | --- Analysis for upper-ontology took 1.992105484008789s
Availability | SPARQL endpoint availability check for Sup_Ont: An Upper Ontology took 4.1484832763671875e-05s
Availability | VoID file availability check for Sup_Ont: An Upper Ontology took 0.0002560615539550781s
Completeness | Calculation of interlinking completeness for Sup_Ont: An Upper Ontology took 0.18258094787597656s
Reputation | Calculation of the PageRank for Sup_Ont: An Upper Ontology took 0.02031874656677246s
Interlinking | Calculation of Degree of Connection for Sup_Ont: An Upper Ontology took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Sup_Ont: An Upper Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Sup_Ont: An Upper Ontology took 3.2901763916015625e-05s
Believability | Calculation of trust value for Sup_Ont: An Upper Ontology took 1.3113021850585938e-05s
INFO | --- Analysis for Upper_Ontology took 2.009965658187866s
Availability | SPARQL endpoint availability check for Urban Atlas dataset took 8.463859558105469e-05s
Availability | VoID file availability check for Urban Atlas dataset took 0.0005328655242919922s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset took 0.17753243446350098s
Reputation | Calculation of the PageRank for Urban Atlas dataset took 0.020495176315307617s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset took 3.0994415283203125e-05s
Believability | Calculation of trust value for Urban Atlas dataset took 6.198883056640625e-06s
INFO | --- Analysis for Urban_Atlas_ took 1.971708059310913s
Availability | SPARQL endpoint availability check for Urban Atlas dataset @PSNC took 8.153915405273438e-05s
Availability | VoID file availability check for Urban Atlas dataset @PSNC took 0.00045800209045410156s
Completeness | Calculation of interlinking completeness for Urban Atlas dataset @PSNC took 0.21360230445861816s
Reputation | Calculation of the PageRank for Urban Atlas dataset @PSNC took 0.020646095275878906s
Interlinking | Calculation of Degree of Connection for Urban Atlas dataset @PSNC took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Urban Atlas dataset @PSNC took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Urban Atlas dataset @PSNC took 3.361701965332031e-05s
Believability | Calculation of trust value for Urban Atlas dataset @PSNC took 7.867813110351562e-06s
INFO | --- Analysis for Urban_Atlas_Dataset took 2.0644967555999756s
Availability | SPARQL endpoint availability check for URIBurner took 8.153915405273438e-05s
Availability | VoID file availability check for URIBurner took 0.00045871734619140625s
Completeness | Calculation of interlinking completeness for URIBurner took 0.1728191375732422s
Reputation | Calculation of the PageRank for URIBurner took 0.022273540496826172s
Interlinking | Calculation of Degree of Connection for URIBurner took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for URIBurner took 0.000720977783203125s
Interlinking | Calculation of Clustering coefficient for URIBurner took 9.107589721679688e-05s
Believability | Calculation of trust value for URIBurner took 9.775161743164062e-06s
INFO | --- Analysis for uriburner took 2.10575795173645s
Availability | SPARQL endpoint availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 6.771087646484375e-05s
Availability | VoID file availability check for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0002467632293701172s
Completeness | Calculation of interlinking completeness for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.18542742729187012s
Reputation | Calculation of the PageRank for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.020609140396118164s
Interlinking | Calculation of Degree of Connection for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 0.0007178783416748047s
Interlinking | Calculation of Clustering coefficient for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 3.0279159545898438e-05s
Believability | Calculation of trust value for Vocabularios de los Códigos de Derecho de la Ciberseguridad en España took 1.0728836059570312e-05s
INFO | --- Analysis for urn_webprotege_ontology_c0b8701e-374c-4d5a-bc60-970f0cba1976 took 2.039930582046509s
Availability | SPARQL endpoint availability check for Legija Stranaca took 8.392333984375e-05s
Availability | VoID file availability check for Legija Stranaca took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for Legija Stranaca took 0.1821596622467041s
Reputation | Calculation of the PageRank for Legija Stranaca took 0.020476341247558594s
Interlinking | Calculation of Degree of Connection for Legija Stranaca took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Legija Stranaca took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Legija Stranaca took 3.0994415283203125e-05s
Believability | Calculation of trust value for Legija Stranaca took 1.049041748046875e-05s
INFO | --- Analysis for Uros_Legija_Susa took 2.0534489154815674s
Availability | SPARQL endpoint availability check for Legija took 3.981590270996094e-05s
Availability | VoID file availability check for Legija took 0.00034546852111816406s
Completeness | Calculation of interlinking completeness for Legija took 0.17456483840942383s
Reputation | Calculation of the PageRank for Legija took 0.02243947982788086s
Interlinking | Calculation of Degree of Connection for Legija took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Legija took 0.0007047653198242188s
Interlinking | Calculation of Clustering coefficient for Legija took 3.170967102050781e-05s
Believability | Calculation of trust value for Legija took 1.430511474609375e-05s
INFO | --- Analysis for Uros_Susa took 1.968567132949829s
Availability | SPARQL endpoint availability check for US Political Violence took 8.034706115722656e-05s
Availability | VoID file availability check for US Political Violence took 0.000457763671875s
Completeness | Calculation of interlinking completeness for US Political Violence took 0.1761765480041504s
Reputation | Calculation of the PageRank for US Political Violence took 0.02122187614440918s
Interlinking | Calculation of Degree of Connection for US Political Violence took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for US Political Violence took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for US Political Violence took 3.314018249511719e-05s
Believability | Calculation of trust value for US Political Violence took 1.049041748046875e-05s
INFO | --- Analysis for us-political-violence took 2.0067272186279297s
Availability | SPARQL endpoint availability check for USAGE review corpus took 8.034706115722656e-05s
Availability | VoID file availability check for USAGE review corpus took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for USAGE review corpus took 0.17588162422180176s
Reputation | Calculation of the PageRank for USAGE review corpus took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for USAGE review corpus took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for USAGE review corpus took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for USAGE review corpus took 2.956390380859375e-05s
Believability | Calculation of trust value for USAGE review corpus took 1.049041748046875e-05s
INFO | --- Analysis for usage-review-corpus took 1.969193696975708s
Availability | SPARQL endpoint availability check for Universidad Técnica Particular de Loja - Linked Open Data took 8.368492126464844e-05s
Availability | VoID file availability check for Universidad Técnica Particular de Loja - Linked Open Data took 0.00047135353088378906s
Completeness | Calculation of interlinking completeness for Universidad Técnica Particular de Loja - Linked Open Data took 0.18277978897094727s
Reputation | Calculation of the PageRank for Universidad Técnica Particular de Loja - Linked Open Data took 0.0210726261138916s
Interlinking | Calculation of Degree of Connection for Universidad Técnica Particular de Loja - Linked Open Data took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Universidad Técnica Particular de Loja - Linked Open Data took 0.0007166862487792969s
Interlinking | Calculation of Clustering coefficient for Universidad Técnica Particular de Loja - Linked Open Data took 7.224082946777344e-05s
Believability | Calculation of trust value for Universidad Técnica Particular de Loja - Linked Open Data took 1.1444091796875e-05s
INFO | --- Analysis for utpl-lod took 1.9656894207000732s
Availability | SPARQL endpoint availability check for Výkazy zisku a ztrát obcí ČR took 8.320808410644531e-05s
Availability | VoID file availability check for Výkazy zisku a ztrát obcí ČR took 0.00021076202392578125s
Completeness | Calculation of interlinking completeness for Výkazy zisku a ztrát obcí ČR took 0.17964816093444824s
Reputation | Calculation of the PageRank for Výkazy zisku a ztrát obcí ČR took 0.021479129791259766s
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.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Výkazy zisku a ztrát obcí ČR took 3.0994415283203125e-05s
Believability | Calculation of trust value for Výkazy zisku a ztrát obcí ČR took 1.0967254638671875e-05s
INFO | --- Analysis for v-kazy-zisku-a-ztr-t-obc---r took 2.328007936477661s
Availability | SPARQL endpoint availability check for terrorist attack took 8.654594421386719e-05s
Availability | VoID file availability check for terrorist attack took 0.0004534721374511719s
Completeness | Calculation of interlinking completeness for terrorist attack took 0.1727890968322754s
Reputation | Calculation of the PageRank for terrorist attack took 0.020547151565551758s
Interlinking | Calculation of Degree of Connection for terrorist attack took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for terrorist attack took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for terrorist attack took 2.9802322387695312e-05s
Believability | Calculation of trust value for terrorist attack took 1.1205673217773438e-05s
INFO | --- Analysis for varsha took 1.9599683284759521s
Availability | SPARQL endpoint availability check for VA took 8.296966552734375e-05s
Availability | VoID file availability check for VA took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for VA took 0.16931939125061035s
Reputation | Calculation of the PageRank for VA took 0.020556926727294922s
Interlinking | Calculation of Degree of Connection for VA took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for VA took 0.0006988048553466797s
Interlinking | Calculation of Clustering coefficient for VA took 2.9802322387695312e-05s
Believability | Calculation of trust value for VA took 1.049041748046875e-05s
INFO | --- Analysis for Vehicule_Autonome took 1.9733588695526123s
Availability | SPARQL endpoint availability check for Velez (1744) Index Totius Artis in LiLa took 8.296966552734375e-05s
Availability | VoID file availability check for Velez (1744) Index Totius Artis in LiLa took 0.0004608631134033203s
Completeness | Calculation of interlinking completeness for Velez (1744) Index Totius Artis in LiLa took 0.1723189353942871s
Reputation | Calculation of the PageRank for Velez (1744) Index Totius Artis in LiLa took 0.02046489715576172s
Interlinking | Calculation of Degree of Connection for Velez (1744) Index Totius Artis in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Velez (1744) Index Totius Artis in LiLa took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Velez (1744) Index Totius Artis in LiLa took 3.814697265625e-05s
Believability | Calculation of trust value for Velez (1744) Index Totius Artis in LiLa took 9.5367431640625e-06s
INFO | --- Analysis for VelezIndexTotiusArtis took 1.9641916751861572s
Availability | SPARQL endpoint availability check for Verrijkt Koninkrijk took 3.981590270996094e-05s
Availability | VoID file availability check for Verrijkt Koninkrijk took 0.00022077560424804688s
Completeness | Calculation of interlinking completeness for Verrijkt Koninkrijk took 0.17577886581420898s
Reputation | Calculation of the PageRank for Verrijkt Koninkrijk took 0.020780086517333984s
Interlinking | Calculation of Degree of Connection for Verrijkt Koninkrijk took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Verrijkt Koninkrijk took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Verrijkt Koninkrijk took 0.00010561943054199219s
Believability | Calculation of trust value for Verrijkt Koninkrijk took 1.1682510375976562e-05s
INFO | --- Analysis for verrijktkoninkrijk took 2.0168161392211914s
Availability | SPARQL endpoint availability check for VIAF: The Virtual International Authority File took 8.463859558105469e-05s
Availability | VoID file availability check for VIAF: The Virtual International Authority File took 0.00045037269592285156s
Completeness | Calculation of interlinking completeness for VIAF: The Virtual International Authority File took 0.18700623512268066s
Reputation | Calculation of the PageRank for VIAF: The Virtual International Authority File took 0.022279024124145508s
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.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for VIAF: The Virtual International Authority File took 0.0001647472381591797s
Believability | Calculation of trust value for VIAF: The Virtual International Authority File took 1.33514404296875e-05s
INFO | --- Analysis for viaf took 2.365459680557251s
Availability | SPARQL endpoint availability check for Vías Públicas de Zaragoza (Localización) took 4.291534423828125e-05s
Availability | VoID file availability check for Vías Públicas de Zaragoza (Localización) took 0.00047278404235839844s
Completeness | Calculation of interlinking completeness for Vías Públicas de Zaragoza (Localización) took 0.17330312728881836s
Reputation | Calculation of the PageRank for Vías Públicas de Zaragoza (Localización) took 0.02219700813293457s
Interlinking | Calculation of Degree of Connection for Vías Públicas de Zaragoza (Localización) took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Vías Públicas de Zaragoza (Localización) took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for Vías Públicas de Zaragoza (Localización) took 3.457069396972656e-05s
Believability | Calculation of trust value for Vías Públicas de Zaragoza (Localización) took 1.1682510375976562e-05s
INFO | --- Analysis for vias-publicas-zaragoza took 2.0193002223968506s
Availability | SPARQL endpoint availability check for Vihar Exports took 4.124641418457031e-05s
Availability | VoID file availability check for Vihar Exports took 0.0004582405090332031s
Completeness | Calculation of interlinking completeness for Vihar Exports took 0.1844160556793213s
Reputation | Calculation of the PageRank for Vihar Exports took 0.020762920379638672s
Interlinking | Calculation of Degree of Connection for Vihar Exports took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Vihar Exports took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Vihar Exports took 3.218650817871094e-05s
Believability | Calculation of trust value for Vihar Exports took 1.049041748046875e-05s
INFO | --- Analysis for Vihar_Exports took 2.029742956161499s
Availability | SPARQL endpoint availability check for vimeo.videoobject took 5.626678466796875e-05s
Availability | VoID file availability check for vimeo.videoobject took 0.00045228004455566406s
Completeness | Calculation of interlinking completeness for vimeo.videoobject took 0.18465185165405273s
Reputation | Calculation of the PageRank for vimeo.videoobject took 0.02058887481689453s
Interlinking | Calculation of Degree of Connection for vimeo.videoobject took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vimeo.videoobject took 0.0007083415985107422s
Interlinking | Calculation of Clustering coefficient for vimeo.videoobject took 3.0517578125e-05s
Believability | Calculation of trust value for vimeo.videoobject took 1.1682510375976562e-05s
INFO | --- Analysis for vimeo_videoobject took 1.9923949241638184s
Availability | SPARQL endpoint availability check for VIVO took 3.981590270996094e-05s
Availability | VoID file availability check for VIVO took 0.0004646778106689453s
Completeness | Calculation of interlinking completeness for VIVO took 0.18839693069458008s
Reputation | Calculation of the PageRank for VIVO took 0.020839452743530273s
Interlinking | Calculation of Degree of Connection for VIVO took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO took 0.0007319450378417969s
Interlinking | Calculation of Clustering coefficient for VIVO took 7.009506225585938e-05s
Believability | Calculation of trust value for VIVO took 1.2874603271484375e-05s
INFO | --- Analysis for vivo took 2.084158420562744s
Availability | SPARQL endpoint availability check for VIVO Cornell took 4.00543212890625e-05s
Availability | VoID file availability check for VIVO Cornell took 0.00022721290588378906s
Completeness | Calculation of interlinking completeness for VIVO Cornell took 0.17604279518127441s
Reputation | Calculation of the PageRank for VIVO Cornell took 0.020461559295654297s
Interlinking | Calculation of Degree of Connection for VIVO Cornell took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for VIVO Cornell took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for VIVO Cornell took 8.058547973632812e-05s
Believability | Calculation of trust value for VIVO Cornell took 5.4836273193359375e-06s
INFO | --- Analysis for vivo-cornell-university took 1.9728648662567139s
Availability | SPARQL endpoint availability check for VIVO CU-Boulder took 7.915496826171875e-05s
Availability | VoID file availability check for VIVO CU-Boulder took 0.0004317760467529297s
Completeness | Calculation of interlinking completeness for VIVO CU-Boulder took 0.17928743362426758s
Reputation | Calculation of the PageRank for VIVO CU-Boulder took 0.020436525344848633s
Interlinking | Calculation of Degree of Connection for VIVO CU-Boulder took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for VIVO CU-Boulder took 0.0007011890411376953s
Interlinking | Calculation of Clustering coefficient for VIVO CU-Boulder took 2.9325485229492188e-05s
Believability | Calculation of trust value for VIVO CU-Boulder took 5.0067901611328125e-06s
INFO | --- Analysis for vivo-cu-boulder took 1.9722356796264648s
Availability | SPARQL endpoint availability check for VIVO Indiana took 6.0558319091796875e-05s
Availability | VoID file availability check for VIVO Indiana took 0.00020694732666015625s
Completeness | Calculation of interlinking completeness for VIVO Indiana took 0.18107223510742188s
Reputation | Calculation of the PageRank for VIVO Indiana took 0.02087545394897461s
Interlinking | Calculation of Degree of Connection for VIVO Indiana took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for VIVO Indiana took 0.0007076263427734375s
Interlinking | Calculation of Clustering coefficient for VIVO Indiana took 8.535385131835938e-05s
Believability | Calculation of trust value for VIVO Indiana took 1.0728836059570312e-05s
INFO | --- Analysis for vivo-indiana-university took 1.9753408432006836s
Availability | SPARQL endpoint availability check for VIVO Ponce took 3.9577484130859375e-05s
Availability | VoID file availability check for VIVO Ponce took 0.000457763671875s
Completeness | Calculation of interlinking completeness for VIVO Ponce took 0.17914819717407227s
Reputation | Calculation of the PageRank for VIVO Ponce took 0.020412921905517578s
Interlinking | Calculation of Degree of Connection for VIVO Ponce took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for VIVO Ponce took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for VIVO Ponce took 3.314018249511719e-05s
Believability | Calculation of trust value for VIVO Ponce took 1.2159347534179688e-05s
INFO | --- Analysis for vivo-ponce took 2.005283832550049s
Availability | SPARQL endpoint availability check for VIVO Scripps Research Institute took 0.00010848045349121094s
Availability | VoID file availability check for VIVO Scripps Research Institute took 0.0004703998565673828s
Completeness | Calculation of interlinking completeness for VIVO Scripps Research Institute took 0.18136906623840332s
Reputation | Calculation of the PageRank for VIVO Scripps Research Institute took 0.020685195922851562s
Interlinking | Calculation of Degree of Connection for VIVO Scripps Research Institute took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO Scripps Research Institute took 0.0007498264312744141s
Interlinking | Calculation of Clustering coefficient for VIVO Scripps Research Institute took 3.7670135498046875e-05s
Believability | Calculation of trust value for VIVO Scripps Research Institute took 1.0251998901367188e-05s
INFO | --- Analysis for vivo-scripps-research-institute took 1.9709672927856445s
Availability | SPARQL endpoint availability check for VIVO University of Florida took 8.0108642578125e-05s
Availability | VoID file availability check for VIVO University of Florida took 0.0004413127899169922s
Completeness | Calculation of interlinking completeness for VIVO University of Florida took 0.18015313148498535s
Reputation | Calculation of the PageRank for VIVO University of Florida took 0.020349502563476562s
Interlinking | Calculation of Degree of Connection for VIVO University of Florida took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for VIVO University of Florida took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for VIVO University of Florida took 8.916854858398438e-05s
Believability | Calculation of trust value for VIVO University of Florida took 1.1444091796875e-05s
INFO | --- Analysis for vivo-university-of-florida took 1.9991428852081299s
Availability | SPARQL endpoint availability check for VIVO Weill Cornell Medical College took 3.910064697265625e-05s
Availability | VoID file availability check for VIVO Weill Cornell Medical College took 0.0004611015319824219s
Completeness | Calculation of interlinking completeness for VIVO Weill Cornell Medical College took 0.1839001178741455s
Reputation | Calculation of the PageRank for VIVO Weill Cornell Medical College took 0.022579431533813477s
Interlinking | Calculation of Degree of Connection for VIVO Weill Cornell Medical College took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for VIVO Weill Cornell Medical College took 0.0007069110870361328s
Interlinking | Calculation of Clustering coefficient for VIVO Weill Cornell Medical College took 3.600120544433594e-05s
Believability | Calculation of trust value for VIVO Weill Cornell Medical College took 1.0728836059570312e-05s
INFO | --- Analysis for vivo-weill-cornell-medical-college took 2.0111773014068604s
Availability | SPARQL endpoint availability check for VIVO WUSTL took 3.981590270996094e-05s
Availability | VoID file availability check for VIVO WUSTL took 0.0004839897155761719s
Completeness | Calculation of interlinking completeness for VIVO WUSTL took 0.17438387870788574s
Reputation | Calculation of the PageRank for VIVO WUSTL took 0.020442962646484375s
Interlinking | Calculation of Degree of Connection for VIVO WUSTL took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for VIVO WUSTL took 0.0007026195526123047s
Interlinking | Calculation of Clustering coefficient for VIVO WUSTL took 3.695487976074219e-05s
Believability | Calculation of trust value for VIVO WUSTL took 1.049041748046875e-05s
INFO | --- Analysis for vivo-wustl took 1.9941363334655762s
Availability | SPARQL endpoint availability check for vivo2doi took 4.4345855712890625e-05s
Availability | VoID file availability check for vivo2doi took 0.0005066394805908203s
Completeness | Calculation of interlinking completeness for vivo2doi took 0.18374180793762207s
Reputation | Calculation of the PageRank for vivo2doi took 0.02258443832397461s
Interlinking | Calculation of Degree of Connection for vivo2doi took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for vivo2doi took 0.0007460117340087891s
Interlinking | Calculation of Clustering coefficient for vivo2doi took 4.2438507080078125e-05s
Believability | Calculation of trust value for vivo2doi took 1.3113021850585938e-05s
INFO | --- Analysis for vivo2doi took 2.0495991706848145s
Availability | SPARQL endpoint availability check for WordNet 3.0 (VU Amsterdam) took 8.392333984375e-05s
Availability | VoID file availability check for WordNet 3.0 (VU Amsterdam) took 0.0005297660827636719s
Completeness | Calculation of interlinking completeness for WordNet 3.0 (VU Amsterdam) took 0.18185210227966309s
Reputation | Calculation of the PageRank for WordNet 3.0 (VU Amsterdam) took 0.020549774169921875s
Interlinking | Calculation of Degree of Connection for WordNet 3.0 (VU Amsterdam) took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WordNet 3.0 (VU Amsterdam) took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for WordNet 3.0 (VU Amsterdam) took 6.604194641113281e-05s
Believability | Calculation of trust value for WordNet 3.0 (VU Amsterdam) took 1.2159347534179688e-05s
INFO | --- Analysis for vu-wordnet took 1.986811876296997s
Availability | SPARQL endpoint availability check for vulnerapedia took 8.535385131835938e-05s
Availability | VoID file availability check for vulnerapedia took 0.0004949569702148438s
Completeness | Calculation of interlinking completeness for vulnerapedia took 0.17802000045776367s
Reputation | Calculation of the PageRank for vulnerapedia took 0.02031850814819336s
Interlinking | Calculation of Degree of Connection for vulnerapedia took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for vulnerapedia took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for vulnerapedia took 6.29425048828125e-05s
Believability | Calculation of trust value for vulnerapedia took 1.3113021850585938e-05s
INFO | --- Analysis for vulnerapedia took 1.956296682357788s
Availability | SPARQL endpoint availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 4.076957702636719e-05s
Availability | VoID file availability check for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0004937648773193359s
Completeness | Calculation of interlinking completeness for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.18132281303405762s
Reputation | Calculation of the PageRank for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.02018570899963379s
Interlinking | Calculation of Degree of Connection for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1682510375976562e-05s
Interlinking | Calculation of Centrality for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.1682510375976562e-05s
Believability | Calculation of trust value for  VVASIAK - Sklepy Internetowe, Strony WWW i Wideo dla Firm took 1.2636184692382812e-05s
INFO | --- Analysis for VVASIAK took 1.9693493843078613s
Availability | SPARQL endpoint availability check for Statybu imone - Vyvasta took 8.535385131835938e-05s
Availability | VoID file availability check for Statybu imone - Vyvasta took 0.00047588348388671875s
Completeness | Calculation of interlinking completeness for Statybu imone - Vyvasta took 0.17960095405578613s
Reputation | Calculation of the PageRank for Statybu imone - Vyvasta took 0.020191431045532227s
Interlinking | Calculation of Degree of Connection for Statybu imone - Vyvasta took 1.0013580322265625e-05s
Interlinking | Calculation of Centrality for Statybu imone - Vyvasta took 0.0008401870727539062s
Interlinking | Calculation of Clustering coefficient for Statybu imone - Vyvasta took 3.0994415283203125e-05s
Believability | Calculation of trust value for Statybu imone - Vyvasta took 1.239776611328125e-05s
INFO | --- Analysis for Vyvasta took 1.989368200302124s
Availability | SPARQL endpoint availability check for W3C took 0.00011301040649414062s
Availability | VoID file availability check for W3C took 0.0004999637603759766s
Completeness | Calculation of interlinking completeness for W3C took 0.17180633544921875s
Reputation | Calculation of the PageRank for W3C took 0.020247936248779297s
Interlinking | Calculation of Degree of Connection for W3C took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for W3C took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for W3C took 0.0001316070556640625s
Believability | Calculation of trust value for W3C took 1.239776611328125e-05s
INFO | --- Analysis for w3c took 1.9864909648895264s
Availability | SPARQL endpoint availability check for W3C Provenance Incubator Group Vocabulary Mappings took 4.076957702636719e-05s
Availability | VoID file availability check for W3C Provenance Incubator Group Vocabulary Mappings took 0.0005395412445068359s
Completeness | Calculation of interlinking completeness for W3C Provenance Incubator Group Vocabulary Mappings took 0.17558884620666504s
Reputation | Calculation of the PageRank for W3C Provenance Incubator Group Vocabulary Mappings took 0.021740436553955078s
Interlinking | Calculation of Degree of Connection for W3C Provenance Incubator Group Vocabulary Mappings took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for W3C Provenance Incubator Group Vocabulary Mappings took 0.0009026527404785156s
Interlinking | Calculation of Clustering coefficient for W3C Provenance Incubator Group Vocabulary Mappings took 3.2901763916015625e-05s
Believability | Calculation of trust value for W3C Provenance Incubator Group Vocabulary Mappings took 1.2636184692382812e-05s
INFO | --- Analysis for w3c-provenance-incubator-group-vocabulary-mappings took 2.027688980102539s
Availability | SPARQL endpoint availability check for WordNet 2.0 (W3C) took 8.225440979003906e-05s
Availability | VoID file availability check for WordNet 2.0 (W3C) took 0.0005018711090087891s
Completeness | Calculation of interlinking completeness for WordNet 2.0 (W3C) took 0.17391586303710938s
Reputation | Calculation of the PageRank for WordNet 2.0 (W3C) took 0.02021622657775879s
Interlinking | Calculation of Degree of Connection for WordNet 2.0 (W3C) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for WordNet 2.0 (W3C) took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for WordNet 2.0 (W3C) took 0.00010800361633300781s
Believability | Calculation of trust value for WordNet 2.0 (W3C) took 1.2636184692382812e-05s
INFO | --- Analysis for w3c-wordnet took 1.976473331451416s
Availability | SPARQL endpoint availability check for WarSampo took 0.33779335021972656s
Availability | VoID file availability check for WarSampo took 0.0004999637603759766s
Extra | Recovery of all triples for WarSampo took 25.390429973602295s
Performance | Total latancy measurement for WarSampo took 0.8324637413024902s
Amount of data | Number of triples check for WarSampo took 19.446725368499756s
Interoperability | New terms check for WarSampo took 3.8449761867523193s
Versatility | Languages check for WarSampo took 51.66590929031372s
Interpretability | Number of blank nodes check for WarSampo took 18.155455350875854s
Security | Check HTTPS for WarSampo took 0.4124186038970947s
Interpretability | RDF structures check for WarSampo took 0.1944420337677002s
Versatility | Serialization formats check for WarSampo took 0.1963350772857666s
Availability | RDF dump link check for WarSampo took 0.80246901512146s
License | MR license check for WarSampo took 0.1986997127532959s
License | HR license check for WarSampo took 43.57495713233948s
Amount of data | Number of property check for WarSampo took 0.20907115936279297s
Understandability | Number of label check for WarSampo took 9.075629472732544s
Understandability | URI regex check for WarSampo took 0.3588521480560303s
Understandability | Vocabs check for WarSampo took 0.16463446617126465s
Verifiability | Authors check for WarSampo took 0.19551897048950195s
Verifiability | Publishers check for WarSampo took 0.19837474822998047s
Performance | Throughput check for WarSampo took 11.15553331375122s
Amount of data | Check the number of entities for WarSampo took 15.002552509307861s
Verifiability | Contribs. check for WarSampo took 0.20726943016052246s
Interlinking | sameAs chians check for WarSampo took 0.20322227478027344s
Interlinking | skos check for WarSampo took 0.2161250114440918s
Interlinking | skos check for WarSampo took 0.16063427925109863s
Timeliness | dataset update frequency check for WarSampo took 0.17475008964538574s
Currency | Creation date check for WarSampo took 0.37238240242004395s
Currency | Modification date check for WarSampo took 0.3771963119506836s
Rep.Conc. | URIs length for WarSampo took 48.16090130805969s
Interoperability | New vocabularies check for WarSampo took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for WarSampo took 0.20431900024414062s
Accuracy | Check Functional Property for WarSampo took 0.19860053062438965s
Accuracy | Check Inverse Functional Property for WarSampo took 0.17416810989379883s
Accuracy | Check Empty annotation labels for WarSampo took 11.21737027168274s
Accuracy | Check White space in annotation for WarSampo took 2.186044692993164s
Accuracy | Check Datatype consistency for WarSampo took 5.2791101932525635s
Consistency | Disjoint class check for WarSampo took 0.2040410041809082s
Consistency | Check Misplaced properties for WarSampo took 19.6752290725708s
Consistency | Check Ontology hijacking for WarSampo took 18.83259606361389s
Consistency | Check Invalid usage of undefined classes for WarSampo took 1.3739235401153564s
Consistency | Check Invalid usage of undefined properties for WarSampo took 1.6033542156219482s
Conciseness | Check Extensional conciseness for WarSampo took 2.8084535598754883s
Conciseness | Check Intensional conciseness for WarSampo took 0.2868068218231201s
Security | Sign check for WarSampo took 0.16506195068359375s
Availability | Check URIs Dereferenciability for WarSampo took 2.6594884395599365s
Completeness | Calculation of interlinking completeness for WarSampo took 0.4043309688568115s
Reputation | Calculation of the PageRank for WarSampo took 0.021023035049438477s
Interlinking | Calculation of Degree of Connection for WarSampo took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WarSampo took 0.0006923675537109375s
Interlinking | Calculation of Clustering coefficient for WarSampo took 9.250640869140625e-05s
Interoperability | Check the re-using of existing vocabs for WarSampo took 2.1457672119140625e-06s
Believability | Calculation of trust value for WarSampo took 1.0967254638671875e-05s
INFO | --- Analysis for warsampo took 962.1146919727325s
Availability | SPARQL endpoint availability check for WASABI RDF Knowledge Graph took 20.481884479522705s
Availability | VoID file availability check for WASABI RDF Knowledge Graph took 0.0005209445953369141s
Completeness | Calculation of interlinking completeness for WASABI RDF Knowledge Graph took 0.18669867515563965s
Reputation | Calculation of the PageRank for WASABI RDF Knowledge Graph took 0.020299434661865234s
Interlinking | Calculation of Degree of Connection for WASABI RDF Knowledge Graph took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WASABI RDF Knowledge Graph took 0.0007183551788330078s
Interlinking | Calculation of Clustering coefficient for WASABI RDF Knowledge Graph took 7.390975952148438e-05s
Believability | Calculation of trust value for WASABI RDF Knowledge Graph took 1.3589859008789062e-05s
INFO | --- Analysis for wasabi took 52.53513026237488s
Availability | SPARQL endpoint availability check for FAO water areas classification as linked data @PSNC took 8.225440979003906e-05s
Availability | VoID file availability check for FAO water areas classification as linked data @PSNC took 0.00046324729919433594s
Completeness | Calculation of interlinking completeness for FAO water areas classification as linked data @PSNC took 0.186784029006958s
Reputation | Calculation of the PageRank for FAO water areas classification as linked data @PSNC took 0.020211458206176758s
Interlinking | Calculation of Degree of Connection for FAO water areas classification as linked data @PSNC took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for FAO water areas classification as linked data @PSNC took 0.0007128715515136719s
Interlinking | Calculation of Clustering coefficient for FAO water areas classification as linked data @PSNC took 2.9325485229492188e-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 2.0101921558380127s
Availability | SPARQL endpoint availability check for Water buffer dataset from Czech Republic @PSNC took 8.440017700195312e-05s
Availability | VoID file availability check for Water buffer dataset from Czech Republic @PSNC took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for Water buffer dataset from Czech Republic @PSNC took 0.2507796287536621s
Reputation | Calculation of the PageRank for Water buffer dataset from Czech Republic @PSNC took 0.02038121223449707s
Interlinking | Calculation of Degree of Connection for Water buffer dataset from Czech Republic @PSNC took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Water buffer dataset from Czech Republic @PSNC took 0.0007016658782958984s
Interlinking | Calculation of Clustering coefficient for Water buffer dataset from Czech Republic @PSNC took 2.8371810913085938e-05s
Believability | Calculation of trust value for Water buffer dataset from Czech Republic @PSNC took 1.2636184692382812e-05s
INFO | --- Analysis for Water_Buffer took 2.0608022212982178s
Availability | SPARQL endpoint availability check for WebIsALOD took 8.702278137207031e-05s
Availability | VoID file availability check for WebIsALOD took 0.0002377033233642578s
Completeness | Calculation of interlinking completeness for WebIsALOD took 0.1813068389892578s
Reputation | Calculation of the PageRank for WebIsALOD took 0.02020740509033203s
Interlinking | Calculation of Degree of Connection for WebIsALOD took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WebIsALOD took 0.0006990432739257812s
Interlinking | Calculation of Clustering coefficient for WebIsALOD took 6.866455078125e-05s
Believability | Calculation of trust value for WebIsALOD took 1.2636184692382812e-05s
INFO | --- Analysis for webisalod took 1.9635732173919678s
Availability | SPARQL endpoint availability check for webnmasunotraveler took 4.100799560546875e-05s
Availability | VoID file availability check for webnmasunotraveler took 0.00048732757568359375s
Completeness | Calculation of interlinking completeness for webnmasunotraveler took 0.18007540702819824s
Reputation | Calculation of the PageRank for webnmasunotraveler took 0.02024555206298828s
Interlinking | Calculation of Degree of Connection for webnmasunotraveler took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for webnmasunotraveler took 0.0007598400115966797s
Interlinking | Calculation of Clustering coefficient for webnmasunotraveler took 3.6716461181640625e-05s
Believability | Calculation of trust value for webnmasunotraveler took 1.3828277587890625e-05s
INFO | --- Analysis for webnmasunotraveler took 1.997826099395752s
Availability | SPARQL endpoint availability check for Whisky Circle took 8.344650268554688e-05s
Availability | VoID file availability check for Whisky Circle took 0.0004737377166748047s
Completeness | Calculation of interlinking completeness for Whisky Circle took 0.36605048179626465s
Reputation | Calculation of the PageRank for Whisky Circle took 0.02090287208557129s
Interlinking | Calculation of Degree of Connection for Whisky Circle took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for Whisky Circle took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Whisky Circle took 0.00010204315185546875s
Believability | Calculation of trust value for Whisky Circle took 8.58306884765625e-06s
INFO | --- Analysis for whisky-circle-info took 2.1712300777435303s
Availability | SPARQL endpoint availability check for Corona Virus Infected Cases Ontology took 8.58306884765625e-05s
Availability | VoID file availability check for Corona Virus Infected Cases Ontology took 0.0002677440643310547s
Completeness | Calculation of interlinking completeness for Corona Virus Infected Cases Ontology took 0.17635798454284668s
Reputation | Calculation of the PageRank for Corona Virus Infected Cases Ontology took 0.02089095115661621s
Interlinking | Calculation of Degree of Connection for Corona Virus Infected Cases Ontology took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Corona Virus Infected Cases Ontology took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Corona Virus Infected Cases Ontology took 3.814697265625e-05s
Believability | Calculation of trust value for Corona Virus Infected Cases Ontology took 1.3828277587890625e-05s
INFO | --- Analysis for WHOnto took 1.9566495418548584s
Availability | SPARQL endpoint availability check for COvid-19 statistics Ontology took 8.296966552734375e-05s
Availability | VoID file availability check for COvid-19 statistics Ontology took 0.0004410743713378906s
Completeness | Calculation of interlinking completeness for COvid-19 statistics Ontology took 0.17407488822937012s
Reputation | Calculation of the PageRank for COvid-19 statistics Ontology took 0.02157759666442871s
Interlinking | Calculation of Degree of Connection for COvid-19 statistics Ontology took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for COvid-19 statistics Ontology took 0.000732421875s
Interlinking | Calculation of Clustering coefficient for COvid-19 statistics Ontology took 3.24249267578125e-05s
Believability | Calculation of trust value for COvid-19 statistics Ontology took 1.33514404296875e-05s
INFO | --- Analysis for whonto took 1.9602441787719727s
Availability | SPARQL endpoint availability check for Wikidata took 8.416175842285156e-05s
Availability | VoID file availability check for Wikidata took 0.00045752525329589844s
Completeness | Calculation of interlinking completeness for Wikidata took 0.1726703643798828s
Reputation | Calculation of the PageRank for Wikidata took 0.02017378807067871s
Interlinking | Calculation of Degree of Connection for Wikidata took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Wikidata took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Wikidata took 0.00028514862060546875s
Believability | Calculation of trust value for Wikidata took 1.2636184692382812e-05s
INFO | --- Analysis for wikidata took 1.962907075881958s
Availability | SPARQL endpoint availability check for Wikilinks RDF/NIF took 8.535385131835938e-05s
Availability | VoID file availability check for Wikilinks RDF/NIF took 0.00045108795166015625s
Completeness | Calculation of interlinking completeness for Wikilinks RDF/NIF took 0.1750643253326416s
Reputation | Calculation of the PageRank for Wikilinks RDF/NIF took 0.02037787437438965s
Interlinking | Calculation of Degree of Connection for Wikilinks RDF/NIF took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for Wikilinks RDF/NIF took 0.0007033348083496094s
Interlinking | Calculation of Clustering coefficient for Wikilinks RDF/NIF took 6.532669067382812e-05s
Believability | Calculation of trust value for Wikilinks RDF/NIF took 1.1920928955078125e-05s
INFO | --- Analysis for wikilinks-rdf-nif took 1.9752323627471924s
Availability | SPARQL endpoint availability check for WikiPathways took 9.5367431640625e-05s
Availability | VoID file availability check for WikiPathways took 0.0004439353942871094s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.1726381778717041s
Reputation | Calculation of the PageRank for WikiPathways took 0.02012324333190918s
Interlinking | Calculation of Degree of Connection for WikiPathways took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.7894973754882812e-05s
Believability | Calculation of trust value for WikiPathways took 5.7220458984375e-06s
INFO | --- Analysis for wikipathways took 2.0392279624938965s
Availability | SPARQL endpoint availability check for WikiWord Thesaurus Data took 7.43865966796875e-05s
Availability | VoID file availability check for WikiWord Thesaurus Data took 0.0004932880401611328s
Completeness | Calculation of interlinking completeness for WikiWord Thesaurus Data took 0.18771958351135254s
Reputation | Calculation of the PageRank for WikiWord Thesaurus Data took 0.02033829689025879s
Interlinking | Calculation of Degree of Connection for WikiWord Thesaurus Data took 9.059906005859375e-06s
Interlinking | Calculation of Centrality for WikiWord Thesaurus Data took 0.0006947517395019531s
Interlinking | Calculation of Clustering coefficient for WikiWord Thesaurus Data took 3.0040740966796875e-05s
Believability | Calculation of trust value for WikiWord Thesaurus Data took 1.33514404296875e-05s
INFO | --- Analysis for wikiword_thesaurus took 2.26642107963562s
Availability | SPARQL endpoint availability check for wiktionary.dbpedia.org took 8.368492126464844e-05s
Availability | VoID file availability check for wiktionary.dbpedia.org took 0.00046253204345703125s
Completeness | Calculation of interlinking completeness for wiktionary.dbpedia.org took 0.18070030212402344s
Reputation | Calculation of the PageRank for wiktionary.dbpedia.org took 0.020311355590820312s
Interlinking | Calculation of Degree of Connection for wiktionary.dbpedia.org took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for wiktionary.dbpedia.org took 0.0007240772247314453s
Interlinking | Calculation of Clustering coefficient for wiktionary.dbpedia.org took 8.058547973632812e-05s
Believability | Calculation of trust value for wiktionary.dbpedia.org took 1.2874603271484375e-05s
INFO | --- Analysis for wiktionary-dbpedia-org took 2.0038859844207764s
Availability | SPARQL endpoint availability check for Wings workflow provenance dataset took 8.296966552734375e-05s
Availability | VoID file availability check for Wings workflow provenance dataset took 0.0004856586456298828s
Completeness | Calculation of interlinking completeness for Wings workflow provenance dataset took 0.17222380638122559s
Reputation | Calculation of the PageRank for Wings workflow provenance dataset took 0.02030634880065918s
Interlinking | Calculation of Degree of Connection for Wings workflow provenance dataset took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Wings workflow provenance dataset took 0.0007205009460449219s
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 1.2636184692382812e-05s
INFO | --- Analysis for wings-workflow-provenance-dataset took 1.9851324558258057s
Availability | SPARQL endpoint availability check for The World Literature Knowledge Graph took 1.3004980087280273s
Availability | VoID file availability check for The World Literature Knowledge Graph took 0.0004925727844238281s
Completeness | Calculation of interlinking completeness for The World Literature Knowledge Graph took 0.17705678939819336s
Reputation | Calculation of the PageRank for The World Literature Knowledge Graph took 0.020256996154785156s
Interlinking | Calculation of Degree of Connection for The World Literature Knowledge Graph took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for The World Literature Knowledge Graph took 0.0006992816925048828s
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 1.0728836059570312e-05s
INFO | --- Analysis for wl-kg took 3.592428207397461s
Availability | SPARQL endpoint availability check for Wordnet-Wikipedia/DBpedia instance mapping took 4.3392181396484375e-05s
Availability | VoID file availability check for Wordnet-Wikipedia/DBpedia instance mapping took 0.0005364418029785156s
Completeness | Calculation of interlinking completeness for Wordnet-Wikipedia/DBpedia instance mapping took 0.18149638175964355s
Reputation | Calculation of the PageRank for Wordnet-Wikipedia/DBpedia instance mapping took 0.021521568298339844s
Interlinking | Calculation of Degree of Connection for Wordnet-Wikipedia/DBpedia instance mapping took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Wordnet-Wikipedia/DBpedia instance mapping took 0.0010421276092529297s
Interlinking | Calculation of Clustering coefficient for Wordnet-Wikipedia/DBpedia instance mapping took 7.82012939453125e-05s
Believability | Calculation of trust value for Wordnet-Wikipedia/DBpedia instance mapping took 1.1920928955078125e-05s
INFO | --- Analysis for wn-wiki-instances took 2.053696393966675s
Availability | SPARQL endpoint availability check for World Loanword Database took 4.029273986816406e-05s
Availability | VoID file availability check for World Loanword Database took 0.000949859619140625s
Completeness | Calculation of interlinking completeness for World Loanword Database took 0.17284083366394043s
Reputation | Calculation of the PageRank for World Loanword Database took 0.020074129104614258s
Interlinking | Calculation of Degree of Connection for World Loanword Database took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for World Loanword Database took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for World Loanword Database took 6.771087646484375e-05s
Believability | Calculation of trust value for World Loanword Database took 1.1920928955078125e-05s
INFO | --- Analysis for wold took 1.998422384262085s
Availability | SPARQL endpoint availability check for Wood Trick LLC took 8.153915405273438e-05s
Availability | VoID file availability check for Wood Trick LLC took 0.0005390644073486328s
Completeness | Calculation of interlinking completeness for Wood Trick LLC took 0.18712759017944336s
Reputation | Calculation of the PageRank for Wood Trick LLC took 0.02229928970336914s
Interlinking | Calculation of Degree of Connection for Wood Trick LLC took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Wood Trick LLC took 0.0007009506225585938s
Interlinking | Calculation of Clustering coefficient for Wood Trick LLC took 2.9087066650390625e-05s
Believability | Calculation of trust value for Wood Trick LLC took 1.049041748046875e-05s
INFO | --- Analysis for woodtrick took 2.0040292739868164s
Availability | SPARQL endpoint availability check for Word Formation Latin (WFL) in LiLa took 8.344650268554688e-05s
Availability | VoID file availability check for Word Formation Latin (WFL) in LiLa took 0.0004477500915527344s
Completeness | Calculation of interlinking completeness for Word Formation Latin (WFL) in LiLa took 0.17516469955444336s
Reputation | Calculation of the PageRank for Word Formation Latin (WFL) in LiLa took 0.020244598388671875s
Interlinking | Calculation of Degree of Connection for Word Formation Latin (WFL) in LiLa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for Word Formation Latin (WFL) in LiLa took 0.0007224082946777344s
Interlinking | Calculation of Clustering coefficient for Word Formation Latin (WFL) in LiLa took 3.552436828613281e-05s
Believability | Calculation of trust value for Word Formation Latin (WFL) in LiLa took 1.0728836059570312e-05s
INFO | --- Analysis for WordFormationLatin took 1.999469518661499s
Availability | SPARQL endpoint availability check for WordLift Blog EN took 4.076957702636719e-05s
Availability | VoID file availability check for WordLift Blog EN took 0.0004563331604003906s
Completeness | Calculation of interlinking completeness for WordLift Blog EN took 0.1842811107635498s
Reputation | Calculation of the PageRank for WordLift Blog EN took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for WordLift Blog EN took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for WordLift Blog EN took 0.0006971359252929688s
Interlinking | Calculation of Clustering coefficient for WordLift Blog EN took 9.894371032714844e-05s
Believability | Calculation of trust value for WordLift Blog EN took 1.1205673217773438e-05s
INFO | --- Analysis for wordlift-io-blog-en took 2.0263986587524414s
Availability | SPARQL endpoint availability check for WordLift IT took 3.910064697265625e-05s
Availability | VoID file availability check for WordLift IT took 0.0004277229309082031s
Completeness | Calculation of interlinking completeness for WordLift IT took 0.17295432090759277s
Reputation | Calculation of the PageRank for WordLift IT took 0.02026987075805664s
Interlinking | Calculation of Degree of Connection for WordLift IT took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for WordLift IT took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for WordLift IT took 9.965896606445312e-05s
Believability | Calculation of trust value for WordLift IT took 1.049041748046875e-05s
INFO | --- Analysis for wordlift-io-blog-it took 1.9781134128570557s
Availability | SPARQL endpoint availability check for Wordnet took 3.9577484130859375e-05s
Availability | VoID file availability check for Wordnet took 0.00021910667419433594s
Completeness | Calculation of interlinking completeness for Wordnet took 0.17418456077575684s
Reputation | Calculation of the PageRank for Wordnet took 0.020291805267333984s
Interlinking | Calculation of Degree of Connection for Wordnet took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Wordnet took 0.0007138252258300781s
Interlinking | Calculation of Clustering coefficient for Wordnet took 3.7670135498046875e-05s
Believability | Calculation of trust value for Wordnet took 1.1205673217773438e-05s
INFO | --- Analysis for wordnet took 1.9468498229980469s
Availability | SPARQL endpoint availability check for WordNet-RDF took 8.344650268554688e-05s
Availability | VoID file availability check for WordNet-RDF took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for WordNet-RDF took 0.18226861953735352s
Reputation | Calculation of the PageRank for WordNet-RDF took 0.02062392234802246s
Interlinking | Calculation of Degree of Connection for WordNet-RDF took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for WordNet-RDF took 0.0006985664367675781s
Interlinking | Calculation of Clustering coefficient for WordNet-RDF took 8.797645568847656e-05s
Believability | Calculation of trust value for WordNet-RDF took 1.0251998901367188e-05s
INFO | --- Analysis for wordnet-rdf took 1.963334321975708s
Availability | SPARQL endpoint availability check for wordpress took 4.291534423828125e-05s
Availability | VoID file availability check for wordpress took 0.0002753734588623047s
Completeness | Calculation of interlinking completeness for wordpress took 0.17587685585021973s
Reputation | Calculation of the PageRank for wordpress took 0.020293474197387695s
Interlinking | Calculation of Degree of Connection for wordpress took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for wordpress took 0.000705718994140625s
Interlinking | Calculation of Clustering coefficient for wordpress took 8.249282836914062e-05s
Believability | Calculation of trust value for wordpress took 5.245208740234375e-06s
INFO | --- Analysis for wordpress took 1.948615550994873s
Availability | SPARQL endpoint availability check for wordpress.post took 4.458427429199219e-05s
Availability | VoID file availability check for wordpress.post took 0.0002181529998779297s
Completeness | Calculation of interlinking completeness for wordpress.post took 0.17285847663879395s
Reputation | Calculation of the PageRank for wordpress.post took 0.02037501335144043s
Interlinking | Calculation of Degree of Connection for wordpress.post took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for wordpress.post took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for wordpress.post took 4.76837158203125e-05s
Believability | Calculation of trust value for wordpress.post took 7.867813110351562e-06s
INFO | --- Analysis for wordpress_post took 1.9034228324890137s
Availability | SPARQL endpoint availability check for World Bank Linked Data took 3.9577484130859375e-05s
Availability | VoID file availability check for World Bank Linked Data took 0.0002155303955078125s
Completeness | Calculation of interlinking completeness for World Bank Linked Data took 0.17445659637451172s
Reputation | Calculation of the PageRank for World Bank Linked Data took 0.020360469818115234s
Interlinking | Calculation of Degree of Connection for World Bank Linked Data took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for World Bank Linked Data took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for World Bank Linked Data took 0.00011873245239257812s
Believability | Calculation of trust value for World Bank Linked Data took 1.2636184692382812e-05s
INFO | --- Analysis for world-bank-linked-data took 1.9256253242492676s
Availability | SPARQL endpoint availability check for World Factbook (FU Berlin) took 4.7206878662109375e-05s
Availability | VoID file availability check for World Factbook (FU Berlin) took 0.0004363059997558594s
Completeness | Calculation of interlinking completeness for World Factbook (FU Berlin) took 0.1835024356842041s
Reputation | Calculation of the PageRank for World Factbook (FU Berlin) took 0.02159738540649414s
Interlinking | Calculation of Degree of Connection for World Factbook (FU Berlin) took 8.344650268554688e-06s
Interlinking | Calculation of Centrality for World Factbook (FU Berlin) took 0.0007469654083251953s
Interlinking | Calculation of Clustering coefficient for World Factbook (FU Berlin) took 7.987022399902344e-05s
Believability | Calculation of trust value for World Factbook (FU Berlin) took 1.1682510375976562e-05s
INFO | --- Analysis for world-factbook-fu-berlin took 2.022897481918335s
Availability | SPARQL endpoint availability check for World Wide Web Foundation took 4.363059997558594e-05s
Availability | VoID file availability check for World Wide Web Foundation took 0.000213623046875s
Completeness | Calculation of interlinking completeness for World Wide Web Foundation took 0.18173861503601074s
Reputation | Calculation of the PageRank for World Wide Web Foundation took 0.02236175537109375s
Interlinking | Calculation of Degree of Connection for World Wide Web Foundation took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for World Wide Web Foundation took 0.0007309913635253906s
Interlinking | Calculation of Clustering coefficient for World Wide Web Foundation took 8.130073547363281e-05s
Believability | Calculation of trust value for World Wide Web Foundation took 1.239776611328125e-05s
INFO | --- Analysis for world-wide-web-foundation took 1.9873671531677246s
Availability | SPARQL endpoint availability check for WikiPathways took 8.463859558105469e-05s
Availability | VoID file availability check for WikiPathways took 0.0004467964172363281s
Completeness | Calculation of interlinking completeness for WikiPathways took 0.18693256378173828s
Reputation | Calculation of the PageRank for WikiPathways took 0.020297765731811523s
Interlinking | Calculation of Degree of Connection for WikiPathways took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for WikiPathways took 0.0007021427154541016s
Interlinking | Calculation of Clustering coefficient for WikiPathways took 2.7418136596679688e-05s
Believability | Calculation of trust value for WikiPathways took 1.049041748046875e-05s
INFO | --- Analysis for wp took 2.041701555252075s
Availability | SPARQL endpoint availability check for wunderground.weatherreport took 8.249282836914062e-05s
Availability | VoID file availability check for wunderground.weatherreport took 0.0005199909210205078s
Completeness | Calculation of interlinking completeness for wunderground.weatherreport took 0.17702817916870117s
Reputation | Calculation of the PageRank for wunderground.weatherreport took 0.021585941314697266s
Interlinking | Calculation of Degree of Connection for wunderground.weatherreport took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for wunderground.weatherreport took 0.001047372817993164s
Interlinking | Calculation of Clustering coefficient for wunderground.weatherreport took 3.7670135498046875e-05s
Believability | Calculation of trust value for wunderground.weatherreport took 1.1920928955078125e-05s
INFO | --- Analysis for wunderground_weatherreport took 2.0155978202819824s
Availability | SPARQL endpoint availability check for World War 1 as Linked Open Data took 0.19163131713867188s
Availability | VoID file availability check for World War 1 as Linked Open Data took 0.0004680156707763672s
Extra | Recovery of all triples for World War 1 as Linked Open Data took 2.5123636722564697s
Performance | Total latancy measurement for World War 1 as Linked Open Data took 0.831052303314209s
Amount of data | Number of triples check for World War 1 as Linked Open Data took 0.24341440200805664s
Interoperability | New terms check for World War 1 as Linked Open Data took 1.5718410015106201s
Versatility | Languages check for World War 1 as Linked Open Data took 0.3888387680053711s
Interpretability | Number of blank nodes check for World War 1 as Linked Open Data took 0.23558402061462402s
Security | Check HTTPS for World War 1 as Linked Open Data took 0.25107526779174805s
Interpretability | RDF structures check for World War 1 as Linked Open Data took 0.26930975914001465s
Versatility | Serialization formats check for World War 1 as Linked Open Data took 0.2743868827819824s
Availability | RDF dump link check for World War 1 as Linked Open Data took 7.02567720413208s
License | MR license check for World War 1 as Linked Open Data took 0.19351506233215332s
License | HR license check for World War 1 as Linked Open Data took 1.829521894454956s
Amount of data | Number of property check for World War 1 as Linked Open Data took 0.19166207313537598s
Understandability | Number of label check for World War 1 as Linked Open Data took 0.3862133026123047s
Understandability | URI regex check for World War 1 as Linked Open Data took 0.36733102798461914s
Understandability | Vocabs check for World War 1 as Linked Open Data took 0.23012447357177734s
Verifiability | Authors check for World War 1 as Linked Open Data took 0.1924741268157959s
Verifiability | Publishers check for World War 1 as Linked Open Data took 0.19612884521484375s
Performance | Throughput check for World War 1 as Linked Open Data took 11.255851030349731s
Amount of data | Check the number of entities for World War 1 as Linked Open Data took 0.06619668006896973s
Verifiability | Contribs. check for World War 1 as Linked Open Data took 0.19168829917907715s
Interlinking | sameAs chians check for World War 1 as Linked Open Data took 0.49121761322021484s
Interlinking | skos check for World War 1 as Linked Open Data took 0.1948385238647461s
Interlinking | skos check for World War 1 as Linked Open Data took 0.15961217880249023s
Timeliness | dataset update frequency check for World War 1 as Linked Open Data took 0.20900583267211914s
Currency | Creation date check for World War 1 as Linked Open Data took 0.3870110511779785s
Currency | Modification date check for World War 1 as Linked Open Data took 0.19406509399414062s
Rep.Conc. | URIs length for World War 1 as Linked Open Data took 2.018249034881592s
Interoperability | New vocabularies check for World War 1 as Linked Open Data took 23.278918981552124s
Consistency | Deprecated classes/propertiers check for World War 1 as Linked Open Data took 0.35059022903442383s
Accuracy | Check Functional Property for World War 1 as Linked Open Data took 0.1926109790802002s
Accuracy | Check Inverse Functional Property for World War 1 as Linked Open Data took 0.1621842384338379s
Accuracy | Check Empty annotation labels for World War 1 as Linked Open Data took 1.1857542991638184s
Accuracy | Check White space in annotation for World War 1 as Linked Open Data took 0.049385786056518555s
Accuracy | Check Datatype consistency for World War 1 as Linked Open Data took 0.3148009777069092s
Consistency | Disjoint class check for World War 1 as Linked Open Data took 0.19233345985412598s
Consistency | Check Misplaced properties for World War 1 as Linked Open Data took 0.6152641773223877s
Consistency | Check Ontology hijacking for World War 1 as Linked Open Data took 2.1803464889526367s
Consistency | Check Invalid usage of undefined classes for World War 1 as Linked Open Data took 1.4003689289093018s
Consistency | Check Invalid usage of undefined properties for World War 1 as Linked Open Data took 1.6484456062316895s
Conciseness | Check Extensional conciseness for World War 1 as Linked Open Data took 0.19098758697509766s
Conciseness | Check Intensional conciseness for World War 1 as Linked Open Data took 0.6812803745269775s
Security | Sign check for World War 1 as Linked Open Data took 0.18828821182250977s
Availability | Check URIs Dereferenciability for World War 1 as Linked Open Data took 1529.6198155879974s
Completeness | Calculation of interlinking completeness for World War 1 as Linked Open Data took 0.3956592082977295s
Reputation | Calculation of the PageRank for World War 1 as Linked Open Data took 0.02167534828186035s
Interlinking | Calculation of Degree of Connection for World War 1 as Linked Open Data took 1.6927719116210938e-05s
Interlinking | Calculation of Centrality for World War 1 as Linked Open Data took 0.0008292198181152344s
Interlinking | Calculation of Clustering coefficient for World War 1 as Linked Open Data took 0.00014829635620117188s
Interoperability | Check the re-using of existing vocabs for World War 1 as Linked Open Data took 8.59175181388855s
Believability | Calculation of trust value for World War 1 as Linked Open Data took 1.2874603271484375e-05s
INFO | --- Analysis for ww1lod took 1628.7907388210297s
Availability | SPARQL endpoint availability check for XlendiAmphorae took 8.440017700195312e-05s
Availability | VoID file availability check for XlendiAmphorae took 0.0005276203155517578s
Completeness | Calculation of interlinking completeness for XlendiAmphorae took 0.17405056953430176s
Reputation | Calculation of the PageRank for XlendiAmphorae took 0.020355939865112305s
Interlinking | Calculation of Degree of Connection for XlendiAmphorae took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for XlendiAmphorae took 0.0007264614105224609s
Interlinking | Calculation of Clustering coefficient for XlendiAmphorae took 3.075599670410156e-05s
Believability | Calculation of trust value for XlendiAmphorae took 1.2874603271484375e-05s
INFO | --- Analysis for xlendiamphorae took 1.975644826889038s
Availability | SPARQL endpoint availability check for xLiD-Lexica took 4.1961669921875e-05s
Availability | VoID file availability check for xLiD-Lexica took 0.0005397796630859375s
Completeness | Calculation of interlinking completeness for xLiD-Lexica took 0.1815042495727539s
Reputation | Calculation of the PageRank for xLiD-Lexica took 0.020236968994140625s
Interlinking | Calculation of Degree of Connection for xLiD-Lexica took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for xLiD-Lexica took 0.0006906986236572266s
Interlinking | Calculation of Clustering coefficient for xLiD-Lexica took 6.222724914550781e-05s
Believability | Calculation of trust value for xLiD-Lexica took 1.2874603271484375e-05s
INFO | --- Analysis for xlid-lexica took 1.997840166091919s
Availability | SPARQL endpoint availability check for Open Multilingual Wordnet took 0.00013303756713867188s
Availability | VoID file availability check for Open Multilingual Wordnet took 0.001119852066040039s
Completeness | Calculation of interlinking completeness for Open Multilingual Wordnet took 0.1810436248779297s
Reputation | Calculation of the PageRank for Open Multilingual Wordnet took 0.021723508834838867s
Interlinking | Calculation of Degree of Connection for Open Multilingual Wordnet took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for Open Multilingual Wordnet took 0.0007152557373046875s
Interlinking | Calculation of Clustering coefficient for Open Multilingual Wordnet took 3.647804260253906e-05s
Believability | Calculation of trust value for Open Multilingual Wordnet took 1.0728836059570312e-05s
INFO | --- Analysis for xwn took 1.9630541801452637s
Availability | SPARQL endpoint availability check for xxx took 0.00010132789611816406s
Availability | VoID file availability check for xxx took 0.00046634674072265625s
Completeness | Calculation of interlinking completeness for xxx took 0.1749110221862793s
Reputation | Calculation of the PageRank for xxx took 0.020206689834594727s
Interlinking | Calculation of Degree of Connection for xxx took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for xxx took 0.0007038116455078125s
Interlinking | Calculation of Clustering coefficient for xxx took 2.9325485229492188e-05s
Believability | Calculation of trust value for xxx took 1.1205673217773438e-05s
INFO | --- Analysis for xx took 1.976487398147583s
Availability | SPARQL endpoint availability check for YAGO took 4.267692565917969e-05s
Availability | VoID file availability check for YAGO took 0.0004665851593017578s
Completeness | Calculation of interlinking completeness for YAGO took 0.1877429485321045s
Reputation | Calculation of the PageRank for YAGO took 0.020103931427001953s
Interlinking | Calculation of Degree of Connection for YAGO took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for YAGO took 0.0006883144378662109s
Interlinking | Calculation of Clustering coefficient for YAGO took 0.00012445449829101562s
Believability | Calculation of trust value for YAGO took 1.239776611328125e-05s
INFO | --- Analysis for yago took 2.0013222694396973s
Availability | SPARQL endpoint availability check for Yahoo Geoplanet RDF took 3.981590270996094e-05s
Availability | VoID file availability check for Yahoo Geoplanet RDF took 0.00021266937255859375s
Completeness | Calculation of interlinking completeness for Yahoo Geoplanet RDF took 0.1694481372833252s
Reputation | Calculation of the PageRank for Yahoo Geoplanet RDF took 0.02025461196899414s
Interlinking | Calculation of Degree of Connection for Yahoo Geoplanet RDF took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Yahoo Geoplanet RDF took 0.0006949901580810547s
Interlinking | Calculation of Clustering coefficient for Yahoo Geoplanet RDF took 7.534027099609375e-05s
Believability | Calculation of trust value for Yahoo Geoplanet RDF took 7.3909759521484375e-06s
INFO | --- Analysis for yahoo_geoplanet took 1.9109418392181396s
Availability | SPARQL endpoint availability check for Yale Senselab took 3.981590270996094e-05s
Availability | VoID file availability check for Yale Senselab took 0.0002205371856689453s
Completeness | Calculation of interlinking completeness for Yale Senselab took 0.1746807098388672s
Reputation | Calculation of the PageRank for Yale Senselab took 0.020120620727539062s
Interlinking | Calculation of Degree of Connection for Yale Senselab took 9.5367431640625e-06s
Interlinking | Calculation of Centrality for Yale Senselab took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for Yale Senselab took 2.8371810913085938e-05s
Believability | Calculation of trust value for Yale Senselab took 7.867813110351562e-06s
INFO | --- Analysis for yale_senselab took 1.944953203201294s
Availability | SPARQL endpoint availability check for test-dapp-2 took 8.392333984375e-05s
Availability | VoID file availability check for test-dapp-2 took 0.0004642009735107422s
Completeness | Calculation of interlinking completeness for test-dapp-2 took 0.17561769485473633s
Reputation | Calculation of the PageRank for test-dapp-2 took 0.020257949829101562s
Interlinking | Calculation of Degree of Connection for test-dapp-2 took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for test-dapp-2 took 0.0006916522979736328s
Interlinking | Calculation of Clustering coefficient for test-dapp-2 took 2.7418136596679688e-05s
Believability | Calculation of trust value for test-dapp-2 took 8.106231689453125e-06s
INFO | --- Analysis for yordhis took 2.1118814945220947s
Availability | SPARQL endpoint availability check for Yovisto - academic video search took 8.320808410644531e-05s
Availability | VoID file availability check for Yovisto - academic video search took 0.0005080699920654297s
Completeness | Calculation of interlinking completeness for Yovisto - academic video search took 0.16910243034362793s
Reputation | Calculation of the PageRank for Yovisto - academic video search took 0.022340774536132812s
Interlinking | Calculation of Degree of Connection for Yovisto - academic video search took 8.58306884765625e-06s
Interlinking | Calculation of Centrality for Yovisto - academic video search took 0.0007102489471435547s
Interlinking | Calculation of Clustering coefficient for Yovisto - academic video search took 6.389617919921875e-05s
Believability | Calculation of trust value for Yovisto - academic video search took 1.0251998901367188e-05s
INFO | --- Analysis for yovisto took 1.981532335281372s
Availability | SPARQL endpoint availability check for Yleinen suomalainen asiasanasto - YSA took 8.630752563476562e-05s
Availability | VoID file availability check for Yleinen suomalainen asiasanasto - YSA took 0.0005185604095458984s
Completeness | Calculation of interlinking completeness for Yleinen suomalainen asiasanasto - YSA took 0.1819310188293457s
Reputation | Calculation of the PageRank for Yleinen suomalainen asiasanasto - YSA took 0.02030181884765625s
Interlinking | Calculation of Degree of Connection for Yleinen suomalainen asiasanasto - YSA took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Yleinen suomalainen asiasanasto - YSA took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for Yleinen suomalainen asiasanasto - YSA took 3.170967102050781e-05s
Believability | Calculation of trust value for Yleinen suomalainen asiasanasto - YSA took 1.1682510375976562e-05s
INFO | --- Analysis for ysa took 2.019667387008667s
Availability | SPARQL endpoint availability check for YSO - General Finnish Ontology took 9.059906005859375e-05s
Availability | VoID file availability check for YSO - General Finnish Ontology took 0.00046753883361816406s
Completeness | Calculation of interlinking completeness for YSO - General Finnish Ontology took 0.1849985122680664s
Reputation | Calculation of the PageRank for YSO - General Finnish Ontology took 0.02082967758178711s
Interlinking | Calculation of Degree of Connection for YSO - General Finnish Ontology took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for YSO - General Finnish Ontology took 0.0006945133209228516s
Interlinking | Calculation of Clustering coefficient for YSO - General Finnish Ontology took 4.887580871582031e-05s
Believability | Calculation of trust value for YSO - General Finnish Ontology took 7.62939453125e-06s
INFO | --- Analysis for yso took 1.9816548824310303s
Availability | SPARQL endpoint availability check for yso-fi-allars took 4.1484832763671875e-05s
Availability | VoID file availability check for yso-fi-allars took 0.00021958351135253906s
Completeness | Calculation of interlinking completeness for yso-fi-allars took 0.16869735717773438s
Reputation | Calculation of the PageRank for yso-fi-allars took 0.020626068115234375s
Interlinking | Calculation of Degree of Connection for yso-fi-allars took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for yso-fi-allars took 0.0007100105285644531s
Interlinking | Calculation of Clustering coefficient for yso-fi-allars took 3.24249267578125e-05s
Believability | Calculation of trust value for yso-fi-allars took 5.7220458984375e-06s
INFO | --- Analysis for yso-fi-allars took 1.8836801052093506s
Availability | SPARQL endpoint availability check for yso-fi-ysa took 4.935264587402344e-05s
Availability | VoID file availability check for yso-fi-ysa took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for yso-fi-ysa took 0.1786329746246338s
Reputation | Calculation of the PageRank for yso-fi-ysa took 0.020174026489257812s
Interlinking | Calculation of Degree of Connection for yso-fi-ysa took 8.821487426757812e-06s
Interlinking | Calculation of Centrality for yso-fi-ysa took 0.0007135868072509766s
Interlinking | Calculation of Clustering coefficient for yso-fi-ysa took 3.123283386230469e-05s
Believability | Calculation of trust value for yso-fi-ysa took 5.9604644775390625e-06s
INFO | --- Analysis for yso-fi-ysa took 1.9392175674438477s
Availability | SPARQL endpoint availability check for YSO places took 5.316734313964844e-05s
Availability | VoID file availability check for YSO places took 0.00021982192993164062s
Completeness | Calculation of interlinking completeness for YSO places took 0.1731095314025879s
Reputation | Calculation of the PageRank for YSO places took 0.02026820182800293s
Interlinking | Calculation of Degree of Connection for YSO places took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for YSO places took 0.0007050037384033203s
Interlinking | Calculation of Clustering coefficient for YSO places took 2.8133392333984375e-05s
Believability | Calculation of trust value for YSO places took 5.0067901611328125e-06s
INFO | --- Analysis for yso-paikat took 1.9440343379974365s
Availability | SPARQL endpoint availability check for Datos Abiertos de Zaragoza took 3.886222839355469e-05s
Availability | VoID file availability check for Datos Abiertos de Zaragoza took 0.00021886825561523438s
Completeness | Calculation of interlinking completeness for Datos Abiertos de Zaragoza took 0.16819167137145996s
Reputation | Calculation of the PageRank for Datos Abiertos de Zaragoza took 0.020172119140625s
Interlinking | Calculation of Degree of Connection for Datos Abiertos de Zaragoza took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for Datos Abiertos de Zaragoza took 0.000698089599609375s
Interlinking | Calculation of Clustering coefficient for Datos Abiertos de Zaragoza took 4.839897155761719e-05s
Believability | Calculation of trust value for Datos Abiertos de Zaragoza took 5.9604644775390625e-06s
INFO | --- Analysis for zaragoza-datosabiertos took 1.908632516860962s
Availability | SPARQL endpoint availability check for zaragoza_turruta took 4.8160552978515625e-05s
Availability | VoID file availability check for zaragoza_turruta took 0.00022029876708984375s
Completeness | Calculation of interlinking completeness for zaragoza_turruta took 0.17756152153015137s
Reputation | Calculation of the PageRank for zaragoza_turruta took 0.020356416702270508s
Interlinking | Calculation of Degree of Connection for zaragoza_turruta took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for zaragoza_turruta took 0.0006983280181884766s
Interlinking | Calculation of Clustering coefficient for zaragoza_turruta took 3.3855438232421875e-05s
Believability | Calculation of trust value for zaragoza_turruta took 7.3909759521484375e-06s
INFO | --- Analysis for zaragoza_turruta took 2.027362823486328s
Availability | SPARQL endpoint availability check for ZBW Labs took 4.792213439941406e-05s
Availability | VoID file availability check for ZBW Labs took 0.0002231597900390625s
Completeness | Calculation of interlinking completeness for ZBW Labs took 0.1818375587463379s
Reputation | Calculation of the PageRank for ZBW Labs took 0.02016472816467285s
Interlinking | Calculation of Degree of Connection for ZBW Labs took 9.298324584960938e-06s
Interlinking | Calculation of Centrality for ZBW Labs took 0.0007054805755615234s
Interlinking | Calculation of Clustering coefficient for ZBW Labs took 6.389617919921875e-05s
Believability | Calculation of trust value for ZBW Labs took 6.4373016357421875e-06s
INFO | --- Analysis for zbw-labs took 1.8909261226654053s
Availability | SPARQL endpoint availability check for 20th Century Press Archives took 0.41415929794311523s
Availability | VoID file availability check for 20th Century Press Archives took 0.00024199485778808594s
Extra | Recovery of all triples for 20th Century Press Archives took 26.99211287498474s
Performance | Total latancy measurement for 20th Century Press Archives took 0.7281582355499268s
Amount of data | Number of triples check for 20th Century Press Archives took 1.143911361694336s
Interoperability | New terms check for 20th Century Press Archives took 1.6102313995361328s
Versatility | Languages check for 20th Century Press Archives took 3.3245391845703125s
Interpretability | Number of blank nodes check for 20th Century Press Archives took 0.9507441520690918s
Interpretability | RDF structures check for 20th Century Press Archives took 0.1679821014404297s
Versatility | Serialization formats check for 20th Century Press Archives took 0.1472339630126953s
Availability | RDF dump link check for 20th Century Press Archives took 0.14665913581848145s
License | MR license check for 20th Century Press Archives took 0.16137957572937012s
License | HR license check for 20th Century Press Archives took 5.4988672733306885s
Amount of data | Number of property check for 20th Century Press Archives took 0.16744279861450195s
Understandability | Number of label check for 20th Century Press Archives took 0.5664577484130859s
Understandability | URI regex check for 20th Century Press Archives took 0.30362415313720703s
Understandability | Vocabs check for 20th Century Press Archives took 0.1691436767578125s
Verifiability | Authors check for 20th Century Press Archives took 0.14748930931091309s
Verifiability | Publishers check for 20th Century Press Archives took 0.1424851417541504s
Performance | Throughput check for 20th Century Press Archives took 10.24588418006897s
Amount of data | Check the number of entities for 20th Century Press Archives took 0.00014710426330566406s
Verifiability | Contribs. check for 20th Century Press Archives took 0.14664435386657715s
Interlinking | sameAs chians check for 20th Century Press Archives took 0.14355731010437012s
Interlinking | skos check for 20th Century Press Archives took 0.19182729721069336s
Interlinking | skos check for 20th Century Press Archives took 0.18560051918029785s
Timeliness | dataset update frequency check for 20th Century Press Archives took 0.15015482902526855s
Currency | Creation date check for 20th Century Press Archives took 0.2858314514160156s
Currency | Modification date check for 20th Century Press Archives took 0.2882528305053711s
Rep.Conc. | URIs length for 20th Century Press Archives took 14.930640459060669s
Interoperability | New vocabularies check for 20th Century Press Archives took 7.152557373046875e-06s
Consistency | Deprecated classes/propertiers check for 20th Century Press Archives took 0.1659526824951172s
Accuracy | Check Functional Property for 20th Century Press Archives took 0.1591506004333496s
Accuracy | Check Inverse Functional Property for 20th Century Press Archives took 0.15962004661560059s
Accuracy | Check Empty annotation labels for 20th Century Press Archives took 7.793602466583252s
Accuracy | Check White space in annotation for 20th Century Press Archives took 0.8757338523864746s
Accuracy | Check Datatype consistency for 20th Century Press Archives took 4.000391960144043s
Consistency | Disjoint class check for 20th Century Press Archives took 0.15913057327270508s
Consistency | Check Misplaced properties for 20th Century Press Archives took 2.332287311553955s
Consistency | Check Ontology hijacking for 20th Century Press Archives took 2.5933969020843506s
Consistency | Check Invalid usage of undefined classes for 20th Century Press Archives took 6.952388763427734s
Consistency | Check Invalid usage of undefined properties for 20th Century Press Archives took 3.5872979164123535s
Conciseness | Check Extensional conciseness for 20th Century Press Archives took 2.7572286128997803s
Security | Sign check for 20th Century Press Archives took 0.15919113159179688s
Availability | Check URIs Dereferenciability for 20th Century Press Archives took 1.978065013885498s
Completeness | Calculation of interlinking completeness for 20th Century Press Archives took 0.21020746231079102s
Reputation | Calculation of the PageRank for 20th Century Press Archives took 0.021064043045043945s
Interlinking | Calculation of Degree of Connection for 20th Century Press Archives took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for 20th Century Press Archives took 0.0007126331329345703s
Interlinking | Calculation of Clustering coefficient for 20th Century Press Archives took 0.00010514259338378906s
Interoperability | Check the re-using of existing vocabs for 20th Century Press Archives took 2.1457672119140625e-06s
Believability | Calculation of trust value for 20th Century Press Archives took 1.239776611328125e-05s
INFO | --- Analysis for zbw-pressemappe20 took 122.19823694229126s
Availability | SPARQL endpoint availability check for zhishi.lemon took 4.076957702636719e-05s
Availability | VoID file availability check for zhishi.lemon took 0.00045013427734375s
Completeness | Calculation of interlinking completeness for zhishi.lemon took 0.17890334129333496s
Reputation | Calculation of the PageRank for zhishi.lemon took 0.020220518112182617s
Interlinking | Calculation of Degree of Connection for zhishi.lemon took 9.775161743164062e-06s
Interlinking | Calculation of Centrality for zhishi.lemon took 0.0007061958312988281s
Interlinking | Calculation of Clustering coefficient for zhishi.lemon took 4.1961669921875e-05s
Believability | Calculation of trust value for zhishi.lemon took 1.0967254638671875e-05s
INFO | --- Analysis for zhishi-lemon took 2.0300188064575195s
Availability | SPARQL endpoint availability check for Zhishi.me took 4.38690185546875e-05s
Availability | VoID file availability check for Zhishi.me took 0.00043487548828125s
Completeness | Calculation of interlinking completeness for Zhishi.me took 0.18164873123168945s
Reputation | Calculation of the PageRank for Zhishi.me took 0.02099466323852539s
Interlinking | Calculation of Degree of Connection for Zhishi.me took 1.0728836059570312e-05s
Interlinking | Calculation of Centrality for Zhishi.me took 0.0006911754608154297s
Interlinking | Calculation of Clustering coefficient for Zhishi.me took 7.009506225585938e-05s
Believability | Calculation of trust value for Zhishi.me took 1.2874603271484375e-05s
INFO | --- Analysis for zhishi-me took 1.985792875289917s
Availability | SPARQL endpoint availability check for MusicBrainz (zitgist.com) took 9.298324584960938e-05s
Availability | VoID file availability check for MusicBrainz (zitgist.com) took 0.0005006790161132812s
Completeness | Calculation of interlinking completeness for MusicBrainz (zitgist.com) took 0.1787734031677246s
Reputation | Calculation of the PageRank for MusicBrainz (zitgist.com) took 0.02099752426147461s
Interlinking | Calculation of Degree of Connection for MusicBrainz (zitgist.com) took 1.0251998901367188e-05s
Interlinking | Calculation of Centrality for MusicBrainz (zitgist.com) took 0.000701904296875s
Interlinking | Calculation of Clustering coefficient for MusicBrainz (zitgist.com) took 8.177757263183594e-05s
Believability | Calculation of trust value for MusicBrainz (zitgist.com) took 8.106231689453125e-06s
INFO | --- Analysis for zitgist-musicbrainz took 1.9960241317749023s
Availability | SPARQL endpoint availability check for 红色经典歌曲关联数据集 took 4.482269287109375e-05s
Availability | VoID file availability check for 红色经典歌曲关联数据集 took 0.0002837181091308594s
Completeness | Calculation of interlinking completeness for 红色经典歌曲关联数据集 took 0.1755828857421875s
Reputation | Calculation of the PageRank for 红色经典歌曲关联数据集 took 0.020875930786132812s
Interlinking | Calculation of Degree of Connection for 红色经典歌曲关联数据集 took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for 红色经典歌曲关联数据集 took 0.0010287761688232422s
Interlinking | Calculation of Clustering coefficient for 红色经典歌曲关联数据集 took 4.076957702636719e-05s
Believability | Calculation of trust value for 红色经典歌曲关联数据集 took 1.33514404296875e-05s
INFO | --- Analysis for 红色经典歌曲关联数据集 took 2.017753839492798s
Availability | SPARQL endpoint availability check for performing-arts.ch took 0.34029150009155273s
Availability | VoID file availability check for performing-arts.ch took 0.0005125999450683594s
Extra | Recovery of all triples for performing-arts.ch took 16.374027490615845s
Performance | Total latancy measurement for performing-arts.ch took 0.7839677333831787s
Amount of data | Number of triples check for performing-arts.ch took 30.806052446365356s
Interoperability | New terms check for performing-arts.ch took 1.5316083431243896s
Versatility | Languages check for performing-arts.ch took 60.143837451934814s
Interpretability | Number of blank nodes check for performing-arts.ch took 60.140748023986816s
Interpretability | RDF structures check for performing-arts.ch took 0.18542218208312988s
Versatility | Serialization formats check for performing-arts.ch took 0.16696929931640625s
Availability | RDF dump link check for performing-arts.ch took 0.15729951858520508s
License | MR license check for performing-arts.ch took 0.17067980766296387s
License | HR license check for performing-arts.ch took 49.26327204704285s
Amount of data | Number of property check for performing-arts.ch took 0.2291576862335205s
Understandability | Number of label check for performing-arts.ch took 2.3284499645233154s
Understandability | URI regex check for performing-arts.ch took 0.32755112648010254s
Understandability | Vocabs check for performing-arts.ch took 0.16675114631652832s
Verifiability | Authors check for performing-arts.ch took 0.17103052139282227s
Verifiability | Publishers check for performing-arts.ch took 0.16544032096862793s
Performance | Throughput check for performing-arts.ch took 11.301880121231079s
Amount of data | Check the number of entities for performing-arts.ch took 7.009506225585938e-05s
Verifiability | Contribs. check for performing-arts.ch took 0.16640639305114746s
Interlinking | sameAs chians check for performing-arts.ch took 0.36069774627685547s
Interlinking | skos check for performing-arts.ch took 0.17659306526184082s
Interlinking | skos check for performing-arts.ch took 0.17687129974365234s
Timeliness | dataset update frequency check for performing-arts.ch took 0.169846773147583s
Currency | Creation date check for performing-arts.ch took 0.334122896194458s
Currency | Modification date check for performing-arts.ch took 0.3488903045654297s
Rep.Conc. | URIs length for performing-arts.ch took 21.384029388427734s
Interoperability | New vocabularies check for performing-arts.ch took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for performing-arts.ch took 0.1630258560180664s
Accuracy | Check Functional Property for performing-arts.ch took 0.16002345085144043s
Accuracy | Check Inverse Functional Property for performing-arts.ch took 0.16417264938354492s
Accuracy | Check Empty annotation labels for performing-arts.ch took 11.264073133468628s
Accuracy | Check White space in annotation for performing-arts.ch took 2.5433640480041504s
Accuracy | Check Datatype consistency for performing-arts.ch took 5.814241647720337s
Consistency | Disjoint class check for performing-arts.ch took 0.1635751724243164s
Consistency | Check Misplaced properties for performing-arts.ch took 0.37890625s
Consistency | Misplaced classes for performing-arts.ch took 8.428576231002808s
Consistency | Check Ontology hijacking for performing-arts.ch took 40.75027823448181s
Consistency | Check Invalid usage of undefined classes for performing-arts.ch took 15199.022338867188s
Consistency | Check Invalid usage of undefined properties for performing-arts.ch took 1.7693092823028564s
Conciseness | Check Extensional conciseness for performing-arts.ch took 2.918449640274048s
Conciseness | Check Intensional conciseness for performing-arts.ch took 0.31286120414733887s
Security | Sign check for performing-arts.ch took 0.1673722267150879s
Availability | Check URIs Dereferenciability for performing-arts.ch took 3.5467352867126465s
Completeness | Calculation of interlinking completeness for performing-arts.ch took 0.44620776176452637s
Reputation | Calculation of the PageRank for performing-arts.ch took 0.021742820739746094s
Interlinking | Calculation of Degree of Connection for performing-arts.ch took 1.811981201171875e-05s
Interlinking | Calculation of Centrality for performing-arts.ch took 0.0006880760192871094s
Interlinking | Calculation of Clustering coefficient for performing-arts.ch took 6.580352783203125e-05s
Interoperability | Check the re-using of existing vocabs for performing-arts.ch took 5.245208740234375e-06s
Believability | Calculation of trust value for performing-arts.ch took 1.4781951904296875e-05s
INFO | --- Analysis for performing-arts.ch took 15952.606623411179s
Availability | SPARQL endpoint availability check for The Art & Architecture Thesaurus took 2.9821252822875977s
Availability | VoID file availability check for The Art & Architecture Thesaurus took 0.0006265640258789062s
Completeness | Calculation of interlinking completeness for The Art & Architecture Thesaurus took 0.18326592445373535s
Reputation | Calculation of the PageRank for The Art & Architecture Thesaurus took 0.021791696548461914s
Interlinking | Calculation of Degree of Connection for The Art & Architecture Thesaurus took 2.193450927734375e-05s
Interlinking | Calculation of Centrality for The Art & Architecture Thesaurus took 0.0007545948028564453s
Interlinking | Calculation of Clustering coefficient for The Art & Architecture Thesaurus took 1.3113021850585938e-05s
Believability | Calculation of trust value for The Art & Architecture Thesaurus took 1.1444091796875e-05s
INFO | --- Analysis for The-AA-Thesaurus took 7.668070077896118s
Availability | SPARQL endpoint availability check for MiMoTextBase took 1.4243390560150146s
Availability | VoID file availability check for MiMoTextBase took 0.0006222724914550781s
Completeness | Calculation of interlinking completeness for MiMoTextBase took 0.19316816329956055s
Reputation | Calculation of the PageRank for MiMoTextBase took 0.020952701568603516s
Interlinking | Calculation of Degree of Connection for MiMoTextBase took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for MiMoTextBase took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for MiMoTextBase took 1.3113021850585938e-05s
Believability | Calculation of trust value for MiMoTextBase took 1.0251998901367188e-05s
INFO | --- Analysis for MiMoTextBase took 5.002426862716675s
Availability | SPARQL endpoint availability check for National Library of Sweden took 0.42131710052490234s
Availability | VoID file availability check for National Library of Sweden took 0.0005741119384765625s
Extra | Recovery of all triples for National Library of Sweden took 6.965921640396118s
Performance | Total latancy measurement for National Library of Sweden took 1.036961317062378s
Amount of data | Number of triples check for National Library of Sweden took 19.47532892227173s
Interoperability | New terms check for National Library of Sweden took 16.136935472488403s
Versatility | Languages check for National Library of Sweden took 0.21544289588928223s
Interpretability | Number of blank nodes check for National Library of Sweden took 300.2357211112976s
Interpretability | RDF structures check for National Library of Sweden took 0.293609619140625s
Versatility | Serialization formats check for National Library of Sweden took 0.22417807579040527s
Availability | RDF dump link check for National Library of Sweden took 0.24929428100585938s
License | MR license check for National Library of Sweden took 0.22949552536010742s
License | HR license check for National Library of Sweden took 0.21748018264770508s
Amount of data | Number of property check for National Library of Sweden took 0.22852396965026855s
Understandability | Number of label check for National Library of Sweden took 0.23606300354003906s
Understandability | URI regex check for National Library of Sweden took 0.42619824409484863s
Understandability | Vocabs check for National Library of Sweden took 0.21450018882751465s
Verifiability | Authors check for National Library of Sweden took 0.235640287399292s
Verifiability | Publishers check for National Library of Sweden took 0.23247361183166504s
Performance | Throughput check for National Library of Sweden took 10.553565502166748s
Amount of data | Check the number of entities for National Library of Sweden took 7.152557373046875e-05s
Verifiability | Contribs. check for National Library of Sweden took 0.22103595733642578s
Interlinking | sameAs chians check for National Library of Sweden took 0.22508835792541504s
Interlinking | skos check for National Library of Sweden took 0.2114701271057129s
Interlinking | skos check for National Library of Sweden took 0.21049714088439941s
Timeliness | dataset update frequency check for National Library of Sweden took 0.21296405792236328s
Currency | Creation date check for National Library of Sweden took 0.42383623123168945s
Currency | Modification date check for National Library of Sweden took 0.42908596992492676s
Rep.Conc. | URIs length for National Library of Sweden took 82.78627490997314s
Interoperability | New vocabularies check for National Library of Sweden took 6.4373016357421875e-06s
Consistency | Deprecated classes/propertiers check for National Library of Sweden took 0.22908997535705566s
Accuracy | Check Functional Property for National Library of Sweden took 0.20956993103027344s
Accuracy | Check Inverse Functional Property for National Library of Sweden took 0.21220755577087402s
Accuracy | Check Datatype consistency for National Library of Sweden took 0.26542186737060547s
Consistency | Disjoint class check for National Library of Sweden took 0.2089855670928955s
Consistency | Check Misplaced properties for National Library of Sweden took 60.98400831222534s
Consistency | Misplaced classes for National Library of Sweden took 1.1357638835906982s
Consistency | Check Ontology hijacking for National Library of Sweden took 3.70133113861084s
Consistency | Check Invalid usage of undefined classes for National Library of Sweden took 1.3211491107940674s
Consistency | Check Invalid usage of undefined properties for National Library of Sweden took 62.069804430007935s
Conciseness | Check Extensional conciseness for National Library of Sweden took 0.27748751640319824s
Conciseness | Check Intensional conciseness for National Library of Sweden took 0.411848783493042s
Security | Sign check for National Library of Sweden took 0.2153949737548828s
Availability | Check URIs Dereferenciability for National Library of Sweden took 16.11619234085083s
Completeness | Calculation of interlinking completeness for National Library of Sweden took 0.23498082160949707s
Reputation | Calculation of the PageRank for National Library of Sweden took 0.02061915397644043s
Interlinking | Calculation of Degree of Connection for National Library of Sweden took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for National Library of Sweden took 0.0007104873657226562s
Interlinking | Calculation of Clustering coefficient for National Library of Sweden took 1.9550323486328125e-05s
Interoperability | Check the re-using of existing vocabs for National Library of Sweden took 1.6689300537109375e-06s
Believability | Calculation of trust value for National Library of Sweden took 1.2636184692382812e-05s
INFO | --- Analysis for NLS took 1386.6004538536072s
Availability | SPARQL endpoint availability check for Japan Search took 2.04679012298584s
Availability | VoID file availability check for Japan Search took 0.0002999305725097656s
Extra | Recovery of all triples for Japan Search took 4.132207632064819s
Performance | Total latancy measurement for Japan Search took 2.2211499214172363s
Amount of data | Number of triples check for Japan Search took 5.080134391784668s
Interoperability | New terms check for Japan Search took 3.796299934387207s
Versatility | Languages check for Japan Search took 0.7427012920379639s
Interpretability | Number of blank nodes check for Japan Search took 12.294241905212402s
Interpretability | RDF structures check for Japan Search took 0.852250337600708s
Versatility | Serialization formats check for Japan Search took 0.39147114753723145s
Availability | RDF dump link check for Japan Search took 0.31743359565734863s
License | MR license check for Japan Search took 0.4787454605102539s
License | HR license check for Japan Search took 10.295786619186401s
Amount of data | Number of property check for Japan Search took 0.29210734367370605s
Understandability | Number of label check for Japan Search took 2.986583948135376s
Understandability | URI regex check for Japan Search took 0.580740213394165s
Understandability | Vocabs check for Japan Search took 0.2842371463775635s
Verifiability | Authors check for Japan Search took 0.3136720657348633s
Verifiability | Publishers check for Japan Search took 0.7374067306518555s
Performance | Throughput check for Japan Search took 11.32626986503601s
Amount of data | Check the number of entities for Japan Search took 7.009506225585938e-05s
Verifiability | Contribs. check for Japan Search took 0.2809641361236572s
Interlinking | sameAs chians check for Japan Search took 0.2848246097564697s
Interlinking | skos check for Japan Search took 0.30634474754333496s
Interlinking | skos check for Japan Search took 0.2844395637512207s
Timeliness | dataset update frequency check for Japan Search took 0.3498988151550293s
Currency | Creation date check for Japan Search took 0.566678524017334s
Currency | Modification date check for Japan Search took 0.5789933204650879s
Rep.Conc. | URIs length for Japan Search took 15.567997694015503s
Interoperability | New vocabularies check for Japan Search took 2.86102294921875e-06s
Consistency | Deprecated classes/propertiers check for Japan Search took 0.7455141544342041s
Accuracy | Check Empty annotation labels for Japan Search took 1.7569053173065186s
Accuracy | Check White space in annotation for Japan Search took 0.0290987491607666s
Accuracy | Check Datatype consistency for Japan Search took 0.028136491775512695s
Consistency | Disjoint class check for Japan Search took 0.2855105400085449s
Consistency | Check Misplaced properties for Japan Search took 10.577481746673584s
Consistency | Misplaced classes for Japan Search took 0.3799924850463867s
Consistency | Check Ontology hijacking for Japan Search took 3.499300003051758s
Consistency | Check Invalid usage of undefined classes for Japan Search took 1.3420188426971436s
Consistency | Check Invalid usage of undefined properties for Japan Search took 11.61516809463501s
Conciseness | Check Extensional conciseness for Japan Search took 0.03787565231323242s
Conciseness | Check Intensional conciseness for Japan Search took 0.9736146926879883s
Security | Sign check for Japan Search took 0.7402195930480957s
Availability | Check URIs Dereferenciability for Japan Search took 16.309911727905273s
Completeness | Calculation of interlinking completeness for Japan Search took 0.176802396774292s
Reputation | Calculation of the PageRank for Japan Search took 0.02089238166809082s
Interlinking | Calculation of Degree of Connection for Japan Search took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for Japan Search took 0.0007245540618896484s
Interlinking | Calculation of Clustering coefficient for Japan Search took 2.0265579223632812e-05s
Interoperability | Check the re-using of existing vocabs for Japan Search took 2.1457672119140625e-06s
Believability | Calculation of trust value for Japan Search took 1.049041748046875e-05s
INFO | --- Analysis for Japan-Search took 397.645521402359s
Availability | SPARQL endpoint availability check for Rijksmuseum Collection took 1.1098926067352295s
Availability | VoID file availability check for Rijksmuseum Collection took 0.0005357265472412109s
Completeness | Calculation of interlinking completeness for Rijksmuseum Collection took 0.18886256217956543s
Reputation | Calculation of the PageRank for Rijksmuseum Collection took 0.02104496955871582s
Interlinking | Calculation of Degree of Connection for Rijksmuseum Collection took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for Rijksmuseum Collection took 0.0007064342498779297s
Interlinking | Calculation of Clustering coefficient for Rijksmuseum Collection took 1.3113021850585938e-05s
Believability | Calculation of trust value for Rijksmuseum Collection took 1.3113021850585938e-05s
INFO | --- Analysis for Rijksmuseum took 3.770883798599243s
Availability | SPARQL endpoint availability check for Finnish Public Libraries took 1.0612695217132568s
Availability | VoID file availability check for Finnish Public Libraries took 0.0008275508880615234s
Extra | Recovery of all triples for Finnish Public Libraries took 13.340712785720825s
Performance | Total latancy measurement for Finnish Public Libraries took 1.4180772304534912s
Amount of data | Number of triples check for Finnish Public Libraries took 56.137577056884766s
Interoperability | New terms check for Finnish Public Libraries took 13.994640588760376s
Versatility | Languages check for Finnish Public Libraries took 60.27905607223511s
Interpretability | Number of blank nodes check for Finnish Public Libraries took 51.17010760307312s
Interpretability | RDF structures check for Finnish Public Libraries took 0.31380558013916016s
Versatility | Serialization formats check for Finnish Public Libraries took 0.2797527313232422s
Availability | RDF dump link check for Finnish Public Libraries took 0.28759193420410156s
License | MR license check for Finnish Public Libraries took 0.2780790328979492s
License | HR license check for Finnish Public Libraries took 29.78072428703308s
Amount of data | Number of property check for Finnish Public Libraries took 0.21026229858398438s
Understandability | Number of label check for Finnish Public Libraries took 11.867297649383545s
Understandability | URI regex check for Finnish Public Libraries took 0.5265653133392334s
Understandability | Vocabs check for Finnish Public Libraries took 0.12818312644958496s
Verifiability | Authors check for Finnish Public Libraries took 0.2809598445892334s
Verifiability | Publishers check for Finnish Public Libraries took 0.28203678131103516s
Performance | Throughput check for Finnish Public Libraries took 11.495381832122803s
Amount of data | Check the number of entities for Finnish Public Libraries took 7.009506225585938e-05s
Verifiability | Contribs. check for Finnish Public Libraries took 0.13350200653076172s
Interlinking | sameAs chians check for Finnish Public Libraries took 0.2859311103820801s
Interlinking | skos check for Finnish Public Libraries took 0.27436399459838867s
Interlinking | skos check for Finnish Public Libraries took 0.12688207626342773s
Timeliness | dataset update frequency check for Finnish Public Libraries took 0.12457418441772461s
Currency | Creation date check for Finnish Public Libraries took 0.43916869163513184s
Currency | Modification date check for Finnish Public Libraries took 0.4015843868255615s
Rep.Conc. | URIs length for Finnish Public Libraries took 78.05275297164917s
Interoperability | New vocabularies check for Finnish Public Libraries took 1.1205673217773438e-05s
Consistency | Deprecated classes/propertiers check for Finnish Public Libraries took 0.3606421947479248s
Accuracy | Check Functional Property for Finnish Public Libraries took 0.1256420612335205s
Accuracy | Check Inverse Functional Property for Finnish Public Libraries took 0.492755651473999s
Accuracy | Check Empty annotation labels for Finnish Public Libraries took 8.089563131332397s
Accuracy | Check White space in annotation for Finnish Public Libraries took 2.1682791709899902s
Accuracy | Check Datatype consistency for Finnish Public Libraries took 4.35671854019165s
Consistency | Disjoint class check for Finnish Public Libraries took 0.26790595054626465s
Consistency | Check Misplaced properties for Finnish Public Libraries took 56.535934925079346s
Consistency | Check Ontology hijacking for Finnish Public Libraries took 14.419250726699829s
Consistency | Check Invalid usage of undefined classes for Finnish Public Libraries took 1.5634181499481201s
Consistency | Check Invalid usage of undefined properties for Finnish Public Libraries took 58.49986433982849s
Conciseness | Check Extensional conciseness for Finnish Public Libraries took 2.723660945892334s
Security | Sign check for Finnish Public Libraries took 0.30857086181640625s
Availability | Check URIs Dereferenciability for Finnish Public Libraries took 1.7889771461486816s
Completeness | Calculation of interlinking completeness for Finnish Public Libraries took 0.3769571781158447s
Reputation | Calculation of the PageRank for Finnish Public Libraries took 0.020801544189453125s
Interlinking | Calculation of Degree of Connection for Finnish Public Libraries took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Finnish Public Libraries took 0.0006952285766601562s
Interlinking | Calculation of Clustering coefficient for Finnish Public Libraries took 1.2159347534179688e-05s
Interoperability | Check the re-using of existing vocabs for Finnish Public Libraries took 1.6689300537109375e-06s
Believability | Calculation of trust value for Finnish Public Libraries took 1.049041748046875e-05s
INFO | --- Analysis for FI-Library took 623.5061151981354s
Availability | SPARQL endpoint availability check for Shanghai Library Open Data Platform took 5.2634570598602295s
Availability | VoID file availability check for Shanghai Library Open Data Platform took 0.0005033016204833984s
Completeness | Calculation of interlinking completeness for Shanghai Library Open Data Platform took 0.18906450271606445s
Reputation | Calculation of the PageRank for Shanghai Library Open Data Platform took 0.020709991455078125s
Interlinking | Calculation of Degree of Connection for Shanghai Library Open Data Platform took 1.52587890625e-05s
Interlinking | Calculation of Centrality for Shanghai Library Open Data Platform took 0.0007221698760986328s
Interlinking | Calculation of Clustering coefficient for Shanghai Library Open Data Platform took 1.4781951904296875e-05s
Believability | Calculation of trust value for Shanghai Library Open Data Platform took 1.0728836059570312e-05s
INFO | --- Analysis for Shanghai-Library-Open-Data-Platform took 9.376300811767578s
Availability | SPARQL endpoint availability check for National Library Netherlands took 1.3394625186920166s
Availability | VoID file availability check for National Library Netherlands took 0.0005269050598144531s
Extra | Recovery of all triples for National Library Netherlands took 0.7085206508636475s
Performance | Total latancy measurement for National Library Netherlands took 0.8244304656982422s
Amount of data | Number of triples check for National Library Netherlands took 0.16785645484924316s
Interoperability | New terms check for National Library Netherlands took 1.4390215873718262s
Versatility | Languages check for National Library Netherlands took 58.140376806259155s
Interpretability | Number of blank nodes check for National Library Netherlands took 0.1624307632446289s
Interpretability | RDF structures check for National Library Netherlands took 0.15721750259399414s
Versatility | Serialization formats check for National Library Netherlands took 0.17279744148254395s
Availability | RDF dump link check for National Library Netherlands took 0.17348051071166992s
License | MR license check for National Library Netherlands took 0.15592217445373535s
License | HR license check for National Library Netherlands took 0.19791769981384277s
Amount of data | Number of property check for National Library Netherlands took 0.1700148582458496s
Understandability | Number of label check for National Library Netherlands took 0.1708381175994873s
Understandability | URI regex check for National Library Netherlands took 0.3239459991455078s
Understandability | Vocabs check for National Library Netherlands took 0.1784803867340088s
Verifiability | Authors check for National Library Netherlands took 0.18080830574035645s
Verifiability | Publishers check for National Library Netherlands took 0.1535630226135254s
Performance | Throughput check for National Library Netherlands took 11.111688613891602s
Amount of data | Check the number of entities for National Library Netherlands took 7.271766662597656e-05s
Verifiability | Contribs. check for National Library Netherlands took 0.1621851921081543s
Interlinking | sameAs chians check for National Library Netherlands took 0.14855360984802246s
Interlinking | skos check for National Library Netherlands took 0.17128658294677734s
Interlinking | skos check for National Library Netherlands took 0.18815851211547852s
Timeliness | dataset update frequency check for National Library Netherlands took 0.1610856056213379s
Currency | Creation date check for National Library Netherlands took 0.31151485443115234s
Currency | Modification date check for National Library Netherlands took 0.33321070671081543s
Rep.Conc. | URIs length for National Library Netherlands took 0.6711223125457764s
Interoperability | New vocabularies check for National Library Netherlands took 1.430511474609375e-06s
Consistency | Deprecated classes/propertiers check for National Library Netherlands took 0.15627813339233398s
Accuracy | Check Empty annotation labels for National Library Netherlands took 0.4418327808380127s
Accuracy | Check White space in annotation for National Library Netherlands took 0.026657581329345703s
Accuracy | Check Datatype consistency for National Library Netherlands took 0.028980731964111328s
Consistency | Disjoint class check for National Library Netherlands took 0.17129087448120117s
Consistency | Check Misplaced properties for National Library Netherlands took 0.31904125213623047s
Consistency | Check Ontology hijacking for National Library Netherlands took 1.7556133270263672s
Consistency | Check Invalid usage of undefined classes for National Library Netherlands took 1.327336072921753s
Consistency | Check Invalid usage of undefined properties for National Library Netherlands took 1.4778945446014404s
Conciseness | Check Extensional conciseness for National Library Netherlands took 0.033225059509277344s
Security | Sign check for National Library Netherlands took 0.15395307540893555s
Availability | Check URIs Dereferenciability for National Library Netherlands took 1711.6020240783691s
Completeness | Calculation of interlinking completeness for National Library Netherlands took 0.5218846797943115s
Reputation | Calculation of the PageRank for National Library Netherlands took 0.021787643432617188s
Interlinking | Calculation of Degree of Connection for National Library Netherlands took 2.09808349609375e-05s
Interlinking | Calculation of Centrality for National Library Netherlands took 0.0007603168487548828s
Interlinking | Calculation of Clustering coefficient for National Library Netherlands took 6.151199340820312e-05s
Interoperability | Check the re-using of existing vocabs for National Library Netherlands took 2.1457672119140625e-06s
Believability | Calculation of trust value for National Library Netherlands took 1.4543533325195312e-05s
INFO | --- Analysis for National-Library-Netherlands took 1816.8324959278107s
Availability | SPARQL endpoint availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.5004959106445312s
Availability | VoID file availability check for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006206035614013672s
Completeness | Calculation of interlinking completeness for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.17303252220153809s
Reputation | Calculation of the PageRank for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.020507097244262695s
Interlinking | Calculation of Degree of Connection for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.33514404296875e-05s
Interlinking | Calculation of Centrality for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 0.0006978511810302734s
Interlinking | Calculation of Clustering coefficient for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.2874603271484375e-05s
Believability | Calculation of trust value for Database of the Census of Antique Works of Art and Architecture Known in the Renaissance took 1.1920928955078125e-05s
INFO | --- Analysis for Antique-Renaissance took 4.5185017585754395s
Availability | SPARQL endpoint availability check for ARTSDATA.CA took 4.374481916427612s
Availability | VoID file availability check for ARTSDATA.CA took 0.0007307529449462891s
Completeness | Calculation of interlinking completeness for ARTSDATA.CA took 0.17533659934997559s
Reputation | Calculation of the PageRank for ARTSDATA.CA took 0.020603656768798828s
Interlinking | Calculation of Degree of Connection for ARTSDATA.CA took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for ARTSDATA.CA took 0.0007605552673339844s
Interlinking | Calculation of Clustering coefficient for ARTSDATA.CA took 1.1920928955078125e-05s
Believability | Calculation of trust value for ARTSDATA.CA took 1.3113021850585938e-05s
INFO | --- Analysis for ARTSDATA-CA took 8.961350917816162s
Availability | SPARQL endpoint availability check for Architecture of Knowledge took 0.18459415435791016s
Availability | VoID file availability check for Architecture of Knowledge took 0.0005359649658203125s
Completeness | Calculation of interlinking completeness for Architecture of Knowledge took 0.18144893646240234s
Reputation | Calculation of the PageRank for Architecture of Knowledge took 0.02047443389892578s
Interlinking | Calculation of Degree of Connection for Architecture of Knowledge took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Architecture of Knowledge took 0.0007231235504150391s
Interlinking | Calculation of Clustering coefficient for Architecture of Knowledge took 1.1444091796875e-05s
Believability | Calculation of trust value for Architecture of Knowledge took 1.2636184692382812e-05s
INFO | --- Analysis for ArCo took 2.5515236854553223s
Availability | SPARQL endpoint availability check for ConfermentSampo took 0.29593610763549805s
Availability | VoID file availability check for ConfermentSampo took 0.0004968643188476562s
Extra | Recovery of all triples for ConfermentSampo took 18.73396944999695s
Performance | Total latancy measurement for ConfermentSampo took 0.8419783115386963s
Amount of data | Number of triples check for ConfermentSampo took 8.756594181060791s
Interoperability | New terms check for ConfermentSampo took 2.5388946533203125s
Versatility | Languages check for ConfermentSampo took 26.15586233139038s
Interpretability | Number of blank nodes check for ConfermentSampo took 8.255790710449219s
Security | Check HTTPS for ConfermentSampo took 0.4083256721496582s
Interpretability | RDF structures check for ConfermentSampo took 0.2145698070526123s
Versatility | Serialization formats check for ConfermentSampo took 0.22080564498901367s
Availability | RDF dump link check for ConfermentSampo took 3.140557050704956s
License | MR license check for ConfermentSampo took 0.21212100982666016s
License | HR license check for ConfermentSampo took 0.26627302169799805s
Amount of data | Number of property check for ConfermentSampo took 0.1945199966430664s
Understandability | Number of label check for ConfermentSampo took 5.518524646759033s
Understandability | URI regex check for ConfermentSampo took 0.3747272491455078s
Understandability | Vocabs check for ConfermentSampo took 0.17062067985534668s
Verifiability | Authors check for ConfermentSampo took 0.201279878616333s
Verifiability | Publishers check for ConfermentSampo took 0.2004234790802002s
Performance | Throughput check for ConfermentSampo took 11.124501466751099s
Amount of data | Check the number of entities for ConfermentSampo took 3.89119029045105s
Verifiability | Contribs. check for ConfermentSampo took 0.17111682891845703s
Interlinking | sameAs chians check for ConfermentSampo took 0.44793152809143066s
Interlinking | skos check for ConfermentSampo took 0.16836786270141602s
Interlinking | skos check for ConfermentSampo took 0.15999889373779297s
Timeliness | dataset update frequency check for ConfermentSampo took 0.17011523246765137s
Currency | Creation date check for ConfermentSampo took 0.36472296714782715s
Currency | Modification date check for ConfermentSampo took 0.36527395248413086s
Rep.Conc. | URIs length for ConfermentSampo took 34.18541622161865s
Interoperability | New vocabularies check for ConfermentSampo took 1.0013580322265625e-05s
Consistency | Deprecated classes/propertiers check for ConfermentSampo took 0.1991429328918457s
Accuracy | Check Functional Property for ConfermentSampo took 0.1956644058227539s
Accuracy | Check Inverse Functional Property for ConfermentSampo took 0.16595983505249023s
Accuracy | Check Empty annotation labels for ConfermentSampo took 14.653632640838623s
Accuracy | Check White space in annotation for ConfermentSampo took 3.003964900970459s
Accuracy | Check Datatype consistency for ConfermentSampo took 5.120793104171753s
Consistency | Disjoint class check for ConfermentSampo took 0.17084336280822754s
Consistency | Check Misplaced properties for ConfermentSampo took 7.033875465393066s
Consistency | Check Ontology hijacking for ConfermentSampo took 14.88993787765503s
Consistency | Check Invalid usage of undefined classes for ConfermentSampo took 1.4708044528961182s
Consistency | Check Invalid usage of undefined properties for ConfermentSampo took 1.5985431671142578s
Conciseness | Check Extensional conciseness for ConfermentSampo took 2.830461263656616s
Conciseness | Check Intensional conciseness for ConfermentSampo took 0.2010185718536377s
Security | Sign check for ConfermentSampo took 0.16660046577453613s
Availability | Check URIs Dereferenciability for ConfermentSampo took 1398.0773684978485s
Completeness | Calculation of interlinking completeness for ConfermentSampo took 0.3002808094024658s
Reputation | Calculation of the PageRank for ConfermentSampo took 0.021908998489379883s
Interlinking | Calculation of Degree of Connection for ConfermentSampo took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for ConfermentSampo took 0.0007023811340332031s
Interlinking | Calculation of Clustering coefficient for ConfermentSampo took 1.621246337890625e-05s
Interoperability | Check the re-using of existing vocabs for ConfermentSampo took 1.9073486328125e-06s
Believability | Calculation of trust value for ConfermentSampo took 7.867813110351562e-06s
INFO | --- Analysis for ConfermentSampo took 1695.8673119544983s
Availability | SPARQL endpoint availability check for Museum Finland took 0.34349966049194336s
Availability | VoID file availability check for Museum Finland took 0.0005083084106445312s
Extra | Recovery of all triples for Museum Finland took 11.093842267990112s
Performance | Total latancy measurement for Museum Finland took 0.8303158283233643s
Amount of data | Number of triples check for Museum Finland took 0.34785985946655273s
Interoperability | New terms check for Museum Finland took 1.991525650024414s
Versatility | Languages check for Museum Finland took 0.6711854934692383s
Interpretability | Number of blank nodes check for Museum Finland took 0.3240065574645996s
Security | Check HTTPS for Museum Finland took 0.24521279335021973s
Interpretability | RDF structures check for Museum Finland took 0.3196532726287842s
Versatility | Serialization formats check for Museum Finland took 0.20707011222839355s
Availability | RDF dump link check for Museum Finland took 0.1676483154296875s
License | MR license check for Museum Finland took 0.19804954528808594s
License | HR license check for Museum Finland took 1.0134117603302002s
Amount of data | Number of property check for Museum Finland took 0.1902768611907959s
Understandability | Number of label check for Museum Finland took 0.3506019115447998s
Understandability | URI regex check for Museum Finland took 0.38097238540649414s
Understandability | Vocabs check for Museum Finland took 0.16307735443115234s
Verifiability | Authors check for Museum Finland took 0.1647968292236328s
Verifiability | Publishers check for Museum Finland took 0.16290068626403809s
Performance | Throughput check for Museum Finland took 11.1304452419281s
Amount of data | Check the number of entities for Museum Finland took 6.699562072753906e-05s
Verifiability | Contribs. check for Museum Finland took 0.16336488723754883s
Interlinking | sameAs chians check for Museum Finland took 0.16463756561279297s
Interlinking | skos check for Museum Finland took 0.16527676582336426s
Interlinking | skos check for Museum Finland took 0.15978121757507324s
Timeliness | dataset update frequency check for Museum Finland took 0.16413617134094238s
Currency | Creation date check for Museum Finland took 0.35444045066833496s
Currency | Modification date check for Museum Finland took 0.3711099624633789s
Rep.Conc. | URIs length for Museum Finland took 3.642947196960449s
Interoperability | New vocabularies check for Museum Finland took 8.344650268554688e-06s
Consistency | Deprecated classes/propertiers check for Museum Finland took 0.19188761711120605s
Accuracy | Check Functional Property for Museum Finland took 0.16243672370910645s
Accuracy | Check Inverse Functional Property for Museum Finland took 0.16277575492858887s
Accuracy | Check Empty annotation labels for Museum Finland took 1.0045533180236816s
Accuracy | Check White space in annotation for Museum Finland took 0.06163311004638672s
Accuracy | Check Datatype consistency for Museum Finland took 0.946368932723999s
Consistency | Disjoint class check for Museum Finland took 0.16269421577453613s
Consistency | Check Misplaced properties for Museum Finland took 0.6218197345733643s
Consistency | Check Ontology hijacking for Museum Finland took 2.2725090980529785s
Consistency | Check Invalid usage of undefined classes for Museum Finland took 1.5177979469299316s
Consistency | Check Invalid usage of undefined properties for Museum Finland took 1.7086288928985596s
Conciseness | Check Extensional conciseness for Museum Finland took 0.6508843898773193s
Conciseness | Check Intensional conciseness for Museum Finland took 0.24527692794799805s
Security | Sign check for Museum Finland took 0.16370129585266113s
Availability | Check URIs Dereferenciability for Museum Finland took 3115.446534395218s
Completeness | Calculation of interlinking completeness for Museum Finland took 0.40229249000549316s
Reputation | Calculation of the PageRank for Museum Finland took 0.022505998611450195s
Interlinking | Calculation of Degree of Connection for Museum Finland took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Museum Finland took 0.0007107257843017578s
Interlinking | Calculation of Clustering coefficient for Museum Finland took 0.00010347366333007812s
Interoperability | Check the re-using of existing vocabs for Museum Finland took 5.245208740234375e-06s
Believability | Calculation of trust value for Museum Finland took 1.1205673217773438e-05s
INFO | --- Analysis for FI-Museum took 3176.745635509491s
Availability | SPARQL endpoint availability check for Mapping Manuscript Migrations took 0.19458699226379395s
Availability | VoID file availability check for Mapping Manuscript Migrations took 0.0005588531494140625s
Extra | Recovery of all triples for Mapping Manuscript Migrations took 15.525054693222046s
Performance | Total latancy measurement for Mapping Manuscript Migrations took 0.8400864601135254s
Amount of data | Number of triples check for Mapping Manuscript Migrations took 29.476972103118896s
Interoperability | New terms check for Mapping Manuscript Migrations took 4.899208068847656s
Versatility | Languages check for Mapping Manuscript Migrations took 75.5254545211792s
Interpretability | Number of blank nodes check for Mapping Manuscript Migrations took 29.213364601135254s
Security | Check HTTPS for Mapping Manuscript Migrations took 0.4233131408691406s
Interpretability | RDF structures check for Mapping Manuscript Migrations took 0.19645261764526367s
Versatility | Serialization formats check for Mapping Manuscript Migrations took 0.1930227279663086s
Availability | RDF dump link check for Mapping Manuscript Migrations took 0.1627507209777832s
License | MR license check for Mapping Manuscript Migrations took 0.1923983097076416s
License | HR license check for Mapping Manuscript Migrations took 1.7992894649505615s
Amount of data | Number of property check for Mapping Manuscript Migrations took 0.19189095497131348s
Understandability | Number of label check for Mapping Manuscript Migrations took 8.637685775756836s
Understandability | URI regex check for Mapping Manuscript Migrations took 0.36713552474975586s
Understandability | Vocabs check for Mapping Manuscript Migrations took 0.16390609741210938s
Verifiability | Authors check for Mapping Manuscript Migrations took 0.19599294662475586s
Verifiability | Publishers check for Mapping Manuscript Migrations took 0.19433283805847168s
Performance | Throughput check for Mapping Manuscript Migrations took 11.304144859313965s
Amount of data | Check the number of entities for Mapping Manuscript Migrations took 1.0381336212158203s
Verifiability | Contribs. check for Mapping Manuscript Migrations took 0.1692965030670166s
Interlinking | sameAs chians check for Mapping Manuscript Migrations took 0.5156538486480713s
Interlinking | skos check for Mapping Manuscript Migrations took 0.17152833938598633s
Interlinking | skos check for Mapping Manuscript Migrations took 0.16007304191589355s
Timeliness | dataset update frequency check for Mapping Manuscript Migrations took 0.16373443603515625s
Currency | Creation date check for Mapping Manuscript Migrations took 0.3556632995605469s
Currency | Modification date check for Mapping Manuscript Migrations took 0.19327783584594727s
Rep.Conc. | URIs length for Mapping Manuscript Migrations took 48.430737018585205s
Interoperability | New vocabularies check for Mapping Manuscript Migrations took 8.821487426757812e-06s
Consistency | Deprecated classes/propertiers check for Mapping Manuscript Migrations took 0.16315054893493652s
Accuracy | Check Functional Property for Mapping Manuscript Migrations took 0.16234540939331055s
Accuracy | Check Inverse Functional Property for Mapping Manuscript Migrations took 0.16289997100830078s
Accuracy | Check Empty annotation labels for Mapping Manuscript Migrations took 10.711938858032227s
Accuracy | Check White space in annotation for Mapping Manuscript Migrations took 2.419818878173828s
Accuracy | Check Datatype consistency for Mapping Manuscript Migrations took 5.701649188995361s
Consistency | Disjoint class check for Mapping Manuscript Migrations took 0.19249629974365234s
Consistency | Check Misplaced properties for Mapping Manuscript Migrations took 22.977481842041016s
Consistency | Check Ontology hijacking for Mapping Manuscript Migrations took 16.313040494918823s
Consistency | Check Invalid usage of undefined classes for Mapping Manuscript Migrations took 1.6332099437713623s
Consistency | Check Invalid usage of undefined properties for Mapping Manuscript Migrations took 1.6414737701416016s
Conciseness | Check Extensional conciseness for Mapping Manuscript Migrations took 2.837460994720459s
Conciseness | Check Intensional conciseness for Mapping Manuscript Migrations took 0.192779541015625s
Security | Sign check for Mapping Manuscript Migrations took 0.16328740119934082s
Availability | Check URIs Dereferenciability for Mapping Manuscript Migrations took 21.716902256011963s
Completeness | Calculation of interlinking completeness for Mapping Manuscript Migrations took 0.24201655387878418s
Reputation | Calculation of the PageRank for Mapping Manuscript Migrations took 0.02074885368347168s
Interlinking | Calculation of Degree of Connection for Mapping Manuscript Migrations took 2.7418136596679688e-05s
Interlinking | Calculation of Centrality for Mapping Manuscript Migrations took 0.0006930828094482422s
Interlinking | Calculation of Clustering coefficient for Mapping Manuscript Migrations took 1.2636184692382812e-05s
Interoperability | Check the re-using of existing vocabs for Mapping Manuscript Migrations took 1.9073486328125e-06s
Believability | Calculation of trust value for Mapping Manuscript Migrations took 1.0728836059570312e-05s
INFO | --- Analysis for MMM took 517.9176936149597s
Availability | SPARQL endpoint availability check for Semantic Kalevala took 0.23331212997436523s
Availability | VoID file availability check for Semantic Kalevala took 0.000457763671875s
Extra | Recovery of all triples for Semantic Kalevala took 9.067280530929565s
Performance | Total latancy measurement for Semantic Kalevala took 0.8285002708435059s
Amount of data | Number of triples check for Semantic Kalevala took 0.41616177558898926s
Interoperability | New terms check for Semantic Kalevala took 2.5439260005950928s
Versatility | Languages check for Semantic Kalevala took 0.9405503273010254s
Interpretability | Number of blank nodes check for Semantic Kalevala took 0.38217759132385254s
Security | Check HTTPS for Semantic Kalevala took 0.2485353946685791s
Interpretability | RDF structures check for Semantic Kalevala took 0.39901161193847656s
Versatility | Serialization formats check for Semantic Kalevala took 0.19420099258422852s
Availability | RDF dump link check for Semantic Kalevala took 0.16436457633972168s
License | MR license check for Semantic Kalevala took 0.279982328414917s
License | HR license check for Semantic Kalevala took 1.0647361278533936s
Amount of data | Number of property check for Semantic Kalevala took 0.19077467918395996s
Understandability | Number of label check for Semantic Kalevala took 0.7620863914489746s
Understandability | URI regex check for Semantic Kalevala took 0.33152174949645996s
Understandability | Vocabs check for Semantic Kalevala took 0.16457152366638184s
Verifiability | Authors check for Semantic Kalevala took 0.16410422325134277s
Verifiability | Publishers check for Semantic Kalevala took 0.17972040176391602s
Performance | Throughput check for Semantic Kalevala took 11.264281272888184s
Amount of data | Check the number of entities for Semantic Kalevala took 0.00015115737915039062s
Verifiability | Contribs. check for Semantic Kalevala took 0.23641037940979004s
Interlinking | sameAs chians check for Semantic Kalevala took 0.19394469261169434s
Interlinking | skos check for Semantic Kalevala took 0.32981419563293457s
Interlinking | skos check for Semantic Kalevala took 0.16444754600524902s
Timeliness | dataset update frequency check for Semantic Kalevala took 0.20964503288269043s
Currency | Creation date check for Semantic Kalevala took 0.3551657199859619s
Currency | Modification date check for Semantic Kalevala took 0.3567337989807129s
Rep.Conc. | URIs length for Semantic Kalevala took 4.765775442123413s
Interoperability | New vocabularies check for Semantic Kalevala took 7.3909759521484375e-06s
Consistency | Deprecated classes/propertiers check for Semantic Kalevala took 0.22651147842407227s
Accuracy | Check Functional Property for Semantic Kalevala took 0.19221901893615723s
Accuracy | Check Inverse Functional Property for Semantic Kalevala took 0.16330170631408691s
Accuracy | Check Empty annotation labels for Semantic Kalevala took 1.875758409500122s
Accuracy | Check White space in annotation for Semantic Kalevala took 0.2986576557159424s
Accuracy | Check Datatype consistency for Semantic Kalevala took 1.3762526512145996s
Consistency | Disjoint class check for Semantic Kalevala took 0.1622002124786377s
Consistency | Check Misplaced properties for Semantic Kalevala took 0.7845032215118408s
Consistency | Check Ontology hijacking for Semantic Kalevala took 2.386868476867676s
Consistency | Check Invalid usage of undefined classes for Semantic Kalevala took 1.4121479988098145s
Consistency | Check Invalid usage of undefined properties for Semantic Kalevala took 1.60654878616333s
Conciseness | Check Extensional conciseness for Semantic Kalevala took 0.8914775848388672s
Conciseness | Check Intensional conciseness for Semantic Kalevala took 0.2155776023864746s
Security | Sign check for Semantic Kalevala took 0.16199874877929688s
Availability | Check URIs Dereferenciability for Semantic Kalevala took 3249.574001312256s
Completeness | Calculation of interlinking completeness for Semantic Kalevala took 1.0196900367736816s
Reputation | Calculation of the PageRank for Semantic Kalevala took 0.5007221698760986s
Interlinking | Calculation of Degree of Connection for Semantic Kalevala took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Semantic Kalevala took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for Semantic Kalevala took 1.2636184692382812e-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 1.2874603271484375e-05s
INFO | --- Analysis for Semantic-Kalevala took 3315.181506872177s
Availability | SPARQL endpoint availability check for Smithsonian American Art Museum took 0.9957516193389893s
Availability | VoID file availability check for Smithsonian American Art Museum took 0.0007219314575195312s
Extra | Recovery of all triples for Smithsonian American Art Museum took 287.99524569511414s
Performance | Total latancy measurement for Smithsonian American Art Museum took 3.4913551807403564s
Amount of data | Number of triples check for Smithsonian American Art Museum took 0.5906577110290527s
Interoperability | New terms check for Smithsonian American Art Museum took 3.0645906925201416s
Versatility | Languages check for Smithsonian American Art Museum took 25.239038705825806s
Interpretability | Number of blank nodes check for Smithsonian American Art Museum took 0.590080976486206s
Security | Check HTTPS for Smithsonian American Art Museum took 0.3647642135620117s
Interpretability | RDF structures check for Smithsonian American Art Museum took 0.9368607997894287s
Versatility | Serialization formats check for Smithsonian American Art Museum took 0.6902961730957031s
Availability | RDF dump link check for Smithsonian American Art Museum took 0.6131889820098877s
License | MR license check for Smithsonian American Art Museum took 0.6694731712341309s
License | HR license check for Smithsonian American Art Museum took 16.942314386367798s
Amount of data | Number of property check for Smithsonian American Art Museum took 0.5910711288452148s
Understandability | Number of label check for Smithsonian American Art Museum took 0.5903618335723877s
Understandability | URI regex check for Smithsonian American Art Museum took 1.193648099899292s
Understandability | Vocabs check for Smithsonian American Art Museum took 0.663175106048584s
Verifiability | Authors check for Smithsonian American Art Museum took 0.6709394454956055s
Verifiability | Publishers check for Smithsonian American Art Museum took 0.5971310138702393s
Performance | Throughput check for Smithsonian American Art Museum took 11.965404987335205s
Amount of data | Check the number of entities for Smithsonian American Art Museum took 7.534027099609375e-05s
Verifiability | Contribs. check for Smithsonian American Art Museum took 0.6026663780212402s
Interlinking | sameAs chians check for Smithsonian American Art Museum took 0.6866605281829834s
Interlinking | skos check for Smithsonian American Art Museum took 0.5903234481811523s
Interlinking | skos check for Smithsonian American Art Museum took 0.5919301509857178s
Timeliness | dataset update frequency check for Smithsonian American Art Museum took 0.6079485416412354s
Currency | Creation date check for Smithsonian American Art Museum took 1.336667776107788s
Currency | Modification date check for Smithsonian American Art Museum took 1.3274903297424316s
Rep.Conc. | URIs length for Smithsonian American Art Museum took 106.34610199928284s
Interoperability | New vocabularies check for Smithsonian American Art Museum took 1.0728836059570312e-05s
Consistency | Deprecated classes/propertiers check for Smithsonian American Art Museum took 0.5977082252502441s
Accuracy | Check Empty annotation labels for Smithsonian American Art Museum took 22.347694873809814s
Accuracy | Check White space in annotation for Smithsonian American Art Museum took 0.494401216506958s
Accuracy | Check Datatype consistency for Smithsonian American Art Museum took 4.234878063201904s
Consistency | Disjoint class check for Smithsonian American Art Museum took 0.5910384654998779s
Consistency | Check Misplaced properties for Smithsonian American Art Museum took 4.188831090927124s
Consistency | Check Ontology hijacking for Smithsonian American Art Museum took 98.58629441261292s
Consistency | Check Invalid usage of undefined classes for Smithsonian American Art Museum took 1.7023484706878662s
Consistency | Check Invalid usage of undefined properties for Smithsonian American Art Museum took 4.582083463668823s
Conciseness | Check Extensional conciseness for Smithsonian American Art Museum took 2.9448368549346924s
Conciseness | Check Intensional conciseness for Smithsonian American Art Museum took 0.6192319393157959s
Security | Sign check for Smithsonian American Art Museum took 0.6275115013122559s
Availability | Check URIs Dereferenciability for Smithsonian American Art Museum took 6.462382793426514s
Completeness | Calculation of interlinking completeness for Smithsonian American Art Museum took 0.28383779525756836s
Reputation | Calculation of the PageRank for Smithsonian American Art Museum took 0.020473003387451172s
Interlinking | Calculation of Degree of Connection for Smithsonian American Art Museum took 1.2636184692382812e-05s
Interlinking | Calculation of Centrality for Smithsonian American Art Museum took 0.0006875991821289062s
Interlinking | Calculation of Clustering coefficient for Smithsonian American Art Museum took 1.2874603271484375e-05s
Interoperability | Check the re-using of existing vocabs for Smithsonian American Art Museum took 2.6226043701171875e-06s
Believability | Calculation of trust value for Smithsonian American Art Museum took 1.1444091796875e-05s
INFO | --- Analysis for Smithsonian took 709.2528238296509s
Availability | SPARQL endpoint availability check for Zeri Photo Archive took 0.24192214012145996s
Availability | VoID file availability check for Zeri Photo Archive took 0.0006809234619140625s
Completeness | Calculation of interlinking completeness for Zeri Photo Archive took 0.18380498886108398s
Reputation | Calculation of the PageRank for Zeri Photo Archive took 0.0205233097076416s
Interlinking | Calculation of Degree of Connection for Zeri Photo Archive took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Zeri Photo Archive took 0.0009021759033203125s
Interlinking | Calculation of Clustering coefficient for Zeri Photo Archive took 1.3589859008789062e-05s
Believability | Calculation of trust value for Zeri Photo Archive took 1.3113021850585938e-05s
INFO | --- Analysis for Zeri-Photo-Archive took 5.272607326507568s
Availability | SPARQL endpoint availability check for Archives Hub took 22.243253231048584s
Availability | VoID file availability check for Archives Hub took 0.0005152225494384766s
Completeness | Calculation of interlinking completeness for Archives Hub took 0.18470215797424316s
Reputation | Calculation of the PageRank for Archives Hub took 0.021063804626464844s
Interlinking | Calculation of Degree of Connection for Archives Hub took 1.5735626220703125e-05s
Interlinking | Calculation of Centrality for Archives Hub took 0.0007040500640869141s
Interlinking | Calculation of Clustering coefficient for Archives Hub took 1.1682510375976562e-05s
Believability | Calculation of trust value for Archives Hub took 1.3113021850585938e-05s
INFO | --- Analysis for Archives-Hub took 54.30658292770386s
Availability | SPARQL endpoint availability check for Yale centre of British Art took 1.6355576515197754s
Availability | VoID file availability check for Yale centre of British Art took 0.0005383491516113281s
Completeness | Calculation of interlinking completeness for Yale centre of British Art took 0.18709444999694824s
Reputation | Calculation of the PageRank for Yale centre of British Art took 0.02060699462890625s
Interlinking | Calculation of Degree of Connection for Yale centre of British Art took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Yale centre of British Art took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Yale centre of British Art took 1.239776611328125e-05s
Believability | Calculation of trust value for Yale centre of British Art took 1.33514404296875e-05s
INFO | --- Analysis for Yale took 3.6212358474731445s
Availability | SPARQL endpoint availability check for Alexandria Digital Library Gazetteer took 262.3491988182068s
Availability | VoID file availability check for Alexandria Digital Library Gazetteer took 0.0004649162292480469s
Completeness | Calculation of interlinking completeness for Alexandria Digital Library Gazetteer took 0.17517304420471191s
Reputation | Calculation of the PageRank for Alexandria Digital Library Gazetteer took 0.020439863204956055s
Interlinking | Calculation of Degree of Connection for Alexandria Digital Library Gazetteer took 1.6450881958007812e-05s
Interlinking | Calculation of Centrality for Alexandria Digital Library Gazetteer took 0.0006926059722900391s
Interlinking | Calculation of Clustering coefficient for Alexandria Digital Library Gazetteer took 1.5974044799804688e-05s
Believability | Calculation of trust value for Alexandria Digital Library Gazetteer took 1.1682510375976562e-05s
INFO | --- Analysis for ADL took 535.0821015834808s
Availability | SPARQL endpoint availability check for MusicKG took 0.7894105911254883s
Availability | VoID file availability check for MusicKG took 0.000782012939453125s
Completeness | Calculation of interlinking completeness for MusicKG took 0.17551064491271973s
Reputation | Calculation of the PageRank for MusicKG took 0.02161097526550293s
Interlinking | Calculation of Degree of Connection for MusicKG took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for MusicKG took 0.0007052421569824219s
Interlinking | Calculation of Clustering coefficient for MusicKG took 1.3589859008789062e-05s
Believability | Calculation of trust value for MusicKG took 1.2874603271484375e-05s
INFO | --- Analysis for MusicKG took 3.278559446334839s
Availability | SPARQL endpoint availability check for CIDOC-CRM took 1.0693309307098389s
Availability | VoID file availability check for CIDOC-CRM took 0.0007090568542480469s
Completeness | Calculation of interlinking completeness for CIDOC-CRM took 0.19078445434570312s
Reputation | Calculation of the PageRank for CIDOC-CRM took 0.020627975463867188s
Interlinking | Calculation of Degree of Connection for CIDOC-CRM took 1.3828277587890625e-05s
Interlinking | Calculation of Centrality for CIDOC-CRM took 0.0007002353668212891s
Interlinking | Calculation of Clustering coefficient for CIDOC-CRM took 1.9073486328125e-05s
Believability | Calculation of trust value for CIDOC-CRM took 1.2159347534179688e-05s
INFO | --- Analysis for CIDOC-CRM took 4.957047939300537s
Availability | SPARQL endpoint availability check for Mondis took 0.5953059196472168s
Availability | VoID file availability check for Mondis took 0.0004973411560058594s
Completeness | Calculation of interlinking completeness for Mondis took 0.18386530876159668s
Reputation | Calculation of the PageRank for Mondis took 0.020758628845214844s
Interlinking | Calculation of Degree of Connection for Mondis took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for Mondis took 0.0007014274597167969s
Interlinking | Calculation of Clustering coefficient for Mondis took 1.33514404296875e-05s
Believability | Calculation of trust value for Mondis took 1.2636184692382812e-05s
INFO | --- Analysis for Mondis took 2.616373062133789s
Availability | SPARQL endpoint availability check for DigitalNZ took 3.145932912826538s
Availability | VoID file availability check for DigitalNZ took 0.0008084774017333984s
Completeness | Calculation of interlinking completeness for DigitalNZ took 0.1825118064880371s
Reputation | Calculation of the PageRank for DigitalNZ took 0.02186894416809082s
Interlinking | Calculation of Degree of Connection for DigitalNZ took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for DigitalNZ took 0.000713348388671875s
Interlinking | Calculation of Clustering coefficient for DigitalNZ took 1.3113021850585938e-05s
Believability | Calculation of trust value for DigitalNZ took 1.4066696166992188e-05s
INFO | --- Analysis for DigitalNZ took 6.145079135894775s
Availability | SPARQL endpoint availability check for Fondazione Zeri took 0.18374943733215332s
Availability | VoID file availability check for Fondazione Zeri took 0.0005640983581542969s
Completeness | Calculation of interlinking completeness for Fondazione Zeri took 0.1781156063079834s
Reputation | Calculation of the PageRank for Fondazione Zeri took 0.020845890045166016s
Interlinking | Calculation of Degree of Connection for Fondazione Zeri took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Fondazione Zeri took 0.0007123947143554688s
Interlinking | Calculation of Clustering coefficient for Fondazione Zeri took 1.4543533325195312e-05s
Believability | Calculation of trust value for Fondazione Zeri took 1.2874603271484375e-05s
INFO | --- Analysis for Fondazione-Zeri took 2.5200486183166504s
Availability | SPARQL endpoint availability check for Digital Public Library of America took 0.24258852005004883s
Availability | VoID file availability check for Digital Public Library of America took 0.0006999969482421875s
Completeness | Calculation of interlinking completeness for Digital Public Library of America took 0.1772770881652832s
Reputation | Calculation of the PageRank for Digital Public Library of America took 0.02335333824157715s
Interlinking | Calculation of Degree of Connection for Digital Public Library of America took 1.9311904907226562e-05s
Interlinking | Calculation of Centrality for Digital Public Library of America took 0.0007066726684570312s
Interlinking | Calculation of Clustering coefficient for Digital Public Library of America took 1.33514404296875e-05s
Believability | Calculation of trust value for Digital Public Library of America took 1.2636184692382812e-05s
INFO | --- Analysis for Library-of-America took 2.829068660736084s
Availability | SPARQL endpoint availability check for Auckland Museum took 2.064399003982544s
Availability | VoID file availability check for Auckland Museum took 0.0007843971252441406s
Completeness | Calculation of interlinking completeness for Auckland Museum took 0.2250380516052246s
Reputation | Calculation of the PageRank for Auckland Museum took 0.0209658145904541s
Interlinking | Calculation of Degree of Connection for Auckland Museum took 1.9073486328125e-05s
Interlinking | Calculation of Centrality for Auckland Museum took 0.0009624958038330078s
Interlinking | Calculation of Clustering coefficient for Auckland Museum took 1.5020370483398438e-05s
Believability | Calculation of trust value for Auckland Museum took 1.3589859008789062e-05s
INFO | --- Analysis for Auckland-Museum took 5.641148567199707s
Availability | SPARQL endpoint availability check for National Library of Spain took 1.7521424293518066s
Availability | VoID file availability check for National Library of Spain took 0.0005643367767333984s
Completeness | Calculation of interlinking completeness for National Library of Spain took 0.18223857879638672s
Reputation | Calculation of the PageRank for National Library of Spain took 0.022414684295654297s
Interlinking | Calculation of Degree of Connection for National Library of Spain took 6.67572021484375e-05s
Interlinking | Calculation of Centrality for National Library of Spain took 0.0011692047119140625s
Interlinking | Calculation of Clustering coefficient for National Library of Spain took 1.4781951904296875e-05s
Believability | Calculation of trust value for National Library of Spain took 1.2636184692382812e-05s
INFO | --- Analysis for BNE took 3.7430593967437744s
Availability | SPARQL endpoint availability check for National Library of Korea took 2.2188720703125s
Availability | VoID file availability check for National Library of Korea took 0.0005047321319580078s
Completeness | Calculation of interlinking completeness for National Library of Korea took 0.18447542190551758s
Reputation | Calculation of the PageRank for National Library of Korea took 0.020971298217773438s
Interlinking | Calculation of Degree of Connection for National Library of Korea took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for National Library of Korea took 0.00070953369140625s
Interlinking | Calculation of Clustering coefficient for National Library of Korea took 1.2874603271484375e-05s
Believability | Calculation of trust value for National Library of Korea took 8.821487426757812e-06s
INFO | --- Analysis for Korea-Library took 4.208394765853882s
Availability | SPARQL endpoint availability check for The State Russian Museum took 1.3684203624725342s
Availability | VoID file availability check for The State Russian Museum took 0.0005087852478027344s
Completeness | Calculation of interlinking completeness for The State Russian Museum took 0.17559385299682617s
Reputation | Calculation of the PageRank for The State Russian Museum took 0.020998001098632812s
Interlinking | Calculation of Degree of Connection for The State Russian Museum took 1.6689300537109375e-05s
Interlinking | Calculation of Centrality for The State Russian Museum took 0.0007200241088867188s
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.33514404296875e-05s
INFO | --- Analysis for Russian-Museum took 3.3450775146484375s
Availability | SPARQL endpoint availability check for National Library of Scotland took 1.7666966915130615s
Availability | VoID file availability check for National Library of Scotland took 0.0005178451538085938s
Completeness | Calculation of interlinking completeness for National Library of Scotland took 0.1837139129638672s
Reputation | Calculation of the PageRank for National Library of Scotland took 0.020380258560180664s
Interlinking | Calculation of Degree of Connection for National Library of Scotland took 1.4066696166992188e-05s
Interlinking | Calculation of Centrality for National Library of Scotland took 0.00070953369140625s
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 1.3113021850585938e-05s
INFO | --- Analysis for National-Library-of-Scotland took 6.4294350147247314s
Availability | SPARQL endpoint availability check for Epigraphic Database Heidelberg took 0.3335757255554199s
Availability | VoID file availability check for Epigraphic Database Heidelberg took 0.0006556510925292969s
Completeness | Calculation of interlinking completeness for Epigraphic Database Heidelberg took 0.189100980758667s
Reputation | Calculation of the PageRank for Epigraphic Database Heidelberg took 0.02066659927368164s
Interlinking | Calculation of Degree of Connection for Epigraphic Database Heidelberg took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for Epigraphic Database Heidelberg took 0.0006997585296630859s
Interlinking | Calculation of Clustering coefficient for Epigraphic Database Heidelberg took 1.33514404296875e-05s
Believability | Calculation of trust value for Epigraphic Database Heidelberg took 1.33514404296875e-05s
INFO | --- Analysis for Epigraphic-Database-Heidelberg took 2.5171754360198975s
Availability | SPARQL endpoint availability check for OntoComedySources took 0.20664715766906738s
Availability | VoID file availability check for OntoComedySources took 0.0004048347473144531s
Completeness | Calculation of interlinking completeness for OntoComedySources took 0.1723647117614746s
Reputation | Calculation of the PageRank for OntoComedySources took 0.020880937576293945s
Interlinking | Calculation of Degree of Connection for OntoComedySources took 1.7881393432617188e-05s
Interlinking | Calculation of Centrality for OntoComedySources took 0.00077056884765625s
Interlinking | Calculation of Clustering coefficient for OntoComedySources took 1.621246337890625e-05s
Believability | Calculation of trust value for OntoComedySources took 7.867813110351562e-06s
INFO | --- Analysis for OntoComedySources took 2.8478877544403076s
Availability | SPARQL endpoint availability check for OntoCeramic 2.0 took 0.20340704917907715s
Availability | VoID file availability check for OntoCeramic 2.0 took 0.0005104541778564453s
Completeness | Calculation of interlinking completeness for OntoCeramic 2.0 took 0.1901998519897461s
Reputation | Calculation of the PageRank for OntoCeramic 2.0 took 0.022503376007080078s
Interlinking | Calculation of Degree of Connection for OntoCeramic 2.0 took 2.2411346435546875e-05s
Interlinking | Calculation of Centrality for OntoCeramic 2.0 took 0.0010085105895996094s
Interlinking | Calculation of Clustering coefficient for OntoCeramic 2.0 took 1.5497207641601562e-05s
Believability | Calculation of trust value for OntoCeramic 2.0 took 1.239776611328125e-05s
INFO | --- Analysis for OntoCeramic-2.0 took 3.334522008895874s
Availability | SPARQL endpoint availability check for SaintGall Ontology took 0.16141080856323242s
Availability | VoID file availability check for SaintGall Ontology took 0.00046706199645996094s
Completeness | Calculation of interlinking completeness for SaintGall Ontology took 0.18399953842163086s
Reputation | Calculation of the PageRank for SaintGall Ontology took 0.02065443992614746s
Interlinking | Calculation of Degree of Connection for SaintGall Ontology took 1.5020370483398438e-05s
Interlinking | Calculation of Centrality for SaintGall Ontology took 0.0007042884826660156s
Interlinking | Calculation of Clustering coefficient for SaintGall Ontology took 1.33514404296875e-05s
Believability | Calculation of trust value for SaintGall Ontology took 1.33514404296875e-05s
INFO | --- Analysis for SaintGall-Ontology took 2.1321473121643066s
Availability | SPARQL endpoint availability check for Linguistic Phenomena Ontology took 0.7947590351104736s
Availability | VoID file availability check for Linguistic Phenomena Ontology took 0.0007448196411132812s
Completeness | Calculation of interlinking completeness for Linguistic Phenomena Ontology took 0.17532086372375488s
Reputation | Calculation of the PageRank for Linguistic Phenomena Ontology took 0.021007299423217773s
Interlinking | Calculation of Degree of Connection for Linguistic Phenomena Ontology took 1.5497207641601562e-05s
Interlinking | Calculation of Centrality for Linguistic Phenomena Ontology took 0.0007143020629882812s
Interlinking | Calculation of Clustering coefficient for Linguistic Phenomena Ontology took 1.4543533325195312e-05s
Believability | Calculation of trust value for Linguistic Phenomena Ontology took 1.33514404296875e-05s
INFO | --- Analysis for Linguistic-Phenomena-Ontology took 3.020218849182129s
Availability | SPARQL endpoint availability check for ICON took 0.26074719429016113s
Availability | VoID file availability check for ICON took 0.0006756782531738281s
Completeness | Calculation of interlinking completeness for ICON took 0.185166597366333s
Reputation | Calculation of the PageRank for ICON took 0.020600080490112305s
Interlinking | Calculation of Degree of Connection for ICON took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for ICON took 0.0007114410400390625s
Interlinking | Calculation of Clustering coefficient for ICON took 1.33514404296875e-05s
Believability | Calculation of trust value for ICON took 1.1205673217773438e-05s
INFO | --- Analysis for ICON took 3.1628501415252686s
Availability | SPARQL endpoint availability check for Polifonia took 0.24168038368225098s
Availability | VoID file availability check for Polifonia took 0.0005156993865966797s
Completeness | Calculation of interlinking completeness for Polifonia took 0.175140380859375s
Reputation | Calculation of the PageRank for Polifonia took 0.022250652313232422s
Interlinking | Calculation of Degree of Connection for Polifonia took 1.3113021850585938e-05s
Interlinking | Calculation of Centrality for Polifonia took 0.0006995201110839844s
Interlinking | Calculation of Clustering coefficient for Polifonia took 1.2874603271484375e-05s
Believability | Calculation of trust value for Polifonia took 1.0728836059570312e-05s
INFO | --- Analysis for Polifonia took 3.2669425010681152s
Availability | SPARQL endpoint availability check for Atlas of Paths Ontology - Italian Application Profile took 0.27611279487609863s
Availability | VoID file availability check for Atlas of Paths Ontology - Italian Application Profile took 0.0005676746368408203s
Completeness | Calculation of interlinking completeness for Atlas of Paths Ontology - Italian Application Profile took 0.18954706192016602s
Reputation | Calculation of the PageRank for Atlas of Paths Ontology - Italian Application Profile took 0.020746946334838867s
Interlinking | Calculation of Degree of Connection for Atlas of Paths Ontology - Italian Application Profile took 1.3589859008789062e-05s
Interlinking | Calculation of Centrality for Atlas of Paths Ontology - Italian Application Profile took 0.0007092952728271484s
Interlinking | Calculation of Clustering coefficient for Atlas of Paths Ontology - Italian Application Profile took 1.3828277587890625e-05s
Believability | Calculation of trust value for Atlas of Paths Ontology - Italian Application Profile took 1.0967254638671875e-05s
INFO | --- Analysis for Atlas-of-Paths took 2.9345436096191406s
Availability | SPARQL endpoint availability check for Music Note Ontology took 0.21120715141296387s
Availability | VoID file availability check for Music Note Ontology took 0.00047707557678222656s
Completeness | Calculation of interlinking completeness for Music Note Ontology took 0.18077397346496582s
Reputation | Calculation of the PageRank for Music Note Ontology took 0.020591259002685547s
Interlinking | Calculation of Degree of Connection for Music Note Ontology took 1.2874603271484375e-05s
Interlinking | Calculation of Centrality for Music Note Ontology took 0.0007035732269287109s
Interlinking | Calculation of Clustering coefficient for Music Note Ontology took 1.239776611328125e-05s
Believability | Calculation of trust value for Music Note Ontology took 9.5367431640625e-06s
INFO | --- Analysis for Music-Note-Ontology took 7.483484506607056s
Availability | SPARQL endpoint availability check for HaMSE took 0.20844435691833496s
Availability | VoID file availability check for HaMSE took 0.0005311965942382812s
Completeness | Calculation of interlinking completeness for HaMSE took 0.17864751815795898s
Reputation | Calculation of the PageRank for HaMSE took 0.020296812057495117s
Interlinking | Calculation of Degree of Connection for HaMSE took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for HaMSE took 0.000690460205078125s
Interlinking | Calculation of Clustering coefficient for HaMSE took 1.239776611328125e-05s
Believability | Calculation of trust value for HaMSE took 5.9604644775390625e-06s
INFO | --- Analysis for HaMSE took 3.6445648670196533s
Availability | SPARQL endpoint availability check for FOOD: FOod in Open Data took 0.2535865306854248s
Availability | VoID file availability check for FOOD: FOod in Open Data took 0.0005242824554443359s
Completeness | Calculation of interlinking completeness for FOOD: FOod in Open Data took 0.18263792991638184s
Reputation | Calculation of the PageRank for FOOD: FOod in Open Data took 0.020304441452026367s
Interlinking | Calculation of Degree of Connection for FOOD: FOod in Open Data took 1.1920928955078125e-05s
Interlinking | Calculation of Centrality for FOOD: FOod in Open Data took 0.0007081031799316406s
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 9.059906005859375e-06s
INFO | --- Analysis for FOod took 4.076843738555908s
Availability | SPARQL endpoint availability check for The ATLAS of Italian Digital Cultural Heritage took 0.6504542827606201s
Availability | VoID file availability check for The ATLAS of Italian Digital Cultural Heritage took 0.0005695819854736328s
Completeness | Calculation of interlinking completeness for The ATLAS of Italian Digital Cultural Heritage took 0.1875474452972412s
Reputation | Calculation of the PageRank for The ATLAS of Italian Digital Cultural Heritage took 0.020503997802734375s
Interlinking | Calculation of Degree of Connection for The ATLAS of Italian Digital Cultural Heritage took 1.4781951904296875e-05s
Interlinking | Calculation of Centrality for The ATLAS of Italian Digital Cultural Heritage took 0.0006992816925048828s
Interlinking | Calculation of Clustering coefficient for The ATLAS of Italian Digital Cultural Heritage took 1.4066696166992188e-05s
Believability | Calculation of trust value for The ATLAS of Italian Digital Cultural Heritage took 1.239776611328125e-05s
INFO | --- Analysis for ATLAS-Italian-Digital-CH took 4.0476603507995605s
Availability | SPARQL endpoint availability check for ARIADNEplus Knowledge Base took 1.725839376449585s
Availability | VoID file availability check for ARIADNEplus Knowledge Base took 0.0007815361022949219s
Completeness | Calculation of interlinking completeness for ARIADNEplus Knowledge Base took 0.17537760734558105s
Reputation | Calculation of the PageRank for ARIADNEplus Knowledge Base took 0.021179914474487305s
Interlinking | Calculation of Degree of Connection for ARIADNEplus Knowledge Base took 1.4543533325195312e-05s
Interlinking | Calculation of Centrality for ARIADNEplus Knowledge Base took 0.0007085800170898438s
Interlinking | Calculation of Clustering coefficient for ARIADNEplus Knowledge Base took 1.2874603271484375e-05s
Believability | Calculation of trust value for ARIADNEplus Knowledge Base took 1.2159347534179688e-05s
INFO | --- Analysis for ARIADNE took 5.050639867782593s
Availability | SPARQL endpoint availability check for Odeuropa Ontology took 0.4216628074645996s
Availability | VoID file availability check for Odeuropa Ontology took 0.0002894401550292969s
Completeness | Calculation of interlinking completeness for Odeuropa Ontology took 0.18137741088867188s
Reputation | Calculation of the PageRank for Odeuropa Ontology took 0.02112269401550293s
Interlinking | Calculation of Degree of Connection for Odeuropa Ontology took 1.239776611328125e-05s
Interlinking | Calculation of Centrality for Odeuropa Ontology took 0.0006964206695556641s
Interlinking | Calculation of Clustering coefficient for Odeuropa Ontology took 1.1920928955078125e-05s
Believability | Calculation of trust value for Odeuropa Ontology took 8.58306884765625e-06s
INFO | --- Analysis for Odeuropa took 2.396780490875244s

--- Total time for analysis:71720.89677786827s ---
--- Total time for analysis:19.92247132718563 hours ---